Mention swagger. Clarify how event type template vars are formed.
This commit is contained in:
parent
c2fc1a2fb1
commit
643468e914
1 changed files with 13 additions and 7 deletions
|
@ -19,16 +19,22 @@ subsections. The section is intended to document the "common shared event
|
||||||
structure" between client and server. Deviations from this shared structure
|
structure" between client and server. Deviations from this shared structure
|
||||||
should be documented in the relevant behaviour section.
|
should be documented in the relevant behaviour section.
|
||||||
|
|
||||||
example.event.type
|
m.example.event.type
|
||||||
~~~~~~~~~~~~~~~~~~
|
~~~~~~~~~~~~~~~~~~~~
|
||||||
There should be JSON Schema docs for this event. You can insert a template like
|
There should be JSON Schema docs for this event. Once there is JSON schema,
|
||||||
so:
|
there will be a template variable with dots in the event type replaced with
|
||||||
|
underscores. You can insert a template like so:
|
||||||
|
|
||||||
{{example_event_type_event}}
|
{{m_example_event_type_event}}
|
||||||
|
|
||||||
Client behaviour
|
Client behaviour
|
||||||
----------------
|
----------------
|
||||||
List any new HTTP endpoints. List the steps the client needs to take to
|
List any new HTTP endpoints. These endpoints should be docced using Swagger. You
|
||||||
|
can insert a template for swagger docs like so:
|
||||||
|
|
||||||
|
{{name-of-yaml-file-without-file-ext_http_api}}
|
||||||
|
|
||||||
|
List the steps the client needs to take to
|
||||||
correctly process this module. Listing what data structures the client should be
|
correctly process this module. Listing what data structures the client should be
|
||||||
storing to aid implementation is recommended.
|
storing to aid implementation is recommended.
|
||||||
|
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue