วีดีโอ

Yes, it solves a real need.

Yes, yes, NgRx 19 is imminent but I want to wait for the next patch/minor release. Btw, it will come in the other channel. This is here is ng-news 😅

Thanks, yes, we usually focus more on the technical aspects but there other things as well. A manager for a big application will very likely prefer the Wiz cooperation over zoneless.

I don't know.. I still feel the burn from Stadia.... and still miss it.. nothing comes close to the convenience it gave.

Yeah, Hydration + SSR is a topic I want to cover in my other TH-cam channel. It is going to be a longer video.

No problem 👍

Happy New Year to you as well Alain. Thanks!

Hey Tayamba, thanks. I still have to publish the yearly review but then everything is towards 2025

Good to hear

It is really worth it!

Thank you, I say the current pace with 1 video per week is good. If you want to have more deep-dive videos, you can also checkout my personal channel www.youtube.com/@rainerhahnekamp

You're very welcome. If you are using Angular 19, you have now the option to go with linkedSignal btw.

Yup, I've hoped that resource also makes into developer preview. Either way, I guess I will use it even in experimental status.

Oh, I think so. This is the default behavior of ngModel. We had the same issue with NgRx. If you use template-driven forms on a state coming from the NgRx Store, then you would see an error because of the mutable change.

@@ng-news Hey, Rainer, regarding this issue, I found what I think might be a clean way to solve this in projects that use @ngrx/signals: make the linkedSignal return a signalState of the input with the data you need for the form, so you have signals for each property, that can be passed to ngModel directive. Then ngModel will immutably update that signal, instead of mutating the wrapped signal object property like the previous solution. Something like this: formModel = linkedSignal( () => signalState({. prop1: this.inputSignal().prop1 ?? 'creationDefaultValue' })); and in the form, just the same: <input ... [(ngModel)]="formModel.prop1" />. What do you think?

You are very welcome

Yes, the sub-optimal TypeScript support is just one of many issues.

You're very welcome

Thanks!

Also here, collect your thoughs and once the RFC arrives, let them know.

I only know that there are some real technical issues with the current approach. I hope though, that they will publish an RFC very soon.

Looks like you ain't so happy about it 😅

Well, nothing has decided yet. We will have to wait for the RFC to fully understand what's behind it.

Well, hard call not to mention that topic in ng-news, but I got you :) Quite a polarizing topic.

There will be an RFC with some insights. I'd wait for that for that.

Sorry, I don't quite understand. When you run playwright, it doesn't pick up your existing Jasmine/Karma tests but looks into the folder defined by playwright.config.ts

@@ng-news ya no worries. I was thinking about saving some package spaces since I don’t quite want to use karma and jasmine but it seems like I have no choice since component unit test are still done by karma and jasmine it seems. The auto generated tests fail in “ng test” and it takes some research to figure out how to add the proper providers declarations to make them pass. And different providers (router ones and http client ones)

Thanks a lot!

You're very welcome

Well, you are very welcome 🙏

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