dotnet/aspnetcore

Blazor Value cannot be null. (Parameter 'obj')

Open

#45,096 opened on Nov 14, 2022

View on GitHub
 (6 comments) (0 reactions) (0 assignees)C# (10,653 forks)batch import
Pillar: Technical Debtarea-blazorbugcopilot-candidatefeature-blazor-builtin-componentsgood first issuehelp wanted

Repository metrics

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

Description

Is there an existing issue for this?

  • I have searched the existing issues

Describe the bug

when calling EditContext.NotifyFieldChanged(FieldIdentifier); with a FieldIdentifier that has .FieldName == null (because the custom component is not declared using @bind ) we'll get this not very useful error message:

Value cannot be null. (Parameter 'obj')`

Expected Behavior

a better error message

Steps To Reproduce

No response

Exceptions (if any)

No response

.NET Version

6

Anything else?

No response

Contributor guide

Research direction
Inspect the EditContext.NotifyFieldChanged method and add a null check for the FieldIdentifier.FieldName to provide a better error 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.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
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
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80