Feedback for blazor data binding in v7

[lonix1]

1

In this section there's a typo in the code:

        inputValue = newValue.Length > 4 ? "Long!" : inputValue = newValue;

Should be

        inputValue = newValue.Length > 4 ? "Long!" : newValue;

2

In this section it says:

> For two-way data binding in ASP.NET Core 7.0 or later, we recommend using @bind:get/@bind:set modifiers. For more information, see the @bind:get/@bind:set in the opening section of this article.

But it doesn't say why? I assume that the new v7 syntax allows one to perform a "set" with an async method, which cannot be done using a regular c# (sync) property setter. That is useful, for e.g., when doing autocomplete. Maybe there are other reasons?

---

Document Details

⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

• ID: b211df59-e1c9-86c0-c904-31fa3c361e6d
• Version Independent ID: 3f912dfc-5ba5-6c6c-ba93-1ae78508a5cc
• Content: ASP.NET Core Blazor data binding
• Content Source: aspnetcore/blazor/components/data-binding.md
• Product: aspnet-core
• Technology: aspnetcore-blazor
• GitHub Login: @guardrex
• Microsoft Alias: riande

[guardrex]

Thanks @lonix1 ... I'm going to patch (fix) this issue quickly and open a follow-up on the motivation for the @bind:get/@bind:set aspect.