Regarding v4

[thecodejack]

Hi Team

I see that there is some active development happening for v4 and it seems to be removing final-form. Just wanted to know if there will be any planned major breaking changes?

[rvsia]

Hello, yeah, our goal is to remove the final-form, because there are some issues and the author ignores them. Our framework will be better suited for React and there will be some enhancements over FF. And with more control we can provide more features in the future.

Also, we plan to make the API the same so we do not expect any breaking changes for users that are using DDF according to our documentation. For users, that are using some undocumented (on our page) FF components/mutators, there could be breaking changes but we can work on them.

[Hyperkid123]

@thecodejack so by adding this prop subscribtion={{ pristine: false }} we get rid of the initial 500ms lag. The experience is still not super smooth, but we have 1000 fields in the form so we can expect any miracles.

There is one bottleneck in ddf which we can fix. Take a look at following profiler snapshot:

We have a lot of grey "leaves" if you will. The MUI text field si properly memoized and not renderer. That is good. However if we zoom a bit we can see that there is not ay many "gray" candles as we would like:

As you can see, we still render some internal DDF components, even though it's not required. We have extra renders in SingleField, FormConditionWrapper, FormFieldHideWrapper and the root unmemoized TextField. yes each of them takes about 0.1ms 0.2ms to render, but when we multiply it by 1000, we have roughly 30ms of extra render time. I will create an issue and PR and we shall see if we can get it down even further and make the experience smooth. If that won't help I think we have reached the limit of the state management.

[thecodejack]

Awesome analysis. Thanks for looking into that.

Just wanted to know if you are planning to fix it with v4 State setup or v3's final-form state manager?

[Hyperkid123]

In V3 final form. This is renderer issue which does not change in v4.

[Hyperkid123]

#1016 Here is an issue where we will track the progress. Start working on it today.

[Hyperkid123]

@thecodejack the performance optimizations have been released in version 3.3.2. Feel free to test it and see if the performance in your original use case has improved.