David Robertson c69ac3bb68 Present OpenAPI additionalProperties field ... When looking at the "Authentication Data" type used in e.g. the account deactivation endpoint https://spec.matrix.org/v1.3/client-server-api/#post_matrixclientv3accountdeactivate it was not clear to me that clients and servers should expect additional fields in this structure (the semantics of which are implied by the `type` of the authentication, or that of the previously established `session`.) In the OpenAPI spec, We occasionally mark some ojects as allowing arbitrary additional properties (`additionalProperties: true`, or `additionalProperties: { description: "..."}`). In other places we are more strict and provide a schema that additional properties must satisfy. In this PR we aim to make the first kind of additional properties (non-strict) more visible in the rendered spec.		2022-07-04 21:24:56 +01:00
..
_default	Render a single page of the spec in Hugo	2021-01-12 15:31:01 -08:00
docs	Comments for all the layout templates	2021-01-12 20:45:24 -08:00
partials	Present OpenAPI additionalProperties field	2022-07-04 21:24:56 +01:00
shortcodes	Remove matrix-doc changelog hack (#1134)	2022-06-16 10:45:45 -06:00
404.html	Render a single page of the spec in Hugo	2021-01-12 15:31:01 -08:00