Fix swagger paths #991
Merged
Fix swagger paths #991
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
Removes the v2 prefix that is already in the base URL.
Removes the v2 prefix that is already in the base URL.
* Removes the v2 prefix that is already in the base URL * Fix incorrect names and paths
* Removes the v2 prefix that is already in the base URL * Fix incorrect names and paths
Also added a FIXME for a missing corresponding Swagger path entry for a route.
Also added FIXMEs for missing entries.
Renamed FIXMEs to TODOs.
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.
Uses
router.exsas the source of truth and fixes any inconsistencies between those routes and the swagger path entries.If I have missed any, they will be done in a future PR as this is a good-to-have and non-critical.
There are also some invalid names that have been changed to point to the correct ones.