feat: force enable query analyzer #270
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…L Smart Cache, even if debug mode is off
josephfusco
approved these changes
Feb 7, 2024
This was referenced Feb 7, 2024
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 force enables the GraphQL Query Analyzer when WPGraphQL Smart Cache is active.
In v1.20.0 of WPGraphQL the GraphQL Query Analyzer became optional, causing some users of WPGraphQL Smart Cache to lose the X-GraphQL-Keys header used by cache tagging and cache invalidation.
This force enables the Query Analyzer when using WPGraphQL Smart cache, ensuring that the keys are generated and output in the headers.
Closes: #269 #268
Related:
graphql_should_analyze_queriesas setting wp-graphql#3008