Skip to content
This repository has been archived by the owner on Oct 26, 2022. It is now read-only.

How do I invalidate the cache if my object is changed #70

Open
deepakmahakale opened this issue Mar 13, 2020 · 1 comment
Open

How do I invalidate the cache if my object is changed #70

deepakmahakale opened this issue Mar 13, 2020 · 1 comment
Assignees
@thebadmonkeydev
Labels
enhancement New feature or request

Comments

@deepakmahakale
Copy link

Is your feature request related to a problem? Please describe.
I am using graphql with graphql-cache.

But now I want to invalidate the cache if my object is changed

Describe the solution you'd like
It will be better if we can just call a method in the after_commit callback and invalidate the cache of related records
@deepakmahakale deepakmahakale added the enhancement New feature or request label Mar 13, 2020
@macdonaldr93
Copy link

Hey! Has anyone been able to look into this? I need something similar. I know after a given mutation has fired to expire the cache but I'm not seeing an API to do that.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@thebadmonkeydev thebadmonkeydev

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@macdonaldr93 @thebadmonkeydev @deepakmahakale