-
Notifications
You must be signed in to change notification settings - Fork 468
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
clientSchemaDirectives is not working for apollo:codegen since 2.18.0 #1484
Comments
I was running into this issue with the directive @rest(
type: String!
path: String!
method: String
endpoint: String
bodyKey: String = "input"
) on FIELD |
Also have this issue. I don't want to modify local schema because it's downloaded automatically from server. Hack is to append the directive to downloaded schema during the automated process, which is not optimal but works:
|
I get the same issue as @codybrouwers with I have not added |
@evankennedy , the same is happening to me, and I wasn't able to fix. Does anyone know if there's a way of fixing this? |
Just to add to the pile, looks like apollo's own code generator doesn't recognize apollo's own federation directives: Unknown directive "key". There's no reason why I'd have to supply anything external to make apollo's own tool work with their own schema/server and federation spec. |
Hello,
I have a mutation:
And I'm trying to run apollo:codegen with this config:
Intended outcome:
Codegen should come through.
Actual outcome:
How to reproduce the issue:
Add a custom directive to one of your .gql files, add it to
clientSchemaDirectives
, and run apollo:codegen.Versions
apollo@2.18.0
With 2.17.4, it was working without having to specify
Thanks in advance!
The text was updated successfully, but these errors were encountered: