rspecq
rspecq copied to clipboard
Remove sentry as a required dependency
We use a different bug tracking tool than sentry. Adding rspecq to the gem file and running some tests results in failures. I have traced this back to conflicts between the two bug tracking tools.
Since it doesn't make sense for us to include sentry in our dependency graph, does it make sense for sentry to be an optional dependency?
Sentry should be abstracted away to an interface that may or may not send results to some api. That is true. There are a number of ideas on how this can be done, for example as events (active support notifications, kafka) and/or plugins (like sentry, datadog etc).
At the very least, the Sentry integration should only kick in if the gem is loaded (e.g. defined?(Sentry)
). I believe this should solve your issue @danielwestendorf, right?
Hey @danielwestendorf, any chance you've seen my message above? Would something like that work for you? In any case, I can prepare a PR so you can test it.