Gustavo Fenilli
Gustavo Fenilli
This is not a bug, it is how schema and the call order works, the example with schema is using both schema and the form component, meaning it is not...
The reproduction not working has nothing to do with being a pro input, pro inputs work by default in the playground, the reason being is that i18n as a library...
This was already answered a lot in the discord, we probably should make a better example of it in the docs for custom components, but the case is a custom...
Yes I would consider that a bug, file types should not keep values from the LocalStorage plugin.
I would say that FormKit does a lot more than an actual native input, like child/parent communication, so large datasets might have a lot of fn calls, not sure how...
Looking loosely into it, I think [this](https://github.com/formkit/formkit/blob/8e2e3c581891e551cce895214cdf87dfb3ccc4d2/packages/addons/src/plugins/multiStep/multiStepPlugin.ts#L292) would need to be awaited for the node to be settled, otherwise it might be still running the validations. What do you think...
That would be correct, it does not know that the value to show is and after options it does not make any changes to the value itself. You can write...
the slot `tabLabel` is at the step not at the multi-step component.