-
Notifications
You must be signed in to change notification settings - Fork 25.3k
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
Is a text/plain formatter really included? #10103
Comments
@tdykstra @scottaddie please confirm. |
@scottaddie @jfoshee , fixed in #10104 |
The documentation was actually somewhat correct before. |
@rynowak please review this issue and the changes made in https://github.com/aspnet/AspNetCore.Docs/pull/10104/files |
@kirodge is correct. We have Is this actually a feature request? |
Oh, I see this is about input |
@serpent5 This looks like an easy one. |
I believe the current documentation is misleading:
> Use a custom formatter when you want the content negotiation process to support a content type that isn't supported by the built-in formatters (JSON, XML, and plain text).
The
TextInputFormatter
is abstract and does not addtext/plain
as a supported media type. If there is a concrete derived class for plain text please document it here, and update the docs: <https://docs.microsoft.com/en-us/dotnet/api/microsoft.aspnetcore.mvc.formatters.textinputformatter?view=aspnetcore-2.1>As a result, it seems that one does in fact need to add a custom input formatter for plain text. See the
TextPlainInputFormatter
in this Stack Overflow response: <https://stackoverflow.com/a/41798960/483776>Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
The text was updated successfully, but these errors were encountered: