Implement local scope, which is a method parameter for the capture methods

[marandaneto]

Similar to Dart/Flutter https://github.com/getsentry/sentry-dart/pull/463/files

[bruno-garcia]

Recently added in .NET: getsentry/sentry-dotnet#1412

[adinauer]

Planning not to change .withScope at all. These new overloads should implement the local scope concept so the scope can be changed for one invocation only without affecting others especially in global hub mode.

Only planning to add overloads to

• captureMessage
• captureException
• captureEvent

[adinauer]

@bruno-garcia @marandaneto should we deprecate withScope as this is basically the less bug prone version of it? It's been removed in .NET. It's still there in .NET, however the docs claim that withScope does what the local scope does which is not true in all circumstances (the scope is pushed, modified, callback run and only after that it is reset back again so any call running at the same time would have the modified scope as well).

[marandaneto]

https://develop.sentry.dev/sdk/unified-api/
Hub::with_scope(callback) is technically optional, but not deprecated, I'm fine deprecating it tho, let's see what @bruno-garcia says.

[adinauer]

I don't see an easy way to fix it as we'd have to pass the Hub to the callback and devs would need to use that instead of Sentry.capture etc. So even if we did that it could still be a source of bugs / wrong info.

[marandaneto]

I don't see an easy way to fix it as we'd have to pass the Hub to the callback and devs would need to use that instead of Sentry.capture etc. So even if we did that it could still be a source of bugs / wrong info.

Not sure I've understood the problem here, do you mind elaborating?

Do we want this part of v6?

[marandaneto]

I've discussed this with @bruno-garcia and this will go to v7 to unblock v6.

[adinauer]

Let's deprecate it in v6 and remove with v7. I've opened an issue here #2083