dotnet/aspnetcore

[Blazor] Throw meaningful exception for JSRuntime calls that timeout

Open

#21,384 opened on Apr 30, 2020

View on GitHub
 (6 comments) (5 reactions) (1 assignee)C# (10,653 forks)batch import
Pillar: Technical Debtaffected-fewarea-blazorbugcost: Sfeature-blazor-jsinteropfeature-blazor-wasmgood first issuehelp wantedreevaluateseverity-major

Repository metrics

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

Description

Capturing the direction on this into a new issue. We should throw a more meaningful exception to users if JS interop invocations timeout.

Ref: #18875 #21375

Contributor guide

Research direction
Look at the JSRuntime implementation to understand how timeout exceptions are currently thrown. Trace the code path from JS interop call to timeout. Identify where a custom exception can be introduced to provide a meaningful message.
Tech stack
csharp
Domain
frontend
Issue type
Bug
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#Blazor basicsJavaScript interop
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70