From 1acdc43cd4d41679974f2e417a2a2f093741bed7 Mon Sep 17 00:00:00 2001 From: Luke Latham <1622880+guardrex@users.noreply.github.com> Date: Sat, 15 Jun 2019 10:35:39 -0500 Subject: [PATCH] Drop Eventcallback child content remark (#12887) --- aspnetcore/blazor/components.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/aspnetcore/blazor/components.md b/aspnetcore/blazor/components.md index 9b08580043..73da47e3eb 100644 --- a/aspnetcore/blazor/components.md +++ b/aspnetcore/blazor/components.md @@ -379,9 +379,9 @@ Invoke an `EventCallback` or `EventCallback` with `InvokeAsync` and await the await callback.InvokeAsync(arg); ``` -Use `EventCallback` and `EventCallback` for event handling and binding component parameters. Don't use `EventCallback` and `EventCallback` for child content—continue to use `RenderFragment` and `RenderFragment` for child content. +Use `EventCallback` and `EventCallback` for event handling and binding component parameters. -Prefer the strongly typed `EventCallback`, 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` over `EventCallback`. `EventCallback` 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