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.
Often, I find it helpful in my retrievers to know whether
StripeEvent
has any registered listeners for a particular event type. This allows me to avoid aStripe::Event.retrieve
API call to Stripe if I am not even interested in processing the event. Currently, I do this in my retrievers:Since
StripeEvent.namespace
andStripeEvent.backend
are internal implementation details, I think it would be nice to provide aStripeEvent.listening?
API which provides this functionality without exposing users of the gem to notification internals.