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.

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

Use Request.json attribute instead of parsing ourselves #17

Closed
jfinkels opened this issue Mar 8, 2012 · 3 comments
Labels
bug

Comments

@jfinkels
Copy link
Owner

@jfinkels jfinkels commented Mar 8, 2012

Use the Request.json property to get parsed JSON instead of parsing it ourselves. Possible issue: how does that handle invalid JSON?

@jfinkels

This comment has been minimized.

Copy link
Owner Author

@jfinkels jfinkels commented Mar 8, 2012

@jfinkels

This comment has been minimized.

Copy link
Owner Author

@jfinkels jfinkels commented Mar 9, 2012

This would work well if we could change the request class for our API blueprint only, so that our request class would override Request.on_json_loading_failed to return a JSON formatted response instead of an HTML formatted response. This depends on the resolution of pallets/flask#422.

jfinkels added a commit that referenced this issue Mar 6, 2013
jfinkels added a commit that referenced this issue Apr 18, 2013
Uses Flask's Request.json for JSON parsing.
jfinkels added a commit that referenced this issue May 18, 2013
Uses Flask's Request.json for JSON parsing.
jfinkels added a commit that referenced this issue Jan 8, 2014
Uses Flask's Request.json for JSON parsing.
@jfinkels

This comment has been minimized.

Copy link
Owner Author

@jfinkels jfinkels commented Jan 11, 2014

A fix has been merged.

@jfinkels jfinkels closed this Jan 11, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant
You can’t perform that action at this time.