📝 Update docs for Query Params and String Validations, remove obsolete Ellipsis docs (...
)
#13377
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.
📝 Update docs for Query Params and String Validations, remove obsolete Ellipsis docs (
...
)Pydantic and FastAPI discourage the use of Ellipsis (
...
) for a while now, any code using Ellipsis should be updated to instead not have any default parameter, which conveys the same meaning of making the parameter required.The docs have been updated to not use nor recommend Ellipsis and instead use the more modern and supported form (just not declaring a default value).
The old examples were targetting Pydantic v1 only, and were not tested, so this hasn't been fully supported for a while.
This also updates and modernizes those same docs, to use the newer version of the syntax in the examples, prioritizing Python 3.10+.