Tag ordering is defined as a number between 0 and 1, not strings
Signed-off-by: Travis Ralston <travpc@gmail.com>
This commit is contained in:
parent
3dfa643b8b
commit
a3f006353c
2 changed files with 6 additions and 7 deletions
|
@ -35,12 +35,11 @@ the tags are for.
|
|||
Each tag has an associated JSON object with information about the tag, e.g how
|
||||
to order the rooms with a given tag.
|
||||
|
||||
Ordering information is given under the ``order`` key as a string. The string
|
||||
are compared lexicographically by unicode codepoint to determine which should
|
||||
displayed first. So a room with a tag with an ``order`` key of ``"apples"``
|
||||
would appear before a room with a tag with an ``order`` key of ``"oranges"``.
|
||||
If a room has a tag without an ``order`` key then it should appear after the
|
||||
rooms with that tag that have an ``order`` key.
|
||||
Ordering information is given under teh ``order`` key as a number between 0 and
|
||||
1. The numbers are compared such that 0 is displayed first. Therefore a room
|
||||
with an ``order`` of ``0.2`` would be displayed before a room with an ``order``
|
||||
of ``0.7``. If a room has a tag without an ``order`` key then it should appear
|
||||
after the rooms with that tag that have an ``order`` key.
|
||||
|
||||
The name of a tag MUST not exceed 255 bytes.
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue