[Blazor] Lifecycle - lifecycle1.png update (eg. SetParametersAsync is not "-first render only-")

[hakenr]

Description

@guardrex Where do I find source-files for the diagrams in the page? I would like to propose some adjustments.

For example the lifecycle1.png

It is not true that SetParametersAsync is - First render only -.

Page URL

https://learn.microsoft.com/en-us/aspnet/core/blazor/components/lifecycle?view=aspnetcore-8.0

Content source URL

https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/blazor/components/lifecycle.md

Document ID

4871f4f7-9cf6-ac7a-0f21-c65d34bd1119

Article author

@guardrex

[github-actions]

😎 March! The gateway to spring! 🌞

A green dinosaur 🦖 will be along shortly to assist. Stand-by ........

[guardrex]

They're here ...

https://github.com/dotnet/AspNetCore.Docs/tree/main/aspnetcore/blazor/components/lifecycle/_static

... but wait until you discuss proposed changes with Steve and/or Javier before performing work on the images/text. Many issues have come in over the years from devs claiming that the diagrams are oversimplified to the point of being incorrect. When they were reviewed by Steve and/or Javier for those issues, they determined that these were generally correct simplifications of how Blazor processes lifecycle events and that they didn't want them updated. I added text to that effect ...

This article simplifies component lifecycle event processing in order to clarify complex framework logic.

... and ...

The following simplified diagrams illustrate Razor component lifecycle event processing.

Other than your remark ...

It is not true that SetParametersAsync is - First render only -.

... list out other changes that you propose to make. When you're ready for them to take a look, I'll email them (i.e., they probably won't see a ping from this repo, and I'll need to email to get their attention on this).

[guardrex]

Steve/Javier ... @hakenr also recommends the following change on #32089 ...

The `Render` lifecycle:

- 1. Avoid further rendering operations on the component:
-    * After the first render.
-    * When [`ShouldRender`](xref:blazor/components/rendering#suppress-ui-refreshing-shouldrender) is `false`.
+ 1. Avoid further rendering operations on the component when both of the following conditions are met:
+    * It is not the first render.
+    * [`ShouldRender`](xref:blazor/components/rendering#suppress-ui-refreshing-shouldrender) returns `false`.
2. Build the render tree diff (difference) and render the component.
3. Await the DOM to update.
4. Call [`OnAfterRender{Async}`](#after-component-render-onafterrenderasync). The synchronous method is called prior to the asychronous method.

Also ...

This one is up for consideration ...

[Blazor] Event handling - ParentChild2.razor without Task.Yield()
#32086

- <Child2 OnClickCallback="@(async (value) => { await Task.Yield(); messageText = value; })" />
+ <Child2 OnClickCallback="@((value) => { messageText = value; })" />

[guardrex]

I sent them an email, so we'll hear back soon 👂on this and the two open PRs.