Document persister's handling of workflow context #182
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.
Description
Document that the serializer is expected to persist the
contextas well as the immediate workflow state. I'm explicitly declaring that it's not the Context instance which is to be returned, because that creates a tight coupling between the persister and the context class it will use. At a later stage, the Factory can be used to associate different Context classes with workflows.Also, update the File persister to persist the workflow's Context according to the declared protocol.
Note: we probably needs something similar in the DBI serializer?
Type of change
Marking as 2.0, because this breaks older serializations: When a Context object was returned from the persister, the new context being instantiated by the Factory receives the content of the blessed Context hash instead of the PARAMS hash.
Checklist: