Update Apollo Cache When Updating FM Settings #2385
Merged
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.
Changes
When a user would update the FM settings, for some parts of the Admin Area app, the changes would take effect only if the user would refresh the screen. A simple example is:
This is because the Apollo cache would not get updated with new values (after the form has been submitted and the underlying GraphQL mutation has been successfully completed).
So, once the GraphQL mutation has been completed, now we make sure the Apollo cache is updated with the new values.
How Has This Been Tested?
Manual (will add Cypress).
Documentation
Changelog.