fix/FlatfileProvider - reactiveness to accessToken changes #283
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
…, provider logic is executed to be aware of new value
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.
React Package - In FlatfileProvider, when accessToken prop is updated, provider logic is executed to be aware of new value
Please explain how to summarize this PR for the Changelog:
FlatfileProvider reacts to changes on accessToken value.
Tell code reviewer how and what to test:
Previously, if accessToken initiated with an empty value a later the value was correctly passed, the new value was never considered. Now, if accessToken value is udpated, the provider is reactive to pass this new value to children components and render properly.