📝 Clarify "Required, can be None" query parameter docs#15496
Open
Sanskar121543 wants to merge 1 commit into
Open
📝 Clarify "Required, can be None" query parameter docs#15496Sanskar121543 wants to merge 1 commit into
Sanskar121543 wants to merge 1 commit into
Conversation
Contributor
📝 Docs previewLast commit c33f807 at: https://e02357cb.fastapitiangolo.pages.dev Modified Pages |
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
1 participant
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.
Summary
Clarifies the wording in the "Required, can be
None" section of the query parameter validation docs.The previous wording implied that clients could directly send Python
Nonevalues in HTTP query parameters, which can be confusing because query parameters are transmitted as strings.This update clarifies that:
NoneChanges
Updated wording in:
docs/en/docs/tutorial/query-params-str-validations.mdRelated
Related to issue #12419