Repository navigation
Allow separate queryset item schema names - #2328
Open
IlyaKhalafi wants to merge 3 commits into
Open
IlyaKhalafi wants to merge 3 commits into
IlyaKhalafi wants to merge 3 commits into
Conversation
Merging this PR will not alter performance
|
This branch has not been deployed
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.
Description
This PR fixes list and item schemas being tied to the same custom name. With this,
submodel_namelets each have its own name while keeping existing naming defaults.Motivation and Context
Fixes #1728.
How Has This Been Tested?
make checkand 55 focused tests passed. The full SQLite suite passed with 1,982 tests, 149 skips and two expected failures. Tests used the bundled pytz timezone data because the host lacksUS/Central, which also fails on unchanged upstream.Checklist