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

Support BadRequest(ModelState) overload content type in default deserializers #73

Closed
Beffyman opened this issue Mar 5, 2019 · 1 comment
Closed

Support BadRequest(ModelState) overload content type in default deserializers #73

Beffyman opened this issue Mar 5, 2019 · 1 comment
Assignees
@Beffyman
Labels
bug Something isn't working
Milestone
1.0.0

Comments

@Beffyman
Copy link
Owner

Beffyman commented Mar 5, 2019

Content Type for the overload is not supported by default, it should be supported as the overload seems like a common use case.
@Beffyman Beffyman added the bug Something isn't working label Mar 5, 2019
@Beffyman Beffyman added this to the 1.0.0 milestone Mar 5, 2019
@Beffyman Beffyman self-assigned this Mar 5, 2019
Beffyman added a commit that referenced this issue Mar 5, 2019
@Beffyman
fixes for #73, #74
4e47564
@Beffyman Beffyman mentioned this issue Mar 5, 2019
Merged
Beffyman added a commit that referenced this issue Mar 5, 2019
@Beffyman
Feature/response type issues (#76)
ccd87d5 
#73
#74
0.17.1
@Beffyman
Copy link
Owner Author

Beffyman commented Mar 5, 2019

This will also fix the content type errors from DataAnnotation attribute failures on requests, application/problem+json will be handled by the default handler

@Beffyman Beffyman closed this as completed Mar 5, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Beffyman Beffyman

Labels
bug Something isn't working
Projects
None yet
Milestone
1.0.0
Development

No branches or pull requests
1 participant
@Beffyman