Yurii Rashkovskii
Yurii Rashkovskii
Crate collection from [wasm.rs](https://wasm.rs)
Currently, attributes are stored as maps of `String.t() -> String.t()` (with occasional sprinkling of non-String keys that are used for internal purposes). This means the following: 1. Misspelled attribute name...
* [x] Signal * [ ] Message * [ ] Timer * [ ] Conditional * [ ] Link * [ ] Multiple * [ ] Parallel Multiple *List is...
> Properties, like Data Objects, are item-aware elements. But, unlike Data Objects, they are not visually displayed on a Process diagram. Certain flow elements MAY contain properties, in particular only...
This particularly applies to `add_node` function. It would have been great to have these: * [x] Passing attributes as maps **or** keyword lists. Will greatly reduce `%{}` noise in tests....
Currently, it's not possible to limit workflows access to any standard BPMN element. However, in some cases it might be very useful. For example, I personally consider `scriptTask` to be...
How do we determine whether a process has completed (no further activity) or in stasis (flow nodes are waiting, not doing anything)? Answering this could really help with improving testing....
Currently, BPXE has two gateways that were designed to make implementation of the flow node operations forward-flowing (so there's no need to check for anything that happened prior to the...
I've tried to run `wasm-pack test` on current CI (GitHub Actions), and it worked for `bpxe-bpmn-schema`, but not for `bpxe` -- it simply hangs. It works fine locally, though.
Currently, the data flow is part of `ActivityContainer` operations and as such, is difficult to test and debug in isolation. Proposed solution: extract it into its own module.