Providing Form with new schema with updated property appears to have no effect in specific case.

Describe the bug I am attempting to have a schema property start as <input type=text /> and change to <select /> after an async call is completed. I am essentially looking to achieve this effect in the gif below:

• ❌ Providing new schema property to <Form /> component seems to have no effect if changing a property from { type: 'string' } to { type: 'string', oneOf: [] } (<input type=text /> to <select />).
• ✅ If the property name changes between schema updates the UI will update.
• ✅ If the Form is unmounted between the schema updates the form UI will update.

To Reproduce Please see this CodeSandbox for code that reproduces the behavior I described. In the CodeSandbox I am switching between two schemas every second, but only the <input type="text" /> is rendered. See the console for when these updates are occurring since it can kind of look like just a static page.

I have achieved the effect in the gif above by changing the property name from model to modelz (see second ✅ above).

Should this work this way or is this functioning as expected?

[joepuzzo]

Ok also if your curious for conditional schema stuff there may be stuff you need here: https://teslamotors.github.io/informed/?path=/story/conditionals--conditional-props-schema

[shelbyspeegle]

Feel free to close - we can work around unless you see this as a feature you want to work to add 👍