daohualiuxiang
/
AspNetCore.Docs
mirror of https://github.com/dotnet/AspNetCore.Docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Remove @bind:{get|set|after} feature NOTEs (#28683)

pull/28689/head
Luke Latham 2023-03-15 16:12:53 -04:00 committed by GitHub
parent 9e6d8ba0ef
commit 7732e0279b
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 0 additions and 48 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

48
aspnetcore/blazor/components/data-binding.md
View File

@ -47,11 +47,6 @@ To execute asynchronous logic after binding, use `@bind:after="{EVENT}"` with a
Using an event callback parameter (`[Parameter] public EventCallback<string> ValueChanged { get; set; }`) with `@bind:after` isn't supported. Instead, pass a method that returns an <xref:System.Action> or <xref:System.Threading.Tasks.Task> to `@bind:after`.
> [!IMPORTANT]
> The `@bind:after` feature is receiving further updates at this time. To take advantage of the latest updates, confirm that you've installed the [latest SDK](https://dotnet.microsoft.com/download). Visual Studio updates to support the feature are planned for the mid-February Visual Studio release.
>
> For more information, see [Blazor `@bind:after` not working on .NET 7 RTM release (dotnet/aspnetcore #44957)](https://github.com/dotnet/aspnetcore/issues/44957).
In the following example:
* The `<input>` element's `value` is bound to the value of `searchText` synchronously.
@ -115,11 +110,6 @@ Components support two-way data binding by defining a pair of parameters:
* `@bind:get`: Specifies the value to bind.
* `@bind:set`: Specifies a callback for when the value changes.
> [!IMPORTANT]
> The `@bind:get` and `@bind:set` features are receiving further updates at this time. To take advantage of the latest updates, confirm that you've installed the [latest SDK](https://dotnet.microsoft.com/download/dotnet/7.0). Visual Studio updates to support the feature are planned for the mid-February Visual Studio release.
>
> For more information, see [Blazor `@bind:after` not working on .NET 7 RTM release (dotnet/aspnetcore #44957)](https://github.com/dotnet/aspnetcore/issues/44957).
The `@bind:get` and `@bind:set` modifiers are always used together.
Using an event callback parameter with `@bind:set` (`[Parameter] public EventCallback<string> ValueChanged { get; set; }`) isn't supported. Instead, pass a method that returns an <xref:System.Action> or <xref:System.Threading.Tasks.Task> to `@bind:set`.
@ -438,18 +428,6 @@ In the following example, the `PasswordUpdated` method executes asynchronously a
## Bind across more than two components
<!-- HOLD: See https://github.com/dotnet/AspNetCore.Docs/issues/27848
> [!IMPORTANT]
> The `@bind:get` and `@bind:set` features demonstrated in this section are receiving further updates at this time. To take advantage of the latest updates, confirm that you've installed the [latest SDK](https://dotnet.microsoft.com/download/dotnet/7.0).
>
> For more information, see the following resources:
>
> * [Blazor `@bind:after` not working on .NET 7 RTM release (dotnet/aspnetcore #44957)](https://github.com/dotnet/aspnetcore/issues/44957)
> * [`BindGetSetAfter701` sample app (javiercn/BindGetSetAfter701 GitHub repository)](https://github.com/javiercn/BindGetSetAfter701)
>
> To see a working version of the guidance in this section that doesn't rely on `@bind:get`/`@bind:set` modifiers, see the 6.0 version of this article.
You can bind parameters through any number of nested components, but you must respect the one-way flow of data:
* Change notifications *flow up the hierarchy*.
@ -476,32 +454,6 @@ In the following `NestedChild` component, the `NestedGrandchild` component:
For an alternative approach suited to sharing data in memory and across components that aren't necessarily nested, see <xref:blazor/state-management>.
-->
You can bind parameters through any number of nested components, but you must respect the one-way flow of data:
* Change notifications *flow up the hierarchy*.
* New parameter values *flow down the hierarchy*.
A common and recommended approach is to only store the underlying data in the parent component to avoid any confusion about what state must be updated, as shown in the following example.
`Pages/Parent2.razor`:
:::code language="razor" source="~/../blazor-samples/6.0/BlazorSample_WebAssembly/Pages/data-binding/Parent2.razor":::
`Shared/NestedChild.razor`:
:::code language="razor" source="~/../blazor-samples/6.0/BlazorSample_WebAssembly/Shared/data-binding/NestedChild.razor":::
> [!WARNING]
> Generally, avoid creating components that write directly to their own component parameters. The preceding `NestedChild` component makes use of a `BoundValue` property instead of writing directly to its `ChildMessage` parameter. For more information, see <xref:blazor/components/index#overwritten-parameters>.
`Shared/NestedGrandchild.razor`:
:::code language="razor" source="~/../blazor-samples/6.0/BlazorSample_WebAssembly/Shared/data-binding/NestedGrandchild.razor":::
For an alternative approach suited to sharing data in memory and across components that aren't necessarily nested, see <xref:blazor/state-management>.
## Additional resources
* [Parameter change detection and additional guidance on Razor component rendering](xref:blazor/components/rendering)