Localized Inputs Break When Value Is Null
See original GitHub issueSummary
LocalizedTextInput
, LocalizedMultilineTextInput
, LocalizedMoneyInput
and LocalizedRichTextInput
all crash when supplied with an undefined or null value
prop.
I am not sure what the expected result would be, since we derive the languages
from the value
prop. So if value
is undefined, we can’t render any inputs as we don’t know which language labels to use?
Issue Analytics
- State:
- Created 4 years ago
- Comments:18 (18 by maintainers)
Top Results From Across the Web
Breaking when a method returns null in the Eclipse debugger
I need to break and investigate when this method returns null. There are many paths and return statements. It is possible to break...
Read more >Terraform 0.12.1 trates "null" as literal value instead of using ...
This issue is about being able to nullify individual input variables and have them use their defaults.
Read more >String claims transformations - Azure AD B2C - Microsoft Learn
The error messages can be localized. ... Determines whether a claim value is equal to the input parameter value. ... Or null, if...
Read more >check the variable is null right a… | Apple Developer Forums
So I want to do this like, if memberData?["login_date"] is null, just do not input a value,. if there is a value, just...
Read more >Dynamic Breaks based on object state
So in other words, when the value you are interested in is about to be unassigned. To accomplish what you want, you would...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
We do provide it as a static function 😉.
So should I close this then?
Another option we have would be to do something like this (example from
LocalizedTextInput
)Then it would not crash when we pass in invalid options. Might have performance implications though?