Matt Young

Hi @nikcorg We'll need to give this some thought to decide on the best API, but in principle exposing the behavior more transparently is a reasonable request. This is now...

Hi @countingtoten Thanks for the offer, but I'm not sure we'd accept a PR at present. We'd like to more carefully consider other possible scenarios here and decide on the...

Hi @stitchfixsam What we'd recommend for your scenario it to not use `discard_classes` but instead store your own list of classes to discard. Then in `add_on_error` once you've run your...

Hi @stoivo Thanks for the feedback. We likely wouldn't accept a PR with your proposed suggestion at present due like you say to issues with other customers who may rely...

Hi @ybiquitous Thanks for your suggestion. We'll consider this as part of future improvements across our Ruby error reporting libraries.

Hi @godfrey-altmetric Thanks for reporting. We're taking a look.

Hi @waynebrantley. This is one of a number of logging frameworks we're considering adding support for in the future but it's not an immediate priority on our roadmap. I've flagged...

Hey @alexmojaki Thanks for highlighting these libraries to us! We plan to take a look and see what we can make best use of. Thanks again!

Hi @cansjt Thanks for the feature request! I can see the value in supporting something like this. It would be useful to understand more about how you're overriding the grouping...

Hi @cansjt Thanks for the info. Yes, I can see why this pattern would work well for you for your use case. This is now being considered on our backlog,...