matrix-spec/event-schemas/examples/m.tag

{
  "$ref": "core/event.json",
  "type": "m.tag",
  "content": {
    "tags": {
      "u.work": {"order": 1}
    }
  }
}
Document a v2 api for setting tags on rooms 2015-10-26 17:14:24 +01:00			`{`
Fix client-server event schemas: remove `age`, dedupe fields This commit adds support for event schema examples to have references to help reduce the chance of fields being forgotten. This also helps reduce duplication of fields, allowing for a more consistent spec that uses the same values everywhere. This also removes both `unsigned` and `age` from the examples as per: * https://github.com/matrix-org/matrix-doc/issues/1524 * https://github.com/matrix-org/matrix-doc/issues/630 Finally, this replaces "localhost" in the examples with an example domain. This is really just a nitpick thing on my part where seeing a "real world" domain is preferred. Fixes https://github.com/matrix-org/matrix-doc/issues/1524 Fixes https://github.com/matrix-org/matrix-doc/issues/630 Step towards https://github.com/matrix-org/matrix-doc/issues/1530 2018-08-25 01:59:48 +02:00			`"$ref": "core/event.json",`
Document a v2 api for setting tags on rooms 2015-10-26 17:14:24 +01:00			`"type": "m.tag",`
			`"content": {`
Allow room tags to have asssociated content, and return that content in the m.tag events 2015-11-02 14:31:25 +01:00			`"tags": {`
Tag ordering is defined as a number between 0 and 1, not strings Signed-off-by: Travis Ralston <travpc@gmail.com> 2018-03-03 20:40:41 +01:00			`"u.work": {"order": 1}`
Allow room tags to have asssociated content, and return that content in the m.tag events 2015-11-02 14:31:25 +01:00			`}`
Document a v2 api for setting tags on rooms 2015-10-26 17:14:24 +01:00			`}`
			`}`