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
Create readme that must be updated every time a new endpoint is created.
Simple:
Alternatively, we could add all existing endpoints and new endpoints to the fastapi webserver, meaning they would show up in the swagger docs. However, this goes against the nice plugin architecture we have.
Experimental:
I will also investigate dynamically creating the swagger docs based on the plugin definitions. This would require each plugin to define a request and response model (which could get passed through into fastapi). Would require the http decorator issue.
The text was updated successfully, but these errors were encountered:
I would like autogenerated swagger, so option 3 sounds like a good one to explore. Might need option 1 for now, just in case we never get 3 and end up with a mammoth docs task.
Basic:
Create readme that must be updated every time a new endpoint is created.
Simple:
Alternatively, we could add all existing endpoints and new endpoints to the fastapi webserver, meaning they would show up in the swagger docs. However, this goes against the nice plugin architecture we have.
Experimental:
I will also investigate dynamically creating the swagger docs based on the plugin definitions. This would require each plugin to define a request and response model (which could get passed through into fastapi). Would require the http decorator issue.
The text was updated successfully, but these errors were encountered: