Feature/cached graph #1718
Merged
Feature/cached graph #1718
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
ljeub-pometry
force-pushed
the
feature/CachedGraph
branch
from
a2e68b0 to
1c34cda
Compare
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.
What changes were proposed in this pull request?
Adds support for caching graph updates to file using the new incremental file format.
Why are the changes needed?
Avoid rewriting the entire graph on updates with the new graph cache in the GraphQL server
Does this PR introduce any user-facing change? If yes is this documented?
Adds new public traits (some doc strings but needs fleshing out)
How was this patch tested?
Existing tests and new test for incremental caching
Issues
resolves #1704
Are there any further changes required?
Still TODO: