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 "jsonify(...), 400" instead of custom "jsonify_status_code(400, ...)" #29

Closed
jfinkels opened this issue Mar 27, 2012 · 1 comment
Closed

Comments

@jfinkels
Copy link
Owner

@jfinkels jfinkels commented Mar 27, 2012

pallets/flask#430 provides functionality that is the same as the custom jsonify_status_code function we have written. When Flask 0.9 is released, we should 1. mark that as the minimum required version, and 2. change the code to use the new Flask functionality.

jfinkels added a commit that referenced this issue Sep 3, 2012
jfinkels added a commit that referenced this issue Nov 28, 2012
jfinkels added a commit that referenced this issue Feb 4, 2013
Conflicts:

	flask_restless/views.py
jfinkels added a commit that referenced this issue Mar 6, 2013
jfinkels added a commit that referenced this issue Apr 18, 2013
Uses `jsonify(...), 400` instead of `jsonify_status_code(400, ...)`.
jfinkels added a commit that referenced this issue May 18, 2013
Uses `jsonify(...), 400` instead of `jsonify_status_code(400, ...)`.
jfinkels added a commit that referenced this issue Dec 2, 2013
Uses `jsonify(...), 400` instead of `jsonify_status_code(400, ...)`.
jfinkels added a commit that referenced this issue Jan 8, 2014
Uses `jsonify(...), 400` instead of `jsonify_status_code(400, ...)`.
@jfinkels
Copy link
Owner Author

@jfinkels jfinkels commented Jan 8, 2014

A fix has been merged: 391a327

Loading

@jfinkels jfinkels closed this Jan 8, 2014
jfinkels added a commit that referenced this issue Jan 8, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant