Implement OptionalFromRequest for Form and RawForm
#3355
Conversation
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.
Motivation
This change enables the use of Form as an optional extractor in certain scenarios.
Solution
This PR implements
OptionalFromRequestforFormandRawForm. The behavior is as follows:GETorHEADrequests, if there are no query parameters, the extractor will returnNone. Otherwise, it will parse the form data using the original logic.Content-Typeheader is not present, the extractor will returnNone. Otherwise, it will parse the form data using the original logic.Additionally, the
FromRequestimplementation forRawFormdoes not include a check for theHEADmethod. I believe this is a bug, asFormandRawFormshould behave consistently. Is this understanding correct?