Start warning if `fields` or `exclude` are not defined on `DjangoObjectType`
See original GitHub issueSo that model fields aren’t accidentally exposed through DjangoObjectType I propose that we start warning if either fields
or exclude
aren’t defined with the intention to error completely in the future. This would also align the API more with Django Rest Framework which hopefully makes it more familiar to most developers.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:6 (5 by maintainers)
Top Results From Across the Web
graphene-django: 'Meta.model' without either 'Meta.fields' or ...
Specify the filter_fields attribute in the PatientType.Meta as class PatientType(DjangoObjectType): class Meta: model = Patients exclude ...
Read more >Graphene Documentation - Read the Docs
Setting neither fields nor exclude is deprecated and will raise a warning, you should at least explicitly make. DjangoObjectType include all ...
Read more >Queries & ObjectTypes - Graphene-Python
DjangoObjectType will present all fields on a Model through GraphQL. If you only want a subset of fields to be present, you can...
Read more >field_name - django-filter - Read the Docs
The name of the model field that is filtered against. If this argument is not provided, it defaults the filter's attribute name on...
Read more >Developing Apps - Nautobot Documentation
This documentation covers the development of custom apps (plugins) for Nautobot. ... Use a Development Environment, Not Production For App Development.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Great. I will start working on it tomorrow. You can assign me to the issue, @jkimbo .
@radekwlsk if you have the time that would be great! I don’t think anyone is working on it at the moment.