matrix-spec-proposals

Commit Graph

Author	SHA1	Message	Date
Richard van der Hoff	41368dc5a7	document CAS login Following the spirit of "document how it is, not how we wish it was", document the CAS login bits.	8 years ago
Mark Haines	30a3302921	Merge pull request #274 from matrix-org/markjh/default_rules Update the predefined push rules in the spec	9 years ago
Richard van der Hoff	01f8173c84	Put each bit of spec in its own directory I want to change the URLs for the spec sections on the website from <version>/<section>.html to <section>/<version>.html, to better reflect how we do the versioning. This puts each bit of spec in its own directory, updates the index to point to the right place, and fixes continuserv to deal with directories as well as files. This will probably require fixes to the speculator too, but I'll have to come back to that.	9 years ago
David Baker	71cb646541	Change `id` in the push gateway poke to be `event_id` and spec that it's the Matrix event ID of the message. Correct the spec for badge count pushes which omit fields previously described as mandatory. Add more detail about when to use event_id to suppress dupes. Also add the push gateway doc so it's actually included in the spec.	9 years ago
Daniel Wagner-Hall	e0c55eeccf	Add initial identity server spec More to come	9 years ago
Richard van der Hoff	68a4306773	Split room previews into a separate module Guest access and room peeking are orthogonal	9 years ago
Mark Haines	afe7638e30	Add a new title level to appease gendoc	9 years ago
Daniel Wagner-Hall	8eb84612f2	Add index page	9 years ago
Erik Johnston	dd276d4c4d	Add event context module	9 years ago
Daniel Wagner-Hall	63ca91f353	Move event signing to server-server spec It's definitely not a client concern. It isn't really in the right place at the moment, but s-s is very much a work in progress whereas c-s is nearly stable.	9 years ago
Daniel Wagner-Hall	f308b7543c	Specify /admin/whois/{userId}	9 years ago
Daniel Wagner-Hall	c9c433bc15	Make section depths consistent	9 years ago
Daniel Wagner-Hall	e401d3e262	Merge pull request #184 from matrix-org/daniel/splitspec Split spec into page-per-section	9 years ago
Daniel Wagner-Hall	e171acf01f	Split spec into page-per-section	9 years ago
Mark Haines	05c0092664	s/config/account_data/	9 years ago
Mark Haines	8f5783615c	Merge branch 'master' into markjh/client_config Conflicts: api/client-server/v1/rooms.yaml specification/targets.yaml	9 years ago
Mark Haines	c3769ef75c	Add a module for client config to the specification	9 years ago
Daniel Wagner-Hall	e72151f2c3	Specify guest room access This was reviewed as PR #150 and merged from daniel/anonymousaccess	9 years ago
Mark Haines	9b0d20315a	Add the tags module to the specification targets	9 years ago
Erik Johnston	1d01f69c3c	Merge remote-tracking branch 'origin/master' into erikj/search_actual	9 years ago
Kegan Dougal	3d087df538	Kill number prefixes for good	9 years ago
Erik Johnston	007bb1a69a	Add extra new line	9 years ago
Erik Johnston	5e48b0b79a	Add search to targets	9 years ago
Daniel Wagner-Hall	2502ca7ac6	Merge branch 'master' into daniel/threepidinvites-2 Conflicts: specification/targets.yaml	9 years ago
Kegan Dougal	a9618a981b	Swaggerify the /enabled endpoint	9 years ago
Kegan Dougal	319ba8f404	Combine push files into one We can fork it out again if it makes sense, but certainly 2/3 of the files were very small and it just adds more complexity when refactoring.	9 years ago
Daniel Wagner-Hall	af7d2ca9fc	Update 3pid invite spec This takes into account: 1) That finding the existing servers of a room is hard 2) Federation	9 years ago
Kegan Dougal	be9402b66f	Move feature profiles section to modules as a sub-section	9 years ago
Kegan Dougal	1da64db302	Use relative depths for groups instead of absolute ones This means the group can be agnostic to how deeply nested it is, improving reusability of groups.	9 years ago
Kegan Dougal	5115346297	Add instant_messaging module; modify batesian section rules Previously, all `m.room.*` events were wodged into `{{room_events}}` which isn't great when you want to pull specific ones out. Batesian had a 1:1 mapping of `render_foo()` to a section `{{foo}}`, and having to constantly add functions for new types is a PITA. Batesian now supports returning a `dict` instead of a section `string` where the keys are the `{{foo}}` and the value is what will be inserted. Also add conflicting section key checks to avoid multiple definitions of the same `{{foo}}`. Define dicts for event schemata and swagger HTTP APIs. Using this new feature, split out the instant messaging stuff from the events section, and replace `{{room_events}}` with a list of specific events e.g. `{{m_room_member_event}}`.	9 years ago
Kegan Dougal	5b134119bd	Add presence module; fix relative title bug If a relative title appeared after an HTTP API table, it would insert the wrong level because it thought that part of the table was a title.	9 years ago
Kegan Dougal	b49cb57fe5	Move events sections to CS API	9 years ago
Kegan Dougal	0c0ac3e814	Fix common event fields template to use subtitle char	9 years ago
Kegan Dougal	e8cdfcbba2	Rename spec files to not have numbers everywhere; update targets.yaml	9 years ago
Kegan Dougal	f71763b0d3	Implement relative title styles Templates don't know at what level they will be inserted. Previously, we hard-coded the title style which is not compatible with the build target system. Define a set of styles which will be replaced by the gendoc script when it encounters them: '<' : Make this title a sub-heading '/' : Make this title a heading at the same level '>' : Make this title a super-heading The build target system is now basically complete and functioning.	9 years ago
Kegan Dougal	067363c629	Get the desired title levels right; print out the actual level used to stdout	9 years ago
Kegan Dougal	8590cc84b5	Process and extract targets in gendoc.py	9 years ago
Kegan Dougal	568982ee2e	Represent nested deps in targets.yaml along with title styles This will allow us to programatically position .rst snippets anywhere which will for once and for all remove the horrid title level mismatch bugs. We require this in order to allow people to re-shuffle the spec without having to adjust the spec itself (e.g. 2 targets with different levels of nesting).	9 years ago
Kegan Dougal	703f913a47	Add a 'targets.yaml' files in /specification We're well beyond the point now where a simple `cat` of .rst files to "build" the spec is practical. We may want to slice and dice the spec in different ways to address various cross-cutting concerns. To this end, there is now a 'targets' file which contains the "build targets" for the spec, which contains the sorting order for the .rst files. For now, we just have a single target: 'main'.	9 years ago

1 2

89 Commits (17e634d78a7d5347171033b429668727f46069de)