This repository was archived by the owner on Jul 19, 2025. It is now read-only.
Services no longer must support all possible events #24
Conversation
This file contains hidden or 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
Prior to this change, a service had to define a receive method for every event, otherwise a NoMethodError would occur if that event is sent. This change allows services to define methods only for those events they care about, others will be ignored.
brynary
added a commit
that referenced
this pull request
Jun 23, 2014
Services no longer must support all possible events
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Prior to this change, a service had to define a receive method for every
event, otherwise a NoMethodError would occur if that event is sent.
This change allows services to define methods only for those events they care
about, others will be ignored.