Manoel Aranda Neto
Manoel Aranda Neto
LGTM from my side but I'd let the owners of this repo approve it.
Its already possible to do some sort of config with `project.ext.sentryCli` on Gradle, so this one can fit in there.
Closing the issue as a part of large repository cleanup, due to it being inactive and/or outdated. Please do not hesitate to ping me if it is still relevant, and...
https://github.com/getsentry/sentry-dart/tree/main/flutter#usage
@ueman what if we offer a method like: `Sentry.captureNestedExceptions(list)` and/or `SentryEvent` is able to take a list of `throwable`? does that help? so the SDK is able to do its...
> For manually reported exceptions that would help though. That would be the first step, yes. > How would that help for automatic reported nested exceptions You have the instance...
Quick note, maybe this list should also get a `stackTrace`, so a different data structure would make more sense.
> Ah, I see, that makes sense. But currently the event processors run after the SentryException and SentryStackTrace are created right? yes, that's a good point, and it should run...
Its a good candidate for v7, I will discuss this, thanks for the input.
Then `event.throwable` has to be deprecated in favor of `event.throwables`, `event.throwable` for now would return the first item of `event.throwables` if any.