Skip to content

Start warning if fields or exclude are not defined on DjangoObjectType #710

Closed
@jkimbo

Description

@jkimbo

So 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.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions