feat: determine LP reference and RTE paths during query resolution #214
Conversation
This file contains hidden or 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
Staging -> master [Bug Fix: Multiple stack import failing]
Deepak-Kharah
previously approved these changes
Jan 12, 2024
Contributor
Deepak-Kharah
left a comment
Deepak-Kharah
left a comment
There was a problem hiding this comment.
Change looks good!
Contentstack-AnkitaD
approved these changes
Jan 16, 2024
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.
As of 5.1.2, for live preview, we determine all possible reference paths and JSON RTE paths at runtime by fetching content types and recursively iterating over them. For very complex content types, this process results in a lot of reference paths caching which becomes impossible.
This change adds a new custom field
cslp__metato each content type node, which resolves with the value of reference paths and JSON RTE paths. This leads to a significant improvement in speed, as no expensive runtime calculation has to be done.To resolve
cslp__meta, we iterate over the content types and the Gatsby query (using theinfoargument of the resolver -info.operation) and collect the reference and RTE paths.