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
GraphQL-Faker throws an error when running on a schema that contains a @deprecated directive on an input field. However that is now supported by the graphql-spec, see: graphql/graphql-spec#805
Logs:
graphql-faker |
graphql-faker | Your schema constains 2 validation errors:
graphql-faker |
graphql-faker | Directive "deprecated" may not be used on INPUT_FIELD_DEFINITION.
graphql-faker |
graphql-faker | schema.sdl:261:19
graphql-faker | 260 | description: description_String_maxLength_2200
graphql-faker | 261 | active: Boolean @deprecated(reason: "this field will soon be replaced by the status field")
graphql-faker | | ^
graphql-faker | 262 | draft: Boolean @deprecated(reason: "this field will soon be replaced by the status field")
graphql-faker |
graphql-faker |
graphql-faker | Directive "deprecated" may not be used on INPUT_FIELD_DEFINITION.
graphql-faker |
graphql-faker | schema.sdl:262:18
graphql-faker | 261 | active: Boolean @deprecated(reason: "this field will soon be replaced by the status field")
graphql-faker | 262 | draft: Boolean @deprecated(reason: "this field will soon be replaced by the status field")
graphql-faker | | ^
graphql-faker | 263 | expiresAt: String
graphql-faker |
The text was updated successfully, but these errors were encountered:
I run into the same problem. I've tried @Xample solution but it gives me following error: Directive "deprecated" already exists in the schema. It cannot be redefined.. Worth pointing that this directive is not declared anywhere else. I've put the declaration as the first thing is the schema file. Any workaround?
GraphQL-Faker throws an error when running on a schema that contains a
@deprecated
directive on an input field. However that is now supported by the graphql-spec, see: graphql/graphql-spec#805Logs:
The text was updated successfully, but these errors were encountered: