Handle defaults of updateOnSdk props, when non boolean values are provided#219
Merged
Conversation
…ly when other values than boolean was provided
gthea
approved these changes
Dec 4, 2024
Refactor for React Strict Mode
|
SonarQube Quality Gate
|
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 SDK
What did you accomplish?
updateOn***object parameters of theuseSplitClientanduseSplitTreatmentshooks, and their components and HOCs alternatives, which were not defaulting totruewhen a non-boolean value was provided.How do we test the changes introduced in this PR?
Extra Notes