Introduce unsnapshottableIdentifier() to allow transient WorkflowIdentifiers. #84
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.
This fixes #79 and unblocks the ability to implement GUWT Workers as Workflows.
WorkflowIdentifiercan now indicate that it is not serializable by returningnull from
toByteString(), in which case neither it nor the snapshot of theworkflow it identifies will be serialized. Because these identifiers do not need
to be serialized, they can contain arbitrary values such as
KTypes, which ishow Workers distinguish themselves for example. Workers also do not need to
be snapshotted, so this works out.