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
Currently we are sending the workflow status changes from the workflow engines as the integer which represents the status, see for example in RWE Serial. This is happening because the enum which contains this statuses is inside REANA-DB and the workflow engines do not have DB as a dependency.
Even though it works it could easily lead to errors and it is definitely less readable. Also it would be more clear when dealing with the state-machine for workflow statuses.
A possible solution would be to move these enums (for Workflows and for Jobs) to REANA-Commons.
The text was updated successfully, but these errors were encountered:
Currently we are sending the workflow status changes from the workflow engines as the integer which represents the status, see for example in RWE Serial. This is happening because the enum which contains this statuses is inside REANA-DB and the workflow engines do not have DB as a dependency.
Even though it works it could easily lead to errors and it is definitely less readable. Also it would be more clear when dealing with the state-machine for workflow statuses.
A possible solution would be to move these enums (for Workflows and for Jobs) to REANA-Commons.
The text was updated successfully, but these errors were encountered: