Repository navigation
fix(ui-kit): preserve falsy values in getInitialValue and useUiKitState - #1436
Open
swarnendusahu10-dotcom wants to merge 1 commit into
Conversation
This branch has not been deployed
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
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.
Summary
Fixes #1235 by ensuring that valid falsy values (
0,"",false) are preserved during initial value extraction and UI Kit state resolution.Details
useUiKitState.js: Replaced(values && (values[actionId]?.value || initialValue)) ?? initialValuewithvalues?.[actionId]?.value ?? initialValue. The logical OR (||) was inadvertently replacing valid falsy values (like0orfalse) withinitialValue.getInitialValue.js: Replaced the chained short-circuiting expression (&&/||) with explicit property guard clauses. This prevents validinitialValue: 0orinitialValue: falsefrom falling through to subsequent property checks or returningundefined.Verification
initialValue: 0,initialValue: false, andinitialValue: ""correctly return the falsy value instead of falling through toundefined.values[actionId].value = 0retains0and does not fall back toinitialValue.initialValuestill occurs when value isnullorundefined.@embeddedchat/ui-kitbuilds cleanly withrollup -c.develop.