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
Our official documentation refers to a number type for the value argument (see docs). However, we can in fact support both string and number (and that's what we defined when migrating to TypeScript and helped us figure out the issue - see PR). Plus, the documentation also mentions that the value should be updated using the update function argument, which for now only returns a string.
It seems we have a wobbly API for our component, as it requires us to parse the value returned by the update function before using it to set our new value.
Our official documentation refers to a
number
type for thevalue
argument (see docs). However, we can in fact support bothstring
andnumber
(and that's what we defined when migrating to TypeScript and helped us figure out the issue - see PR). Plus, the documentation also mentions that thevalue
should be updated using theupdate
function argument, which for now only returns astring
.It seems we have a wobbly API for our component, as it requires us to parse the value returned by the
update
function before using it to set our newvalue
.A suggestion could be the following:
Note that if the suggestion is accepted and implemented, it will be a breaking change.
The text was updated successfully, but these errors were encountered: