Martin Maroši
Martin Maroši
@zgover can you provide a simple example?
Ah, I see. There should be similar functionality on the submit event. This would basically fall into the global validation category but instead of evaluating it client-side function, we would...
The validation engine is available even now. It's just not prepared to "consume" schema but only a field state.
@yhrchan The issue number will be fixed in the next release (should be published soon) The second issue is caused when a field with a duplicate name is added to...
@GilbertCherrie I think this is not bug, but the schema is not correct. You can take a look at this example: https://codesandbox.io/s/smoosh-firefly-4uwjx3?file=/src/App.js It uses the exact same schema as the...
So the rendering performance seems solid. Looking at the profiler, the only time when multiple fields are re-rendered in the same cycle is when a condition is met/broken which makes...
@msageryd sorry for the silence (weekend). Going through the changes now.
> I decided that FormFieldConditionWrapper should be removed. The condition data is already available in uiState in context and used as input to FormFieldHideWrapper This might cause issues with the...
> **Do you want the conditions collection to be an object or an array?** From the development point of view, the object is preferable. But the order of execution is...
> @Hyperkid123 I can't find any repo for the documentation. Thought I'd update the docs for the new conditions schema. its the `react-renderer-demo` package (I know what an intuitive name...