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

add more granular control over content negotiation #31

Open

4 tasks

DanielSchaffer opened this issue Feb 28, 2019 · 0 comments

Open

4 tasks

add more granular control over content negotiation #31

DanielSchaffer opened this issue Feb 28, 2019 · 0 comments

Labels

@dandi/http-pipeline feature good first issue

Contributor

DanielSchaffer commented Feb 28, 2019 •

edited

Loading

add @Accept() decorator, which can take one or more MIME type strings as input
@Accept() can be applied at controller or method level
With no @Accept(), any configured renderer will be used
With @Accept(), content type rendering will be limited to the route's specified content types

Depends on #24

The text was updated successfully, but these errors were encountered:

DanielSchaffer added @dandi/mvc feature labels

DanielSchaffer added @dandi/http-pipeline good first issue and removed @dandi/mvc labels

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment