Fix TypeUtil#isDifferentType
type util
#1787
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes the
TypeUtil#isDifferentType
issue reported through camunda/camunda-bpmn-js#213 (comment).The underlying issue is that
TypeUtil#isDifferentType
would not detect that the transaction entry matches a transaction element. This is due totriggerByEvent=false
on thebpmn:Transaction
, andtriggeredByEvent=undefined
on the menu entry. This leads tofalse === undefined
which isfalse
when it should betrue
.The reason this did not surface yet is that we had distinct entries for transactions and event-subprocesses so that no filtering was ever needed.
We rely on the utility to properly work in connectors land, working around #1786.