feat: multiple queries per template #61
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
- update LayoutArchive exports - update imports to use LAYOUT_ARCHIVE_QUERY
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
Check out the recent updates to your Atlas preview environment:
Learn more about preview environments in our documentation. |
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 implements the new Template.queries approach supported by FaustJS.
SEE:
Benefits
This is beneficial as it means each query is responsible for fewer nodes and will be invalidated more precisely.
Now, instead of querying for Menus, Global Settings and the posts or post archive data all in one query, these queries can be separated into their own responsibilities and take advantage of better caching / cache invalidation via WPGraphQL Smart Cache.