Good summary Mark. I would only add that you also call StateHasChanged if you are doing multiple asynchronous steps in a method such as OnInitializedAsync and want additional renders while awaiting. Blazor will do a render on the first await, and another after completion of execution of the method. If you have say 5 sequential async awaits inside the method, you should call StateHasChanged just before each await if you want additional renders.
Consider me subscribed. I'm the exact beginner Blazor developer that this video is for 😉Thanks again I'm only 2 videos in and learning so much already
Glad to have you.
Great summary, Thanks.
Good summary Mark. I would only add that you also call StateHasChanged if you are doing multiple asynchronous steps in a method such as OnInitializedAsync and want additional renders while awaiting. Blazor will do a render on the first await, and another after completion of execution of the method. If you have say 5 sequential async awaits inside the method, you should call StateHasChanged just before each await if you want additional renders.
Yes. Totally valid.