Add Support for customizing how nested names are generated #305
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
…ames ✨ feat(types.py): add NestedNamingStrategy type alias ✨ feat(spec.py): add nested_naming_strategy parameter to SpecTree constructor and get_model_schema method ✨ feat(utils.py): add get_nested_key function to generate nested model reference names The changes add support for nested model reference names in Spectree. A new type alias, NestedNamingStrategy, is added to _types.py. SpecTree constructor and get_model_schema method in spec.py now accept a new parameter, nested_naming_strategy, which is used to generate nested model reference names. get_nested_key function is added to utils.py to generate nested model reference names.
AndreasBBS
force-pushed
the
refactor/get_model_schema
branch
from
c7d16f7
to
9fbebf0
Compare
kemingy
approved these changes
Apr 24, 2023
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.
In the normal behavior the nested models are suffixed with the parent model name. This merge allows to override that behavior in the
Spectreeclass. For example: