Thanks a lot!

You're very welcome

Well, you are very welcome 🙏

They've never been there. For that import problem, which Jeremy described, the new term is selectorless. But we don't have any release date for that yet.

Thanks Konrad

Thanks a lot. Comments like this are always motivating

Thanks Kai. Happy to hear!

You are very welcome!

Thanks Carnaru

And still not over. A little bit beyond half-time.

You're welcome

Yeah, I hope this migrator is the beginning of an official recommendation for inject.

I know, I know. The problem are the 100 seconds. I decided not to drop stuff but just pack everything in it.

Thanks Rahul

Thanks Marçal

You are welcome!

Thanks Michael. Yeah, I was not expected that they postpone a minor release but a week isn't that long either and there should be enough content for the next episode. I did the Signal's talk now already the fourth time in the same manner. I've tried out different styles but I think explaining the signal store via refactoring is the optimal way you can do it if you have 20 minutes and you want to do some live coding.

Yeah, having seen some of these iterations in your previous stream appearances I found this one effective. I feel like state management frameworks are maligned as unneeded boilerplate, when really they are something that is mindfully done to streamline things and prevent chaos. Starting from existing code and refactoring into an ngrx approach gives that perspective. And refactoring also shows that it isn't too late to pull in a state framework, or shift into one. I pushed for a recent big project to use component store as we were on the fence about signal store, but I imagine we will probably pivot into signal store at a later time. This iteration of your talk would probably be one I would reference.

Hi Michael, thanks and about that issue: The implicit tracking has been a pain point for a lot of developers. It is still not fixed but we got at least an official response and a potential future fix.

And two days because I think Angular 18.1 will be released on Wednesday...

I too have found myself using untracked() all over the place to avoid unintentional tracking nested signal call 😂. Feeling the pain but it's still manageable

Yeah, so Dmytro has quite a lot videos around forms in general.

Thanks. Happy to hear

👍

Hi, it looks to me that this should be covered in the official tutorials (except the bootstrap framework): angular.dev/tutorials For bootstrap, please checkout : ng-bootstrap.github.io or valor-software.com/ngx-bootstrap/ I would highly recommend to go with standalone components and NgModules

@@ng-news many thanks, all love

Yes, from my perspective almost all devs appreciate the progress Angular has done and is still doing.

It's simply amazing. Looking forward to ditch zonejs

The required method wouldn't be possible with Decorators. Decorators cannot enforce a certain type.

​@@ng-newsrequired is possible with decorators.

Thanks a lot!

You are very welcome!

Thanks, that's only what I knew at the time of the recording. I think with the upcoming nx Launch things are becoming even more crystal-clear ;)

Thanks, that's the intention and it will stay like this.

Hi Vinit, I've meant the part in the script tag where we don't require a class anymore but define the metadata via a function.

@@ng-news got it

Oh really? Thanks for letting me know. I always add there the complete text for the reader's convenience. It is is the same that shows up here on KZbin as description.

Me? Well that's one my things I want to do in life. Writing a book. But time is not infinite...

Thank you "Mugatu".

Well, it didn't change anything in the way how property binding works. In the old days, the value in the constructor was just undefined. With input.require that's not an option anymore.

It will also simplify things. No need for ngOnChanges anymore. Just deal with it as with any other signal.

Hi, ah, forgot about that. I've added the links to the description. For your convenience: - Alex Rickabaugh on Signals: kzbin.info/www/bejne/fZimZXSshpVkZqs - Minko Gechev about 2024: kzbin.info/www/bejne/aH6UaJqIhseanKs

Yeah, I really hope that the official changes to the authoring format go into the same direction. Doesn't have to be a ng file, but double imports should go away and a shorter syntax for the properties in the decorator. That would be great.

Absolutely!

Thanks as well Indrek!

Hi, thanks. That's very nice of you. More followers on this channel, would be a good thing. My other one has way more. I guess, KZbin doesn't really like videos with just 100 seconds. Too long for a short and too short for a normal one :)

Thanks Dany, we should talk soon!

Thanks for your support!

Hi, I don't think that your statement applies here. Given, there is no difference between class-based and function-based components, I would say your statement fits and I would also agree. But the situation is a different one: The Angular team only would consider such a huge change, if it turns out that certain future features can ONLY be done with functional components. So they don't switch because it looks more modern, they would switch if there is an absolute need for it. Does that make sense or how do you see it?

Most people are against functional components, cos human by nature, once get used to current way of doing things, will refuse to switch over to the other direction, as it takes time to get used to it. If Angular is to begin with functional components in the first place, i bet many people will start protesting, when switches over to class components. 🙂 For me, I support functional components as long as the benefits (over its cons) is justifiable.

It is coming Dany!

Yup, me too. I stumbled upon it in React two years ago, but didn't pay too much attention. This time, it will be different ;)

Merry Christmas to you as well. Thanks for your support.

You're welcome. Merry Christmas to you as well.

Happy holidays. We still have two episodes to go :).

You're welcome again :)

Sure, next video will be released in a couple of minutes

Welcome!