Streamline event emission and tracking #154
Merged
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.
Improves the flow followed by the extension when firing and tracking events.
Previously, a
SubscriptionEvent
record would be created first, which would then fire aSpree::Event
in anafter_create
callback. This wasn't a very intuitive flow and it didn't follow the conventions used in the core.Now, a
Spree::Event
is fired first thing. Then, a subscriber catches all events fired by this extension and saves them as aSubscriptionEvent
record under the related subscription.Using the built-in subscriber mechanism streamlines how we handle events and makes it more consistent with the core.