wholetrans/docs-matrix-spec
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Tag ordering is defined as a number between 0 and 1, not strings

Browse source 
Signed-off-by: Travis Ralston <travpc@gmail.com>
This commit is contained in:
Travis Ralston 2018-03-03 12:40:41 -07:00
parent 3dfa643b8b
commit a3f006353c
2 changed files with 6 additions and 7 deletions
Download patch file Download diff file Expand all files Collapse all files

2
event-schemas/examples/m.tag
View file

@ -2,7 +2,7 @@
"type": "m.tag", "type": "m.tag",
"content": { "content": {
"tags": { "tags": {
"work": {"order": 1} "u.work": {"order": 1}
} }
} }
} }

11
specification/modules/tags.rst
View file

@ -35,12 +35,11 @@ the tags are for.
Each tag has an associated JSON object with information about the tag, e.g how Each tag has an associated JSON object with information about the tag, e.g how
to order the rooms with a given tag. to order the rooms with a given tag.
Ordering information is given under the ``order`` key as a string. The string Ordering information is given under teh ``order`` key as a number between 0 and
are compared lexicographically by unicode codepoint to determine which should 1. The numbers are compared such that 0 is displayed first. Therefore a room
displayed first. So a room with a tag with an ``order`` key of ``"apples"`` with an ``order`` of ``0.2`` would be displayed before a room with an ``order``
would appear before a room with a tag with an ``order`` key of ``"oranges"``. of ``0.7``. If a room has a tag without an ``order`` key then it should appear
If a room has a tag without an ``order`` key then it should appear after the after the rooms with that tag that have an ``order`` key.
rooms with that tag that have an ``order`` key.
The name of a tag MUST not exceed 255 bytes. The name of a tag MUST not exceed 255 bytes.