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

angular team lacks of vision

After watching your guide I decided to give it a try and I have to say I'm impressed! The most obvious benefit to myself is that the Webstorm project explorer is much easier to navigate with your eye than VS Code. I'm still learning things but I think I'm going to switch!

Thank you!

My main issue with Webstorm is Angular Language Service. They are not using the extension that Angular team provides, their own version is baked into the app. This caused my IDE to complain on new features from v17+ like signal inputs, and JetBrains took a long time releasing a new version. This forced me to use VS Code and I haven't looked back since. It's more lightweight and I'm pretty sure Webstorm uses double the ram compared to VS Code (Take this with the grain of salt).

can you make a good series on ssr more . How to fix the LCP and FCP with google fonts and images and improve the performance more than 90 + . it would be more useful

My fav and day to day is Sublime Text (with plugins) but I do use IntelliJ for Java. I like how IntelliJ and WebStorm does its file pane management (having multiple files open in different panes with the ability to move them around easily). I don’t think you showed that in this video.

The music is too loud to talk over. Hard to follow.

Great video as usual. I would appreciate it if the background music is not added, it makes it hard to follow what you are saying.

I'm using 35 shortcuts everyday. You're at the very start of mastering the JetBrains products my friend :)

New course available, Modern Angular With Signals - angular-university.io/course/angular-signals-course

Thanks for the info! It is great! Regarding the await, if you have two awaits (one in onRequestTriggered and another one in getCourses), does it mean that you are executing two promises? could it be a performance issue if there were so many functions like that?

Hi, i got a question when testing on Angular SSR. in normal SSR application, when user choose some filters on page 1, showing list of data, then navigate to page 2, when navigate back using the browser back button, the filters will remain and as well as the list of data however using Angular SSR, the user filters are gone, is there any way to configure to achieve this behaviour?

Very useful. Thank you.

we want a book with all your knowledge

ummm i don't like put services inside store, store must know only about data and not about services, it's my personal opinion

Great video 👌🏾 At 5:57, where you add the try block, what's the extension/shortcut that instantly wrapped the below statement in the try block?

Awww, damn! I unknowingly had only watched a portion of the short and got it all backwards. This is so nice!

Is it the same for input?

Great content Vasco ! Valuable lesson 😎

Everything is too complicated when you don't know how to use it. A good developer shoul know both methods and choose when to use. In my opinion observables are more scalable then async/await.

On the fetch you could have shown how to do a then / catch and resolve / reject, rather than wrapping in a try/catch. Great tutorial.

Also in this case "return await" looks like an antipattern to me. It seems that who wrote the code wasn't even aware about promises! I'd rather go with just promise.catch and remove the async from getCourses

Thanks for the content Vasco! 6:18 Is there any difference in putting the return null inside the catch block or just in the end of the function like you did?

Vasco, I just wanted to say a HUGE THANK YOU for this video! It helped me understand a lot about promises & error handling! I'm working on a hobby project which will very soon involve "fetch" calls, so this is super valuable! Btw, I'm already annual member of Angular University. But I wanted to know, do you also do 1-1 calls/consultation? I would love to chat with you someday about few topics. Please let me know, thanks - Solat Ali

That is helpful.. ty..

Looking to learn how to use async/await in Angular to build modern signal-based applications? Check out my latest course, which is just out - angular-university.io/course/angular-signals-course

@10:25, shouldn't it be [value] instead of [(value)], because there's already (valueChange) event ?

Thanks for the video! Just one question: I thought that apart from improving the rendering times, SSR also helps with SEO in a way that the crawler gets all the texts on the page. However as you inspect the page source after enabling SSR, there are NO texts I can see.. Am I mixing some things up? Why are the texts not there?

let course = null; if(course && course.title){ console.log(`this course title is ${course.title}`) } I get error Property 'title' does not exist on type 'never'.ts(2339) Using typeScript: Version 5.4.5

This feature is amazing, it allows us to right a lot of less code