Describe the Bug
I replace an event (i.e. a boundary event) from interrupting to non-interrupting. I see that the global message reference gets lost.
We have existing test cases for the desired behavior (reference is kept), but due to nested it(..., function() { it(...); } calls these are not actually executed 🙈.
#2248 uncovered this miss-use, and the bug.
Steps to Reproduce
- Uncomment these tests
- See that test suite fails
Expected Behavior
When replacing an event (toggling interrupting / non-interrupting) we keep the global element reference.
Environment
- Browser: Any
- OS: Any
- Library version: v17.1.0
Related to #1906
Describe the Bug
I replace an event (i.e. a boundary event) from interrupting to non-interrupting. I see that the global message reference gets lost.
We have existing test cases for the desired behavior (reference is kept), but due to nested
it(..., function() { it(...); }calls these are not actually executed 🙈.#2248 uncovered this miss-use, and the bug.
Steps to Reproduce
Expected Behavior
When replacing an event (toggling interrupting / non-interrupting) we keep the global element reference.
Environment
Related to #1906