Specify how ordering of tags is supposed to work
This commit is contained in:
parent
3b390bff3c
commit
299af673da
5 changed files with 10 additions and 5 deletions
|
@ -314,7 +314,7 @@ paths:
|
||||||
"visibility": "private",
|
"visibility": "private",
|
||||||
"private_user_data": [{
|
"private_user_data": [{
|
||||||
"type": "m.tag",
|
"type": "m.tag",
|
||||||
"content": {"tags": {"work": {"order": 1}}}
|
"content": {"tags": {"work": {"order": "1"}}}
|
||||||
}]
|
}]
|
||||||
}
|
}
|
||||||
schema:
|
schema:
|
||||||
|
|
|
@ -248,7 +248,7 @@ paths:
|
||||||
"visibility": "private",
|
"visibility": "private",
|
||||||
"private_user_data": [{
|
"private_user_data": [{
|
||||||
"type": "m.tag",
|
"type": "m.tag",
|
||||||
"content": {"tags": {"work": {"order": 1}}}
|
"content": {"tags": {"work": {"order": "1"}}}
|
||||||
}]
|
}]
|
||||||
}
|
}
|
||||||
]
|
]
|
||||||
|
|
|
@ -291,7 +291,7 @@ paths:
|
||||||
"events": [
|
"events": [
|
||||||
{
|
{
|
||||||
"type": "m.tags",
|
"type": "m.tags",
|
||||||
"content": {"tags": {"work": {"order": 1}}}
|
"content": {"tags": {"work": {"order": "1"}}}
|
||||||
}
|
}
|
||||||
]
|
]
|
||||||
}
|
}
|
||||||
|
|
|
@ -55,7 +55,7 @@ paths:
|
||||||
application/json: |-
|
application/json: |-
|
||||||
{
|
{
|
||||||
"tags": {
|
"tags": {
|
||||||
"work": {"order": 1},
|
"work": {"order": "1"},
|
||||||
"pinned": {}
|
"pinned": {}
|
||||||
}
|
}
|
||||||
}
|
}
|
||||||
|
@ -97,7 +97,7 @@ paths:
|
||||||
schema:
|
schema:
|
||||||
type: object
|
type: object
|
||||||
example: |-
|
example: |-
|
||||||
{"order": 1}
|
{"order": "1"}
|
||||||
responses:
|
responses:
|
||||||
200:
|
200:
|
||||||
description:
|
description:
|
||||||
|
|
|
@ -21,6 +21,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
|
||||||
|
are compared lexicographically by unicode codepoint to determine which should
|
||||||
|
displayed first. So a tag with an ``order`` key of ``"apples"`` would appear
|
||||||
|
before a tag with an ``order`` key of ``"oranges"``.
|
||||||
|
|
||||||
{{m_tag_event}}
|
{{m_tag_event}}
|
||||||
|
|
||||||
Client Behaviour
|
Client Behaviour
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue