-
Notifications
You must be signed in to change notification settings - Fork 345
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
redis cache issues #1130
Comments
Could you try with this canary version? |
That looks to have solved the first issue. I'm still having problems with aliases, though. |
Looking at the difference, I see that the following fields are in the initial result but not the cached result:
Since symbols can't be stringified, this makes sense that they're getting left out. I wonder if the alias information is somehow being stored in these fields that are getting discarded. I am using a custom transform that uses @graphql-tools/stitch to transform the schema, so maybe that has something to do with it. |
@jakeblaxon We're having this alias issue also, did you find any workaround or solution to this bug? |
@jackedgson I ended up using the One note: I'm using
This was from a while ago, though, so they may have fixed it by now. |
Did you try the canary version I mentioned here? |
Closing the issue due to the inactivity. Feel free to create a new one if the issue persists. |
Co-authored-by: Renovate Bot <bot@renovateapp.com>
Hello, I've noticed two issues when trying to use the redis-cache plugin:
get
andset
commands don't parse and stringify the values correctly. For example, we pass an object instead of a string as the value to redis'sset
command, which causes it to error out.Let me know if you have any questions. Thanks!
The text was updated successfully, but these errors were encountered: