-
Notifications
You must be signed in to change notification settings - Fork 1
feat: support custom directives #134
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
# Conflicts: # bun.lock # package.json
ffd0eb6
to
acddaed
Compare
return `@GraphQLDirective( | ||
name = "${titleCase(directiveName)}", | ||
description = "${node.description?.value ?? ""}", | ||
locations = [${node.locations.map((location) => `graphql.introspection.Introspection.DirectiveLocation.${location.value}`).join(", ")}] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it doesn't really matter all that much, but why inline the imports?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just easier than manually adding the imports to the top of the file which would require adding them to the extraImports
config
🎉 This PR is included in version 3.9.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
📝 Description
@GraphQLDirective
annotation classes for custom directives specified via config.