Closed barmac closed 9 months ago
Root Cause
I tested this on Output Mappings.
Output mappings are created with the source target being an empty string <zeebe:output source="" target="Output_1" />
.
When we add content and remove it again, the source
property is removed <zeebe:output target="Output_1" />
When we undo to the initial state:
CommandStack
ID | Command
1. ...
2. Add Output Var
------ <-- undo till here
3. Add Content
4. ...
this triggers the change handler that removes the source
property.
New CommandStack
1. ...
2. Add Output Var
5. Remove `source` property
This breaks the redo chain by adding something to the stack. The command with ID 3 in the example can no longer be reached.
The Change handler should not be triggered on Undo, or handle the property being empty correctly.
I can only reproduce this issue in Input/Output fields. Other FEEL enabled fields, such as Task type or Script Tasks FEEL expressions manage the undo stack correctly.
Describe the Bug
Given I type in the FEEL entry, when I press cmd+Z and cmd+Y, in FEEL input, redo stops to work as soon as I reach empty input with undo.
Steps to Reproduce
Expected Behavior
Redo should work.
Environment