7 commits

Author	SHA1	Message	Date
Travis Ralston	25c77ab2d0	Define authorization requirements on federation swagger APIs	2018-08-09 08:37:35 -06:00
Travis Ralston	8dd63388e0	invites consume JSON	2018-08-03 13:58:27 -06:00
Travis Ralston	fcaa299f81	Include information on how invite_room_state works ... This is completely optional, and the events included are up to the sender. Sources: * Structure: d69decd5c7/synapse/handlers/message.py (L896-L904) * What events are recommended: d69decd5c7/synapse/config/api.py (L30-L40)	2018-07-26 08:44:10 -06:00
Travis Ralston	f873bae0cc	Improve documentation for how non-third party invites work ... The details are fairly straightforward. An `event` has been added to the response body because that's what Synapse returns, despite the spec saying otherwise until now: d69decd5c7/synapse/federation/federation_server.py (L339)	2018-07-26 08:44:10 -06:00
Travis Ralston	eaf175056f	Full stops	2018-07-24 10:58:15 -06:00
Travis Ralston	45ec8269e6	Fill out the required fields in all the examples	2018-07-24 10:58:15 -06:00
Travis Ralston	004998b98f	Convert invites to swagger ... The whole section reads like a description for the endpoint, and has been replaced by the swagger definition now (rather than at a later stage). All the same information should be kept.	2018-07-24 10:58:15 -06:00