matrix-spec

Commit Graph

Author	SHA1	Message	Date
Richard van der Hoff	5f3b34448d	Add HTML ids for object definitions in the formatted specification (#1174 ) * Remove redundant call to resolve-allof All of the callers to resolve-additional-types already call resolve-allof (or if not, they should), so this is redundant. * Update `resolve-additional-types` to take a dict I want to add more params to this, so first make it take a dict. * `render-object-table`: take a "title" rather than a "caption" ... which means we can use the result from resolve-additional-types directly. * render-object-table: support adding an anchor to generated tables. * resolve-additional-types: generate an id for each returned type * render-event: pass an anchor_base into resolve-additional-types This means that it will generate an anchor for each type, whihc will then be passed into render-object-table and used as an `id` for the table. * render-operation: pass an anchor_base into resolve-additional-types * newsfiles	2 years ago
Travis Ralston	98db9a6d04	v1.3 changelog generation	2 years ago
Travis Ralston	10bd1b5038	Re-add timestamp massaging (#1094 ) * Re-add timestamp massaging Per [MSC3316](https://github.com/matrix-org/matrix-spec-proposals/pull/3316) * changelog	3 years ago
Travis Ralston	e488a7fb6d	v1.2 changelog	3 years ago
Richard van der Hoff	36b02edfc2	Distinguish 'client' from 'federation' events (#3658 ) Fixes #3305 Fixes #3380 The idea here is to better distinguish between a 'raw' event (as we send over the wire), and the 'serialised' format, as sent in responses to the C-S api and in `PUT /_matrix/app/v1/transactions/{txnId}`. It's made more complicated by the fact that there are _two_ serialisation formats, one used by `/sync` and `/notifications`, and one by everything else (the difference being whether `room_id` is included). In an ideal world, we wouldn't repeat `SerialisedEvent` every time it's used, and instead just link to the first reference, but that's a job for another day. Another job for another day is to get rid of things like `sync_state_event.yaml` (which is now used only in one place, so should be inlined.)	3 years ago
Richard van der Hoff	4a9c236572	Changelogs for #3674	3 years ago
Richard van der Hoff	39a41a18ba	Fix the response for `GET /_matrix/app/v1/thirdparty/protocol/{protocol}` (#3675 ) This should return a single protocol, not all of them. Fixes #2286.	3 years ago
Travis Ralston	195b8a54c5	v1.1 changelog	3 years ago
Travis Ralston	e659572183	Add changelogs for 2888	4 years ago
Travis Ralston	0b49112399	Appservices r0.1.2 changelog	5 years ago
Andrew Morgan	52643a92c6	Less confusing wording on Application Service's Legacy Routes (#2160 ) https://matrix.org/docs/spec/application_service/r0.1.1#legacy-routes The "becomes" wording made it a little bit confusing for which was the new route and which was the old.	5 years ago
Travis Ralston	4f915f2760	Appservice r0.1.1	6 years ago
Travis Ralston	d0fd20fdb4	Clarify how homeservers are meant to auth themselves to appservices Fixes https://github.com/matrix-org/matrix-doc/issues/1765 Note that the swagger definitions already say that authorization is required. It just wasn't mentioned in the spec.	6 years ago
Travis Ralston	9c2a789d34	Add missing changelogs and make existing ones match conventions The conventions are not set in stone, however the changelog should not be a mixed bag of voices.	6 years ago
Travis Ralston	fa96d8629b	Prepare the appservice spec for an r0 release This puts the scaffolding in place for an r0 release to happen, such as the changelog and version variables.	6 years ago

15 Commits (b36d4eff7d7a83ac24e3b6102ca221886cd40474)