Implemented new workflow model #86
Open
+1,595
−1,619
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Here are the wanted changes to the workflow model.
This mostly concerns the initial creation of the gmodel after loading the model and subsequent serialization when saving. The model state is still handled as gmodel, since the point of the change is to showcase how to use different models by transforming them to the internal gmodel-format.
Because of this, the changes are not very invasive, since it only concerns the outermost layer of model loading/saving, keeping the internal logic the same.
I already tested this by running the node server and it seemed to be working as expected.