Vinícius Goulart

Make error messages accessible

1

__Describe the Bug__ Currently, `@bpmn-io/form-js` shows errors, but there's nothing connecting these errors to the appropriate fields. This can be achieved by some methods described on this [link](https://www.w3.org/WAI/tutorials/forms/notifications/#inline) __Steps to...

__Is your feature request related to a problem? Please describe__ In order to lazy load values for inputs we need to show a loading state on the inputs in case...

__Is your feature request related to a problem? Please describe__ On Zeebe a user might have a variable of up to 4MB and because of that there might be cases...

Make it possible to change form data after first render

4

__Is your feature request related to a problem? Please describe__ On Zeebe Tasklist if we try to complete a Task that was already completed we receive the updated Task and...

It's impossible to drop new elements in the same row when the screen is too narrow

1

### Describe the Bug When using a narrow screen with large elements it's impossible to drop new elements in the same row ### Steps to Reproduce 1. With a small...

> This is the implementation epic for https://github.com/camunda/product-hub/issues/1756 > Design deliverables: https://github.com/camunda/product-hub/issues/1756#issuecomment-1903648224 ### What should we do? Currently it's very hard to reuse parts of the form when editing big...

### What should we do? In order to make easier to model forms, we should allow copy&pasting form components ### TODO - [ ] The actions should trigger on the...

### What should we do? While releasing 1.7.0 we had issues with [this test](https://github.com/camunda/form-playground/blob/51ee237043b41c8a20464bf26a4c07f210e27a6d/test/spec/CamundaFormPlayground.spec.js#L247). We decided to just skip it for now since it seems to be working correctly on...

### Describe the Bug Properties panel popout editor is wrong  ### Steps to Reproduce 1. Hover over any entry that has a popout editor in the properties panel 2....

### What should we do? Currently the form rendering layer is very coupled with the form mutation layer (`FormFieldRegistry`, `PathRegistry`) and this brings problems with reactivity/difficulty to maintain complex structures...