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
Since that is just one function down from makeSchema and uses the same type, all it requires is adding a new field on the SchemaConfighere and passing it along. I tested it locally, and it works perfectly. The schema gets generated correctly with the directive specification at the top, and the information is passed to the resolvers at info.fieldNodes.directives as graphql-js defines.
It seems deceptively simple for no one to have done it by now, is there a problem with this that happens not to affect my application, or should I open a PR?
The text was updated successfully, but these errors were encountered:
The discussion on issue #53 seems to be about schema directives, so I'm opening a new issue regarding query directives which is also not supported,
It seems quite simple to add this feature by passing an extra field to the
GraphQLSchema
constructor here:nexus/src/builder.ts
Lines 1700 to 1709 in 8e0ce1b
Since that is just one function down from
makeSchema
and uses the same type, all it requires is adding a new field on theSchemaConfig
here and passing it along. I tested it locally, and it works perfectly. The schema gets generated correctly with the directive specification at the top, and the information is passed to the resolvers atinfo.fieldNodes.directives
as graphql-js defines.Here is how it ended up being with this change:
It seems deceptively simple for no one to have done it by now, is there a problem with this that happens not to affect my application, or should I open a PR?
The text was updated successfully, but these errors were encountered: