prosody
ca6a43fe0231
spec/scansion/pep_nickname.scs

Find changesets by keywords by author, files, the commit message, revision number or hash, or revset expression.

Software / code / prosody

File

spec/scansion/pep_nickname.scs @ 12579:ca6a43fe0231 0.12

util.jsonschema: Fix validation to not assume presence of "type" field MattJ reported a curious issue where validation did not work as expected. Primarily that the "type" field was expected to be mandatory, and thus leaving it out would result in no checks being performed. This was likely caused by misreading during initial development. Spent some time testing against https://github.com/json-schema-org/JSON-Schema-Test-Suite.git and discovered a multitude of issues, far too many to bother splitting into separate commits. More than half of them fail. Many because of features not implemented, which have been marked NYI. For example, some require deep comparisons e.g. when objects or arrays are present in enums fields. Some because of quirks with how Lua differs from JavaScript, e.g. no distinct array or object types. Tests involving fractional floating point numbers. We're definitely not going to follow references to remote resources. Or deal with UTF-16 sillyness. One test asserted that 1.0 is an integer, where Lua 5.3+ will disagree.
author Kim Alvefur <zash@zash.se>
date Fri, 08 Jul 2022 14:38:23 +0200
parent 11714:d783716103c1
child 12965:edde56b60fd7
line wrap: on
line source

# Publishing a nickname in PEP and receiving a notification

[Client] Romeo
	jid: romeo@localhost
	password: password

-----

Romeo connects

Romeo sends:
	<iq id="4" type="set">
	  <pubsub xmlns="http://jabber.org/protocol/pubsub">
	    <publish node="http://jabber.org/protocol/nick">
	      <item id="current">
	        <nickname xmlns="http://jabber.org/protocol/nick"/>
	      </item>
	    </publish>
	  </pubsub>
	</iq>

Romeo receives:
	<iq id="4" type="result">
	  <pubsub xmlns="http://jabber.org/protocol/pubsub">
	    <publish node="http://jabber.org/protocol/nick">
	      <item id="current"/>
	    </publish>
	  </pubsub>
	</iq>

Romeo sends:
	<presence>
	  <c xmlns="http://jabber.org/protocol/caps" hash="sha-1" node="http://code.matthewwild.co.uk/clix/" ver="jC32N+FhQoLrZ7nNQtZK3aqR0Fk="/>
	</presence>

Romeo receives:
	<iq id="disco" from="romeo@localhost" type="get">
	  <query xmlns="http://jabber.org/protocol/disco#info" node="http://code.matthewwild.co.uk/clix/#jC32N+FhQoLrZ7nNQtZK3aqR0Fk="/>
	</iq>

Romeo receives:
	<presence>
	  <c xmlns="http://jabber.org/protocol/caps" hash="sha-1" node="http://code.matthewwild.co.uk/clix/" ver="jC32N+FhQoLrZ7nNQtZK3aqR0Fk="/>
	</presence>

Romeo sends:
	<iq id="disco" type="result" to="romeo@localhost">
	  <query xmlns="http://jabber.org/protocol/disco#info" node="http://code.matthewwild.co.uk/clix/#jC32N+FhQoLrZ7nNQtZK3aqR0Fk=">
	    <identity type="console" name="clix" category="client"/>
	    <feature var="http://jabber.org/protocol/disco#items"/>
	    <feature var="http://jabber.org/protocol/disco#info"/>
	    <feature var="http://jabber.org/protocol/caps"/>
	    <feature var="http://jabber.org/protocol/nick+notify"/>
	  </query>
	</iq>

Romeo receives:
	<message type="headline" from="romeo@localhost">
	  <event xmlns="http://jabber.org/protocol/pubsub#event">
	    <items node="http://jabber.org/protocol/nick">
	      <item id="current" publisher="${Romeo's JID}">
	        <nickname xmlns="http://jabber.org/protocol/nick"/>
	      </item>
	    </items>
	  </event>
	</message>

Romeo sends:
	<presence type="unavailable"/>

Romeo disconnects