matrix-spec

Commit Graph

Author	SHA1	Message	Date
Kévin Commaille	45b6aaf07a	Upgrade Swagger data to OpenAPI 3.1 (#1310 ) Signed-off-by: Kévin Commaille <zecakeh@tedomum.fr>	1 year ago
Travis Ralston	b14759a27b	Add `room_types` and `room_type` to `/publicRooms` (#1199 ) MSC: https://github.com/matrix-org/matrix-spec-proposals/pull/3827 Incorporates https://github.com/matrix-org/matrix-spec-proposals/pull/3858	2 years ago
Alexey Rusakov	6792b7a9d6	Use type: integer, format: int64 for timestamps (#1129 ) * Use type: integer / format: int64 for timestamps Closes #749. * Changelog	2 years ago
Alexey Rusakov	6adacd18c1	Arrange a few titles (#1126 ) * Arrange a few titles Before this change, PublicRoomsChunk in the spec text could be found in two places (actually three but the third one is identical to the first one), defining two (_mostly_ identical but) different schemas. Ctrl-F'ing through the spec may confuse you with the "wrong" definition. This commit gives distinct schemas distinct names; aside from PublicRoomChunk, the same story happens with the derivative of stripped_state.yaml used in space_hierarchy.yaml (it's not exactly StrippedStateEvent either). As for the removal of `PublicRoomsChunks` (plural) - this title is unnecessary because the tooling would place rather self-explanatory `[PublicRoomsChunk]` without it, whereas the plural title ends up with no definition in the spec text. * Add changelog	2 years ago
Nicolas Werner	e70045f4cc	room_type is not a required parameter in practice (#1110 ) * room_type is not a required parameter in practice In practice servers seem to mirror what the room create event does and leave out the room_type when unset. Signed-off-by: Nicolas Werner <n.werner@famedly.com> * Add changelog Signed-off-by: Nicolas Werner <n.werner@famedly.com> * Also make room_type and allowed_room_ids optional in the openapi They are optional according to the text, but the openapi marks them as required instead. Signed-off-by: Nicolas Werner <n.werner@famedly.com> * Fix copy and paste error of newsfragment Signed-off-by: Nicolas Werner <n.werner@famedly.com>	2 years ago
The one with the braid (she/her) \| Dфҿ mit dem Zopf (sie/ihr)	31304300f5	fix: spaces hierarchy paramater types (#1097 ) * fix: spaces hierarchy paramater types - changed `limit` parameter type to integer - changed `query` parameter type to integer A floating number does not make any sense here. Also, at least Synapse does not allow floating point numbers in here. Signed-off-by: TheOneWithTheBraid <the-one@with-the-braid.cf> * Update changelogs/client_server/newsfragments/1097.clarification Co-authored-by: Travis Ralston <travpc@gmail.com>	3 years ago
Travis Ralston	fc3f7d60eb	Remove `aliases` from `/publicRooms` response (#3624 ) Through attempting to land [Synapse#11667](https://github.com/matrix-org/synapse/pull/11667) it was found that Synapse doesn't return the `aliases` property on `/publicRooms` as it was [removed](https://github.com/matrix-org/synapse/pull/6970) by a [tracking issue](https://github.com/matrix-org/synapse/issues/6898) referencing [MSC2432](https://github.com/matrix-org/matrix-doc/pull/2432) as its base. Though MSC2432 does not make mention of this, the [document](https://docs.google.com/document/d/1NNDkobiFLeUkJtyj0H6qvKIedgvIkZnFKo78-03cGEk/edit) the MSC is based upon makes deliberate effort to mention the endpoint and the removal of `aliases`. Thus, it is determined as a likely accidental omission from the formal MSC and therefore the formal spec. This has been corrected here by amending the MSC (per the process) and removing the field, basing itself off of the [spec PR for spaces](https://github.com/matrix-org/matrix-doc/pull/3610) for diff clarity.	3 years ago
Travis Ralston	9af83dfd41	Add Spaces to the spec (#3610 ) * First iteration of specifying Spaces MSCs: * https://github.com/matrix-org/matrix-doc/pull/3288 * https://github.com/matrix-org/matrix-doc/pull/2946 * https://github.com/matrix-org/matrix-doc/pull/1772 Note that this makes modifications to the underlying MSCs as well. These are intended to be minor edits to aid clarity/accuracy of the MSCs, as per the proposal process. Functionally, clients and servers might need to change their behaviour slightly as is expected of implementing this stuff early. Synapse has these changes (alongside backwards compatibility) here: https://github.com/matrix-org/synapse/pull/11667 * add changelogs * Accuracy per review * Apply suggestions from code review Co-authored-by: Richard van der Hoff <1389908+richvdh@users.noreply.github.com> * fully prefix new endpoints * Fully prefix endpoint in 3616 too * Fix ordering example Co-authored-by: Richard van der Hoff <1389908+richvdh@users.noreply.github.com>	3 years ago

8 Commits (044a78730eac66a2b55ed1cf09dd32da80727b13)