Skip to content

HTTP_204_NO_CONTENT response to handle None return value #88

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
Merged
merged 1 commit into from
Jan 24, 2018
Merged

HTTP_204_NO_CONTENT response to handle None return value #88

merged 1 commit into from
Jan 24, 2018

Conversation

rainulf
Copy link
Contributor

@rainulf rainulf commented Jan 24, 2018

To resolve #85

@rainulf rainulf mentioned this pull request Jan 24, 2018
Closed
jacebrowning
jacebrowning approved these changes Jan 24, 2018
View reviewed changes
Copy link
Member

@jacebrowning jacebrowning left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice tests!

@jacebrowning jacebrowning merged commit cf9f50c into flask-api:develop Jan 24, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@jacebrowning jacebrowning jacebrowning approved these changes

@auvipy auvipy auvipy approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

No content responses should accept not only an empty string
3 participants
@rainulf @jacebrowning @auvipy