[Purv-Kabaria]

Issue: #957

What I did

NumberType seeds numStr from arg.value?.toString(), so when the panel renders before the story's args are set, the input mounts with value={undefined} (uncontrolled). useResyncValue then sets a string and the input becomes controlled, which logs React's "changing an uncontrolled input to be controlled" warning on web. The input now falls back to '', as suggested in the issue. Added a patch changeset for @storybook/addon-ondevice-controls.

How to test

1. Add a story with a number arg, e.g. args: { value: 5 }.
2. Run the expo example on web and open the story's Controls panel.
3. Before this change, the console shows the uncontrolled-to-controlled warning from NumberType. With it, there's no warning and the control still edits the arg.

No new example or docs needed.

[changeset-bot]

🦋 Changeset detected

Latest commit: 844b931

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 9 packages

Name	Type
@storybook/addon-ondevice-controls	Patch
@storybook/addon-ondevice-actions	Patch
@storybook/addon-ondevice-backgrounds	Patch
@storybook/addon-ondevice-notes	Patch
@storybook/react-native-theming	Patch
@storybook/react-native-ui-common	Patch
@storybook/react-native-ui-lite	Patch
@storybook/react-native-ui	Patch
@storybook/react-native	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[Purv-Kabaria]

@dannyhw whenever you have a moment, this needs a workflow approval to run CI. It's the fix we discussed in #957. Happy to adjust anything.

[dannyhw]

@Purv-Kabaria approved, thanks for the contribution :)