We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hello,
An idea that would be nice: the ability to set the GET param names in settings. Something like the default:
DRF_DYNAMIC_FIELDS_GET_NAMES = ['fields', 'omit]
Which could be overriden in the local settings with something like:
DRF_DYNAMIC_FIELDS_GET_NAMES = ['__fields', '__omit]
So that the risk of the GET param colliding with model fields named "fields" and "omit" is minimised when using drf_dynamic_fields alongside https://github.com/carltongibson/django-filter, for example.
Thanks!
The text was updated successfully, but these errors were encountered:
Sounds like a nice idea. Although a dictionary for configuration would probably be better:
DRF_DYNAMIC_FIELDS = { 'GET_PARAMETERS': { 'fields': '__fields', 'omit': '__omit', }, }
Pull requests (including tests and documentation) are welcome. If someone has any questions regarding implementation, feel free to ask!
Sorry, something went wrong.
No branches or pull requests
Hello,
An idea that would be nice: the ability to set the GET param names in settings. Something like the default:
Which could be overriden in the local settings with something like:
So that the risk of the GET param colliding with model fields named "fields" and "omit" is minimised when using drf_dynamic_fields alongside https://github.com/carltongibson/django-filter, for example.
Thanks!
The text was updated successfully, but these errors were encountered: