We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
In the Go SDK, setting certain fields on the scope override the equivalent fields in events, while in other SDKs the event fields take precedence.
Compare Scope.ApplyToEvent (Go) and Scope.applyToEvent (JS).
In particular:
if len(scope.contexts) > 0 { if event.Contexts == nil { event.Contexts = make(map[string]interface{}) } for key, value := range scope.contexts { event.Contexts[key] = value } }
if (this._contexts && Object.keys(this._contexts).length) { event.contexts = { ...this._contexts, ...event.contexts }; }
SDKs should handle this type of detail consistently.
sentry-go
0.9.0
The spec is not clear about precedence, but seems that the JavaScript behavior is the one replicated elsewhere.
The text was updated successfully, but these errors were encountered:
cleptric
Successfully merging a pull request may close this issue.
Summary
In the Go SDK, setting certain fields on the scope override the equivalent fields in events, while in other SDKs the event fields take precedence.
Steps To Reproduce
Compare Scope.ApplyToEvent (Go) and Scope.applyToEvent (JS).
In particular:
Go
JavaScript
Expected Behavior
SDKs should handle this type of detail consistently.
SDK
sentry-go
version:0.9.0
Additional context
The spec is not clear about precedence, but seems that the JavaScript behavior is the one replicated elsewhere.
The text was updated successfully, but these errors were encountered: