feat: add new "graphql_cache_is_object_cache_enabled" filter #178
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds a new
graphql_cache_is_object_cache_inabledfilter that can allow 3rd party developers to dynamically enable/disable the object cache.For example, (as mentioned in #177) a query param in the request, such as
?disable_cachecould be read by this filter and disable the cache for that request.This filter could be used like so: