You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
All fields that are expandable will get the same serializer names. It's not directly an issue with this library but this causes issues with (for example) schema generation where names -can- be based on serializer class names.
Perhaps include the original serializer name in the generated type name.
This implementation was actually altered in the latest version. The request query params (expand and fields) now get injected via the serializer context, rather than dynamic modification of the serializer class to incorporate them. This seemed less magical/more aligned with the DRF API.
All fields that are expandable will get the same serializer names. It's not directly an issue with this library but this causes issues with (for example) schema generation where names -can- be based on serializer class names.
Perhaps include the original serializer name in the generated type name.
In
views.py:50
change this:The text was updated successfully, but these errors were encountered: