Currently, when developing the front part of the demo, the Python server must be up.
This requires that "frontend" contributors setup it which is not very convenient (Java must also be configured).
To simplify the development process, I suggest we develop a fake JavaScript server that will replicate the Python server behavior.
If needed, this will also let easily test some edge cases: API errors, slow or fast responses, ....
The server has to replicate 2 API:
XES to BPMN: discover/inductive-miner
get frequency data: stats/frequency
conformance alignment data file transformation: conformance/alignment
Currently, when developing the front part of the demo, the Python server must be up. This requires that "frontend" contributors setup it which is not very convenient (Java must also be configured).
To simplify the development process, I suggest we develop a fake JavaScript server that will replicate the Python server behavior. If needed, this will also let easily test some edge cases: API errors, slow or fast responses, ....
The server has to replicate 2 API:
We could use Express, Fastify, NestJS, Next.js, or others.
Notes
This will help investigating #15 for instance