wholetrans/docs-matrix-spec
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Flatten out v1 and v2_alpha directories

Browse source 
As a side effect, I got rid of all of the horrible symlinks and just put
in all of the proper relative paths. Because the horrible symlinks were
horrible.
This commit is contained in:
Daniel Wagner-Hall 2015-11-30 11:22:57 +00:00
parent 1a4a9af9a7
commit 6c66bfc755
123 changed files with 52 additions and 77 deletions
Download patch file Download diff file Expand all files Collapse all files

6
specification/client_server_api.rst
View file

@ -468,7 +468,7 @@ This section refers to API Version 2. These API calls currently use the prefix
.. _User-Interactive Authentication: `sect:auth-api`_
{{v2_registration_http_api}}
{{registration_http_api}}
Old V1 API docs: |register|_
@ -769,9 +769,9 @@ When the client first logs in, they will need to initially synchronise with
their home server. This is achieved via the initial sync API described below.
This API also returns an ``end`` token which can be used with the event stream.
{{sync_http_api}}
{{old_sync_http_api}}
{{v2_sync_http_api}}
{{sync_http_api}}
Getting events for a room

2
specification/modules/account_data.rst
View file

@ -24,4 +24,4 @@ the tags are for.
Client Behaviour
----------------
{{v2_account_data_http_api}}
{{account_data_http_api}}

2
specification/modules/receipts.rst
View file

@ -52,7 +52,7 @@ dismissing a notification in order for the event to count as "read".
A client can update the markers for its user by interacting with the following
HTTP APIs.
{{v2_receipts_http_api}}
{{receipts_http_api}}
Server behaviour
----------------

2
specification/modules/tags.rst
View file

@ -45,4 +45,4 @@ Two special names are listed in the specification:
Client Behaviour
----------------
{{v2_tags_http_api}}
{{tags_http_api}}