Thanks for the tutorial! Really well explained and clear. I do have a further question to this which is is it possible to pass/return variables upstream i.e passing values from child component to parent. If so how?
nice video, this is very interesting to me, but i cant come up with examples on where would i apply this concept. Do you have any use cases for it? like real applications examples to implement it?
It has to do with more on how you design your app and what info you want to pass along. Lets say your name or something that you would rather keep on passing through the components instead of having to continuously ask for it via an api call.
Interesting! What I recently had to deal with was passing a value to @ChildContent (RenderFragment) or @Body. Since I'm doing the Auth customly, I kinda have to reinvent triggering the UI updates accordingly. For example, setting the CurrentUserData after succesful authentication but the OnInitialized already triggerd on the @Body or @ChildContent. Also, how Blazor re-renders the UI partially instead of completely on state change (like React does?). For example, only the UI elements within an @if block will be updated on state change, not the elements above it etc.
awesome man!
thank you for the content, I really apreciate it
Thank you for subbing since i see you are subbed.
Thanks for the tutorial! Really well explained and clear. I do have a further question to this which is is it possible to pass/return variables upstream i.e passing values from child component to parent. If so how?
no you cant do that to my knowledge
@@justblazorprogramming Thanks for the reply. i've found a way to do it using event callback by pairing it with a parameter
nice video, this is very interesting to me, but i cant come up with examples on where would i apply this concept. Do you have any use cases for it? like real applications examples to implement it?
It has to do with more on how you design your app and what info you want to pass along. Lets say your name or something that you would rather keep on passing through the components instead of having to continuously ask for it via an api call.
Interesting! What I recently had to deal with was passing a value to @ChildContent (RenderFragment) or @Body. Since I'm doing the Auth customly, I kinda have to reinvent triggering the UI updates accordingly. For example, setting the CurrentUserData after succesful authentication but the OnInitialized already triggerd on the @Body or @ChildContent. Also, how Blazor re-renders the UI partially instead of completely on state change (like React does?). For example, only the UI elements within an @if block will be updated on state change, not the elements above it etc.
what 's your font in visual studio? It's look kinda nice
Im not sure, i probably made the font bigger to make the presentation easier to read