You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now it's very confusing when to pass an unmasked value or a masked value to the component. I'm thinking it would be better if users of the component were explicit about which value they cared to work with. An API I think might be good would be something like this:
In this scenario the developer passed the maskedValue in and so the update action would return the maskedValue as the first argument and the unmaskedValue as the 2nd argument.
In this scenario the developer passed the unmaskedValue in and so the update action would return the unmaskedValue as the first argument and the maskedValue as the 2nd argument.
It would be an error to pass both the unmaskedValue and maskedValue to the component.
We would deprecate passing value in as a positional param to help move developers to being explicit about which type of format they want to use.
The text was updated successfully, but these errors were encountered:
Right now it's very confusing when to pass an unmasked value or a masked value to the component. I'm thinking it would be better if users of the component were explicit about which value they cared to work with. An API I think might be good would be something like this:
In this scenario the developer passed the
maskedValue
in and so theupdate
action would return themaskedValue
as the first argument and theunmaskedValue
as the 2nd argument.In this scenario the developer passed the
unmaskedValue
in and so theupdate
action would return theunmaskedValue
as the first argument and themaskedValue
as the 2nd argument.It would be an error to pass both the
unmaskedValue
andmaskedValue
to the component.We would deprecate passing
value
in as a positional param to help move developers to being explicit about which type of format they want to use.The text was updated successfully, but these errors were encountered: