Skip to content

When enum is used as argument, its default value is not validated against enum definition #122

@rafalp

Description

@rafalp

Hello!

While working on enum support in Ariadne I've found that enums values aren't validated against GraphQL enum when they are defined as fields on GraphQL schema.

Following schema passes validation:

enum Role {  ADMIN  USER } type Query { hello(r: Role = ADMIN): String complex(i: Test = { role: INVALID }): String complexAlt(i: Test): String } input Test { ignore: String role: Role = INVALID }

I would've expected schema validators to raise INVALID, but instead those fields are quietly excluded from default value passed to field's resolver.

Metadata

Metadata

Assignees

Labels

pendingWaiting for other issues to move forwardupstreamShould be solved or discussed upstream

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions