Blazor Wasm global scope

[bruno-garcia]

Problem Statement

Global scope:

sentry-dotnet/src/Sentry/SentryOptions.cs

Line 59 in 66ddcd8

public bool IsGlobalModeEnabled { get; set; }

by default relies on AsyncLocal. This is optimal for web servers, where we PushScope at the start of web requests to have isolation for Logs, HTTP data, etc.

This is an issue on Client apps such as Mobile and Desktop. It turns out on Blazor WASM it's the same issue. Users set scope such as User when retriving a user from the backend, and expect any subsequent event will include that data.

Solution Brainstorm

Possibly enable global mode for Blazor WASM out of the box.

Come from Zendesk

[mattjohnsonpint]

Looks like we should just detect running in a browser at runtime and set global mode true for that. This is pretty small then.