We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Currently WPGraphQL Smart Cache listens for changes to meta, and triggers purge events for the node that was updated.
A lot of plugins update meta a lot more then it seems like they should leading to more purge requests than expected.
Instead of default behavior to listen to all meta changes, I think the default should be to not track meta and instead make it opt-in.
Users must provide meta key(s) or other criteria that should be met for meta to individually be tracked for purge events.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Currently WPGraphQL Smart Cache listens for changes to meta, and triggers purge events for the node that was updated.
A lot of plugins update meta a lot more then it seems like they should leading to more purge requests than expected.
Instead of default behavior to listen to all meta changes, I think the default should be to not track meta and instead make it opt-in.
Users must provide meta key(s) or other criteria that should be met for meta to individually be tracked for purge events.
The text was updated successfully, but these errors were encountered: