Sends all nested exception's ex-data grouped in sub levels #56
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.
This PR enables the client's option
:indexed-ex-data
to be able to send all neted exception'sex-data
grouped under an indexed level.Background
Currently Rollcage only uses one level for the exception
ex-data
calledcustom
. Under that level, anex-data
key would becomecustom.some_value
. However, when you send nested exceptions, you don't know which exception the key belongs to, and repeated keys are overwritten, preferring the deepest exception in the tree.So, for an exception like this:
you currently see something like this:
with this information:
Proposal
This PR enables a client like
(rollcage/client token {:indexed-ex-data "__exception" :block-fields [:jwt]})
to have the following information in Rollbar: