-
Notifications
You must be signed in to change notification settings - Fork 1
Provide a polyglot debugger #49
Copy link
Copy link
Open
Labels
an: enhancement 📈Improve somethingImprove somethingfor: IDE 🌒Affect EKumi's integration in the IDEAffect EKumi's integration in the IDEfor: core ❤️Affect EKumi's core.Affect EKumi's core.impacts: extensibility 🔗Affects the way new features can be added to EKumiAffects the way new features can be added to EKumiis: available 🏁No one works on this yet so you can pick itNo one works on this yet so you can pick it
Description
Metadata
Metadata
Assignees
Labels
an: enhancement 📈Improve somethingImprove somethingfor: IDE 🌒Affect EKumi's integration in the IDEAffect EKumi's integration in the IDEfor: core ❤️Affect EKumi's core.Affect EKumi's core.impacts: extensibility 🔗Affects the way new features can be added to EKumiAffects the way new features can be added to EKumiis: available 🏁No one works on this yet so you can pick itNo one works on this yet so you can pick it
Motivation
It is important to allow users to debug their workflow. However, since most activities (called
External Activities) are implemented by writting code in Java, Python or whatever the debugger must support all these environments at once.Solution
A possible solution is to create a composite debugger that would interact with the Workflow Debugger, the Java Debugger, the Python Debugger... and would provide a unique interface to the user. Still have to determine how to implement this exactly!