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
I noticed that all directives at field definitions, (excepted for the @deprecated directive), are lost when a schema is parsed and printed. Essentially, I noticed the following issue:
constgraphql=require("graphql");schema=`directive @custom_directive(a: Int) on FIELD_DEFINITIONtype Object { a : Int @custom_directive(a: 1)}`console.log(graphql.printSchema(graphql.buildASTSchema(graphql.parse(schema))));
# directive @custom_directive(a: Int)onFIELD_DEFINITION
#
# typeObject{
# a: Int
# }
As you can see the @custom_directive gets lost.
Please let me know what you think.
PS: I am using graphql@15.0.0-alpha.2.
The text was updated successfully, but these errors were encountered:
@pmantica1 Thanks for taking the time to report this 👍 @m14t Is absolutely correct this is duplicate of #552 and I fully agree that this is surprising behavior and should fix it.
Thanks for the help on the previous issue!
I noticed that all directives at field definitions, (excepted for the
@deprecated
directive), are lost when a schema is parsed and printed. Essentially, I noticed the following issue:As you can see the
@custom_directive
gets lost.Please let me know what you think.
PS: I am using
graphql@15.0.0-alpha.2
.The text was updated successfully, but these errors were encountered: