Bpmn helper update

[LucasMGo]

Summary

Adapted bpmn-helper module for use in typescript environment. JSDoc comments have been extended and there have been generated declaration files based on these to use in typescript files.

Details

• Updated bpmn moddle to newest version
• Improved jsdoc comments
• Added declaration files for bpmn helper module

[jjoderis]

In some situations like milestones and callActivities we might expect values to exist when the bpmn is valid. But a bpmn might contain a milestone without a name which is not reflected by the current annotations.
Should every value be set to optional that could have an edge-case where it might not be present even if we expect it to generally exist?

[OhKai]

Should every value be set to optional that could have an edge-case where it might not be present even if we expect it to generally exist?

Absolutely, any value that can be optional must be denoted as such. It is the responsibility of the caller to ensure the safe usage of these values by either

• using optional chaining or checking them against null/undefined and handle exceptions accordingly
• or if it is 100% semantically clear that the value won't ever be not there (e.g. it was checked earlier and cannot be unset etc.) you can use variable!.method() to force typescript to treat the optional value as non-optional.

[jjoderis]

LGTM