Skip to content

Conversation

@guardrex
Copy link
Collaborator

@guardrex guardrex commented Oct 23, 2025

Fixes #36052

Distilled from Javier's remarks at dotnet/aspnetcore#57962 (comment).

I'm waiting on Javier to answer an offline question. Then, I'll call for review.


Internal previews

📄 File 🔗 Preview link
aspnetcore/blazor/components/data-binding.md aspnetcore/blazor/components/data-binding

@guardrex guardrex self-assigned this Oct 23, 2025
@guardrex guardrex requested a review from Copilot October 23, 2025 14:42
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR improves documentation coverage for @bind:get/@bind:set syntax in Blazor data binding based on feedback from issue #36052 and #57962. The changes clarify why direct parameter mutation should be avoided and explain the benefits of using @bind:get/@bind:set syntax.

Key Changes:

  • Added explanation of why direct component parameter modification should be avoided
  • Documented the benefits and use cases for @bind:get/@bind:set syntax
  • Included an analogy using HTML's <input> element to explain the concept
  • Added a reference to issue #57962 for additional context

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Potential further improvements to multiple level binding scenario coverage

1 participant