Use serializers for simple informational views like "metadata" views #283
Labels
app:resource_registry
enhancement
New feature or request
ready to work
Item is ready to be worked on
Some background in #276
With the latest changes (speculative) I still have the schema outputting this:
This isn't correct / complete, and it can't be unless the view uses a serializer. In these cases, the serializer would just be filled with read-only fields. It would do the same thing it does not, but using the serializer would allow OPTIONS to show the expected keys, and would allow OpenAPI spec to provide information about the format of the response.
The text was updated successfully, but these errors were encountered: