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

Drop Eventcallback child content remark (#12887)

pull/12894/head
Luke Latham 2019-06-15 10:35:39 -05:00 committed by GitHub
parent 415e78f589
commit 1acdc43cd4
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
aspnetcore/blazor/components.md
View File

@ -379,9 +379,9 @@ Invoke an `EventCallback` or `EventCallback<T>` with `InvokeAsync` and await the
await callback.InvokeAsync(arg); await callback.InvokeAsync(arg);
``` ```
Use `EventCallback` and `EventCallback<T>` for event handling and binding component parameters. Don't use `EventCallback` and `EventCallback<T>` for child content&mdash;continue to use `RenderFragment` and `RenderFragment<T>` for child content. Use `EventCallback` and `EventCallback<T>` for event handling and binding component parameters.
Prefer the strongly typed `EventCallback<T>`, which provides better error feedback to users of the component. Similar to other UI event handlers, specifying the event parameter is optional. Use `EventCallback` when there's no value passed to the callback. Prefer the strongly typed `EventCallback<T>` over `EventCallback`. `EventCallback<T>` provides better error feedback to users of the component. Similar to other UI event handlers, specifying the event parameter is optional. Use `EventCallback` when there's no value passed to the callback.
## Capture references to components ## Capture references to components