elsa-workflows / elsa-workflows/elsa-core
Moving towards statecharts
- Dominant language
- C#
- Stars
- 7.9k
- Forks
- 1.5k
- Avg merge
- 15h 22m
- Merged PRs (30d)
- 114
Description
With the support of rather complex workflows, statecharts and parallel execution going towards a standard makes sense. BPMN covers some but not all (as far as I see).
It looks like you are moving towards statecharts support (https://statecharts.dev/) in json. It might make sense to seek inspiration from https://xstate.js.org/ where it is specified in json.
It is also possible to make an API that translates to and from elsa model to xstates model making it possible to push workflow execution to a manual workflow in an app for manual steps execution.
Contributor guide
Research direction
Start by reviewing the existing workflow model and JSON representation, then compare them with the statecharts.dev and XState JSON models referenced in the issue. Clarify whether the goal is statechart support, Elsa-to-XState translation, or both; done would require an agreed scope and design before implementation can begin.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100