Add workspaces to OpenAPI spec #634
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Why is this not automated? |
JAORMX
previously approved these changes
Jan 17, 2025
Do you mean the generation, or including routers for generation? |
|
The openapi.json generation, that's right |
|
There's some discussion around cleanest way to do this happening on discord |
lukehinds
approved these changes
Jan 20, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Exposes the workspaces API to the OpenAPI spec.
Also moves the dashboard router under the
/api/v1router, and uses the root FastAPI app to build the OpenAPI spec, which should include all new endpoints.Finally, tidies up the operation IDs for the dashboard endpoints as they were getting ridiculously long.