[FEAT] CasePathResolver: create a dedicated demo #143
Description
DISCLAIMER: this issue describes path computation for a single instance/case only. So the implementation will go to the CasePathResolver class as it differs from PathResolver which is a generic implementation that both deals with single instance or all instances of a process.
Is your feature request related to a problem? Please describe.
We already have a demo for PathResolver but as CasePathResolver is for a dedicated use case and will provide several computation options, I suggest we introduce a dedicated demo to clearly show that we have 2 different implementations.
Describe the solution you'd like
The demo could demonstrate the various resolution options that are available.
The user should be able to
- select completed or pending elements (the way of doing this is to be discussed): [FEAT] CasePathResolver: distinguish completed and pending elements passed as input parameters to infer more flows/edges in the path #16
- change the resolution options. For instance, a "cogg" icon could open a modal, or if there is enough space, we could display all options directly in the page
Additional context
See also #79.