Stefan Dirix

@manmal Are you still using JSON Forms and are you still experiencing this issue with the latest JSON Forms 3.0?

@manmal Thanks for the update. @LukasBoll please check the minimal reproduction in the [first post](https://github.com/eclipsesource/jsonforms/issues/1754#issue-896030145), update to the latest JSON Forms and verify whether the reported performance problems are fixed.

I can also recommend [`fast-json-patch`](https://www.npmjs.com/package/fast-json-patch) to calculate a diff between the old and the new data. Using this you get a nice description of what actually changed with each update.

I'll close this issue for now as there are some workarounds like `fast-json-patch` which can be used for this. For the foreseeable future we'll not support more detailed change notifications.

This is now supported via the new `additionalErrors` feature for JSON Forms 3.0. In case errors need to be modified the validation can be run outside of JSON Forms and...

I'll close this issue for now as there is no more discussion going on. In general JSON Forms can be combined with any kind of UI framework. Feel free to...

In my understanding this issue should now be gone thanks to our many rerendering improvements for JSON Forms 3.0. Updating the JSON Schema with for example `lodash fp/set` and handing...

> I'm not sure what's the best approach for implementing this. We could adapt the core and introduce another validation mode, e.g. showOnChange. This way the behavior could be implemented...

I'll close this for now as the Vuetify issues are tracked in another repository. See [here](https://github.com/eclipsesource/jsonforms-vuetify-renderers/issues/44) for the corresponding issue there.

This seems to be related to https://github.com/eclipsesource/jsonforms/issues/1760 @LukasBoll Can you verify whether this is the same issue?