Swagger feature docstring (and spec?) places tags on route-data root:
https://github.com/metosin/reitit/blob/master/modules/reitit-swagger/src/reitit/swagger.cljc#L55
Examples place tags key under swagger:
https://github.com/metosin/reitit/blob/master/examples/ring-swagger/src/example/server.clj#L30
Both seem to generate proper swagger.json, but first one fails spec validation. Why? Sp
The Generated Client API is remains largely undocumented...
It would also be awesome if we could include the documentation of the API in the Generated DSL
While converting the developer docs docuemnt to markdown I stumbled
upon the envvar directive. I think it would be nice to use that generally,
but it needs some work. For one all variables from environment.rst show
up as second level TOC entries in the main navigation now. Which is something
we do not want. The developer docs should also use the referencing mechanism
and maybe we want to add a
Currently the model namespace keeps track of registered models and creates maps for "quick" mapping (e.g. mapping a model field to table column). This is mainly for performance benefits.
These maps are stored in atoms. However it might be nice to actually store then in `^:dy
Add a description, image, and links to the data-driven topic page so that developers can more easily learn about it.
To associate your repository with the data-driven topic, visit your repo's landing page and select "manage topics."
Use case
As a user, I would like to see the service name and the timestamp also on the details page of a sequence execution.
Details
of cartsis inserted between the sequence name and status. ->delivery of carts succeeded