Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Remove error log when parsing malformed JSON body #1351

Merged
merged 1 commit into from
Jun 12, 2020
Merged

Remove error log when parsing malformed JSON body #1351

merged 1 commit into from
Jun 12, 2020

Conversation

dbanty
Copy link
Contributor

@dbanty dbanty commented Apr 29, 2020

Addresses #1350

@codecov
Copy link

codecov bot commented Apr 29, 2020 •
edited
Loading

Codecov Report

Merging #1351 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff            @@
##            master     #1351   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files          226       226           
  Lines         6785      6784    -1     
=========================================
- Hits          6785      6784    -1
Impacted Files Coverage Δ
fastapi/routing.py 100.00% <ø> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 4e77737...4b6e221. Read the comment docs.

@tiangolo tiangolo merged commit 2351fb5 into fastapi:master Jun 12, 2020
@tiangolo
Copy link
Member

Yep, good point. Awesome, thank you! 🚀 🎉 ☕

@tiangolo tiangolo mentioned this pull request Jun 12, 2020
Closed
@dbanty dbanty deleted the patch-1 branch June 12, 2020 21:00
hyahiaoui pushed a commit to hyahiaoui/fastapi that referenced this pull request Aug 1, 2020
@dbanty @hyahiaoui
🔇 Remove error log when parsing malformed JSON body as it's a client …
b2e5863 
…error (fastapi#1351)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
2 participants
@dbanty @tiangolo