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
Describe the Bug
When I generate the SDL from a set of resolvers which use the @ Directive decorator the directives do not appear in the SDL. I see similar behaviour when running a live graphql server.
I'm not sure whether this is a bug, or whether this is the intended behavior since I couldn't deduce from https://typegraphql.com/docs/directives.html whether directives are supported in the SDL generated by type-graphql, in which case #965 may help clarify. Otherwise it could related to the original issue reported as graphql/graphql-js#1343.
PS: the reason I'm looking for this functionality is so that I can eventually integrate more seamlessly with Apigee which uses a @scope directive to generated the authentication config - https://github.com/apigee/graphql-authz.
# -----------------------------------------------
# !!! THIS FILE WAS GENERATED BY TYPE-GRAPHQL !!!
# !!! DO NOT MODIFY THIS FILE BY YOURSELF !!!
# -----------------------------------------------
type Config {
VERSION: String!
}
type Query {
getConfig: Config!
}
Expected Behavior
I would expect the file contents to contain the directive, e.g.
type Query @auth(requires: USER) {
getConfig: Config!
}
Logs
N/A
Environment:
OS: MacOS 11.4
Node v12.22.1
Package version 1.1.1
TypeScript version 4.3.5
The text was updated successfully, but these errors were encountered:
Uh oh!
There was an error while loading. Please reload this page.
Describe the Bug
When I generate the SDL from a set of resolvers which use the @ Directive decorator the directives do not appear in the SDL. I see similar behaviour when running a live graphql server.
I'm not sure whether this is a bug, or whether this is the intended behavior since I couldn't deduce from https://typegraphql.com/docs/directives.html whether directives are supported in the SDL generated by type-graphql, in which case #965 may help clarify. Otherwise it could related to the original issue reported as graphql/graphql-js#1343.
PS: the reason I'm looking for this functionality is so that I can eventually integrate more seamlessly with Apigee which uses a @scope directive to generated the authentication config - https://github.com/apigee/graphql-authz.
To Reproduce
Compile and run the following code
The text.graphql file has the following contents
Expected Behavior
I would expect the file contents to contain the directive, e.g.
Logs
N/A
Environment:
The text was updated successfully, but these errors were encountered: