dotnet/aspnetcore

[Blazor] Clearer way to troubleshoot complex state transitions

Open

#51,844 opened on Nov 3, 2023

View on GitHub
 (3 comments) (0 reactions) (0 assignees)C# (10,653 forks)batch import
Pillar: Technical DebtPriority:1area-blazorfeature-observabilityhelp wantedtask

Repository metrics

Stars
 (37,933 stars)
PR merge metrics
 (Avg merge 16d 9h) (258 merged PRs in 30d)

Description

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:

  1. We can afford an extra "if".
  2. We can find a way link it out if we need it on production builds.

/cc: @JamesNK

Contributor guide

Research direction
Look at the ComponentState.cs file around line 230-244, understand the state transitions, and add appropriate logging conditions.
Tech stack
csharp
Domain
frontenddeveloper experience
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
C#Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65