fix: undo/redo for auto disabling if-return blocks

[BeksOmega]

The basics

• I branched from develop
• My pull request is against develop
• My code follows the style guide
• I ran npm run format and npm run lint

The details

Resolves

#6010

Proposed Changes

Wrap the enable/disable event for the if-return in the same group as the initial move event, so the events get undone together. This is the same way the break/continue block handles this behavior.

Behavior Before Change

Undoing was not possible because the events were not properly grouped.

Behavior After Change

Now the events are properly grouped so undo and redo works.

Reason for Changes

Undo and redo are helpful.

Test Coverage

1. Drag an if-return from the workspace to a procedure. Undo and redo.
2. Drag an if-return from the workspace to a block inside a procedure. Undo and redo.
3. Drag an if-return from the workspace to a disabled block inside a procedure. Undo and redo. Enable the disabled block. Observe how the if-return is enabled.
4. Drag an if-return from a procedure to the workspace. Undo and redo.
5. Drag an if-return from a procedure to a block on the workspace. Undo and redo.
6. Drag an if-return from a procedure to a disabled block on the workspace. Undo and redo. Enable the disabled block. Observe how the if-return is not enabled.

Tested on:

• Desktop Chrome

Documentation

Additional Information

N/A

[alschmiedt]

Can you update this to be "Move event"?

[alschmiedt]

Just curious why don't we need the this.getInheritedDisabled anymore?

[BeksOmega]

I don't think we ever needed it. That would mean that if you dragged an if-return out of a procedure block, and into a disabled block, it wouldn't get disabled itself. Then you could re-enable the disabled parent, and the if-return would get enabled as well, which is not the behavior we want.