วีดีโอ

note that the computed signals from the signalStore return a copy by reference. The store is not supposed to return in the computed signals a copy by reference but a deep copy. So that if a component changes the value, then it changes only in the component and does not propagate the change in the store. Do the test yourself if you like. With this same example of the todo. Try using ngModel to do the two way binding to change the value of whether or not the todo is complete. and check with the angular devtool to see if the change is propagating in the store or just pops up in the component and you will notice that ngModel propagates the change in the store as well. That suggests that the value returned by the computed signal is a copy by reference. ngModel should only change the value read from the component and if I want the change to propagate into the store I should use a method declared in the withMethods to propagate the change. I don't understand why this is happening to me....

Great tutorial. Much clearer than the official documentation.

Great tutorial, Thank you

Will it automatically unsubscribe ?

I only use 'root' signal stores for things that require the persisted state throughout the app also I use them for my search pages so that when I return to it from an edit page the search state is remembered. I still use the signal store for each of my components as the extra complexity is a worthwhile tradeoff for having a consistent pattern throughout the app along with removing lots of code from the component ts files.

What use cases does this signalState have? I don't understand the use cases it has. Great Video!

How are you using async and await in NgOnit since it is not async and will not wait for the promise to complete?? You can use it on button clicks but not to load the initial data in NgOnit so you are still stuck with observables in NgOnit since you can't make ngonit async and even if you do it still will not wait

tnks for all! Man i have a question, we can use the hooks for init the store or is bad practice? another question! what is the best way or the best practice for prevent fetch data 2 times i mean, if i know my store is data will never change how i can prevent the fetch if alredy exist data ?

Do you have source link?

great series

Single Data Observability Pattern

Clear, precise and informative video. Way to go!

Did you generate a repository?

Thank you for great introduction to Angular sections. You could shorten your explanations in avoiding repeating the same all over the time. For example telling the benefits of Signals by the end of the second part of your video.

I have a question: In Angular v18.1.0 if we set viewChild.required(MatButtonToggleGroup) and then try to access it in the effect that is inside the constructor and we get an error: 'Child query result is required but no value is available'. It is clear that the value is not yet there, in that point in time, but how did you not get that error? And how would we then write required viewChild values and use them in effects?

Beautifully explained. Probably the best Angular SSR explanation. Loved how the hydration is explained.

Im watching from mobile, can you move this link to your description, it is not clickable here

Great explanation

How about subscriptions?

Do you have repository to look add the code?

Can anyone explain how the secured api will be accessed using SSR?

This was just what I was looking for. I was concerned that ssr didn’t use the router. From some previous reading the hydration is a bit more manual but I’m sure that’s in your course.

Signals pretty shit if you can't mutate the properties of an object because they might be bound to UI

Halo Vasco, thank you for all the great contents. I bought some of your udemy courses. I'm just starting to learn Angular. Due to the fast "6 month" update cycle, it becomes unclear for me which feature/technology is still relevant and which one os not. For example signalStore(), does this makes the old way, such as createStore, createSelector, createXxxx become obsolete?

Thanks a lot for this video. You really nailed the explanation.

The deployment process is not clear. How the two different servers will communicate with each other to fetch the browser folder content?

What if the non-primitive signals are used in a template-driven form? For example, how would you correctly do `<input [(ngModel)]="course().title" type="text" />`?

I would suggest you remove the background music. I think it takes away from the quality of the video and lesson.

thanks for the Explanation .. but do we need to make http request on every single change . May be it would better if a user saves the form on click of save button which might avoid unnecessary calls to server.

I am using rxMethod and now I need to use it in component. and after getting success api response I need to perform some action based on data.. how to do that ? Not able to understand

Very helpfull! Thanks 👍

Thanks a lot!

How do you access route parameters from such a service ?

Would have been nice to know which version you are using here and which version this implementation supports. A lot more angular devs are in v16 and cannot move to 18 yet...

08:57 Why Angular Signals?

great rundown as always

Great video! Thank you for sharing. How would you suggest to set up environment variables. Esbuild doesn't seem to have anything out of the box. Been struggling with it. On build esbuild can't find my environment variables. Using Anguar 17.3.11

Amazing video, Vasco!

Thanks a lot for the great explanation and effort.

very helpful. thank you so much.

Hi you have great English but wanted to respectfully critique that you say "here" as an empty word very often to quite a distracting amount. The test is if you remove the word does it communicate the same thing and I did not hear any case where the word here was needed.

Hello, very good video! Starting with angular 16, in the chrome debug, the "this" context inside an async function always turns out to be undefined. What is the reason?

Why do we need the effect type in constructor (filtering part) and what would happen if i didn´t wrap that code into effect function ? Thanks.

signalStore + service is quite appealing approach. How do you think of it?

very sensible

for me this approach is much cleaner compared to old school way

Excellent video! Can you please explain why is it needed the injector?

This is why I have switched to vue. Signals are just vue refs and vue comes with state management from pinia.

Thanks a lot for the video! One quick question: Is there a browser extension to see the actual state? For the NGRX store I always used Redux extension to see in the browser the store (and it's very helpful to debug), is there something like that for this signal store?

Really nice. Good job