Fix apollo cache warning for framework configs #91
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.
Problem
Apollo is showing a cache warning in production when updating Framework configs:
This occurs because Apollo doesn't know how to safely merge the
configsarray field when updates occur, potentially causing unnecessary network requests.Solution
Added a merge function in the Apollo cache configuration to explicitly handle updates to the Framework's
configsfield. Since our queries always return the complete list of configs, we can just replace the existing data with incoming data.Also added a GQL fragment for
FrameworkConfigqueries.