Provide a way to re-attach events on replay #195
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.
Sometimes events don't need state at first but eventually do. This adds a simple way to "re-attach" all the events state during replay, effectively ensuring that everything with a
#[StateId]
attribute now is connected to that state for future queries. Imagine:And later needing to track some sort of "legacy rules" value for future events:
With this feature, you can run replays with the
--reattach
flag, and old events that were fired before we updated our code with#[StateId(UserState::class)]
will automatically get attached to theUserState
before replay.