dotnet/aspnetcore
GitHub で見る[Blazor] Clearer way to troubleshoot complex state transitions
Open
#51,844 opened on 2023年11月3日
Pillar: Technical DebtPriority:1area-blazorfeature-observabilityhelp wantedtask
Repository metrics
- Stars
- (37,933 stars)
- PR merge metrics
- (平均マージ 16d 9h) (30d で 258 merged PRs)
説明
This came up as part of a discussion.
In complex apps is hard to detect state transitions that might happen during a brief period of time and cause issues. We could consider adding additional logging https://github.com/dotnet/aspnetcore/blob/main/src/Components/Components/src/Rendering/ComponentState.cs#L230-L244 to avoid such issues in the future.
We discuss this in the initial days of Blazor and we were concerned about the perf, but I think that the perf characteristics have changed enough that:
- We can afford an extra "if".
- We can find a way link it out if we need it on production builds.
/cc: @JamesNK