-
Notifications
You must be signed in to change notification settings - Fork 68
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Remove the ability to configure multiple notifiers
This feature starts getting in the way of future development of the library: * We have to maintain a complex API to support different configurations for many notifiers (we have 3 now vs 1 when we were releasing this functionality). We want a simple API * It's hard to pass the config object around. If a component that sits at the bottom layer of the library architecture suddenly needs to read some config value, we have to pass it through all the layers, from the top to the bottom. This was a compromise since the very beginning but back then it was easy to maintain it (although it always bugged me). We now rapidly add new features and this approach does not scale well - too much clutter * Classes know more than they really need. As a result, testing becomes harder since we need to inject the config (sometimes with "correct" values). An alternative way would be exposing the config through `Airbrake.notifiers[:default][:notice].config.config_value`. This only adds to the clutter since the API becomes more complex and less malleable. On the other hand, this feature is likely not used by 90% of our customers. We have a solid Rails workflow that never involves more than 1 notifier. If people need another notifier, they can easily instantiate it directly through `Airbrake::NoticeNotifier.new`.
- Loading branch information
Showing
4 changed files
with
13 additions
and
105 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
This file contains 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