You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We need to write an OpenAPI-compliant JSON file to configure the swagger endpoint already in place.
ElysiaJS uses a static analyzer to parse the code and find the endpoints, but it cannot read endpoints with a path containing a wildcard (e.g. '/viticulture/vine-varieties*'), so we have to write the documentation for the table endpoints ourselves.
It should not be too much of a problem, as these endpoints all share the same base output. A LLM should be able to generate all of the missing documentation from a snippet and the list of available paths.
We need to write an OpenAPI-compliant JSON file to configure the swagger endpoint already in place.
ElysiaJS uses a static analyzer to parse the code and find the endpoints, but it cannot read endpoints with a path containing a wildcard (e.g. '/viticulture/vine-varieties*'), so we have to write the documentation for the table endpoints ourselves.
It should not be too much of a problem, as these endpoints all share the same base output. A LLM should be able to generate all of the missing documentation from a snippet and the list of available paths.
https://swagger.io/specification/v2/
https://elysiajs.com/plugins/swagger
The text was updated successfully, but these errors were encountered: