Fix OpenAPI spec partitioning - #3824
Open
rhysyngsun wants to merge 3 commits into
Open
Conversation
rhysyngsun
force-pushed
the
nl/fix-drf-versioning-split
branch
from
August 6, 2026 02:06
b831a4e to
c007482
Compare
OpenAPI ChangesShow/hide changes |
cp-at-mit
approved these changes
Aug 6, 2026
Contributor
Author
|
Will rebase and merge on Monday. |
This file contains hidden or 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
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.
What are the relevant tickets?
N/A
Description (What does it do?)
This is a long-standing issue I tried to fix 6 months ago and it lead to some whack-a-mole regressions. Things seem to be better now so trying to get this addressed again. Up until now our openapi specs contain all the APIs because the namespacing strategy was configured with an incorrect key and so ignored. This fixes that and also patches around a few oddities of how some versioned APIs are defined by using explicit version classes.
How can this be tested?
The APIs defined in each of the versioned schemas should be limited to APIs for that version and no extraneous non-versioned APIs should appear either.