You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I agree that the workflow engine specific part should ideally be included in the workflow engines. At the moment it is primarily included in this repository to enable faster iteration of the Python Workflow Definition.
I agree it makes sense to separate the JSON writer to a separate module.
While I am not exactly sure how we want to address the first issue, the second and third could be address directly. Feel free to open a corresponding pull request.
I guess we have to properly increase the version but as long as the JOSN format remains the same, I am fine. I think the main focus at the moment is on maintaining backwards compatibility to exported workflows.
Activity
jan-janssen commentedon Jan 20, 2026
Hi @XzzX ,
While I am not exactly sure how we want to address the first issue, the second and third could be address directly. Feel free to open a corresponding pull request.
[-]Restructure package folder?[/-][+][Suggestion] Restructure package folder?[/+]XzzX commentedon Jan 21, 2026
These are API breaking changes. Is that ok?
jan-janssen commentedon Jan 21, 2026
I guess we have to properly increase the version but as long as the JOSN format remains the same, I am fine. I think the main focus at the moment is on maintaining backwards compatibility to exported workflows.