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
Extend type with cacheControl doesn't work #903
Comments
Having the same issue here, any suggestions? |
I'd also tried this. It would be great to proxy a remote schema, such as AppSync which doesn't allow custom directives, and stitch in cacheControl directives to then serve it up via Apollo Server. Sadly I ran into a number of issues. The first being with graphql@14.0.x there is an SDL validation failure when trying to merge for the custom directive which I was unable to get around. After downgrading I then hit the same issue reported here. |
This seems to be a bug within the cacheControl extension support by Apollo. A workaround would be to create a way to enhance using directives as metadata, possibly, for example, automatically copying the directives from the extensionAstNodes to the primary astNode. |
Related, but different, what if you can't even use extend, like with existing fields, as in #451. |
You would use mergeSchemas which should hopefully merge directives... Closing for now as there is no bug in tools... |
Hi people! It's my first issue here, and I have a specific problem encountered on my project using stitching and cache with apollo engine.
We're extending types to add some fields. This is the scenario:
graph/schemas/extend/category.js
The field
services
is a stitching of another server that has a ServiceConnection type. We make the realtionship with Category is acategorySlug
field. But this is not the problem!The result, on the "extensions" property return this:
The
maxAge
of path category it's not set as 1000. I don't know if this is the expected behavior.The text was updated successfully, but these errors were encountered: