-
-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Form data processed #4351
Form data processed #4351
Conversation
Codecov Report
@@ Coverage Diff @@
## master #4351 +/- ##
==========================================
- Coverage 97.49% 97.48% -0.02%
==========================================
Files 43 43
Lines 8857 8861 +4
Branches 1388 1389 +1
==========================================
+ Hits 8635 8638 +3
- Misses 97 98 +1
Partials 125 125
Continue to review full report at Codecov.
|
I decided to raise a ClientPayloadError if the FormData instance has already been processed. Is this the best Exception or is there something more fitting? I also think this code could break some people's code as even in some of the other tests code broke. Should I add documentation somewhere? |
Change-note is enough, I don't think we should document it additionally. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
(cherry picked from commit 0273535) Co-authored-by: Adam Bannister <adam.p.bannister@gmail.com>
What do these changes do?
A FormData instance keeps track whether it has been processed already. If the instance is sent for a second time then it raises a ClientPayloadError.
Are there changes in behavior for the user?
Will raise an exception if they try to resend a FormData instance.
Related issue number
#4345
Checklist
CONTRIBUTORS.txt
CHANGES
folder<issue_id>.<type>
for example (588.bugfix)issue_id
change it to the pr id after creating the pr.feature
: Signifying a new feature..bugfix
: Signifying a bug fix..doc
: Signifying a documentation improvement..removal
: Signifying a deprecation or removal of public API..misc
: A ticket has been closed, but it is not of interest to users.