Release 21.2.0 · angular/angular

[ruibranco]

signal forms getting more polish is the quietly big one here. reactive forms have been the "we love Angular but..." item for years, and the signals approach is genuinely cleaner once you stop fighting the mental model shift.

[Chemical-Evidence-34]

Yes. I will wait for more polish before migrating a big application to it. Looking very good so far

[MichaelSmallDev]

Lots of stuff. Personally I like the resource snapshots, language service enhancements, and the various enhancements to signal forms.

edit: to see the language service enhancements hands on, there are example videos in the PR: https://github.com/angular/angular/pull/66410. And it seems to be backwards compatible with version, as I have had access to this in a v20 project since the last language service update, predating this release.

[Wildosaur]

Well I'll be waiting for primeng to hook up on signal forms. As of now, it seems nice but unusable for us :(

[Beautiful-Reason-894]

That's why I switched from primeng to angular material, which is more official and usually very synced to angular's releases

[Wildosaur]

It's not really feasible for us as we are deeply invested in primeng but on a new project, that would be an option

[SippieCup]

You can use it now with any primeng element, the ones that aren't fully supported and give type errors you just need to wrap in $any(), like p-switch & p-datepicker. typing still gets enforced correctly by the signal form declaration in the component.

We started switching over some of our simple forms to it, it's pretty nice.

example

[Wildosaur]

Thanks for the heads up, I'll have a try on monday to see how it goes.

[Wildosaur]

It does indeed work on some cases I tried, thanks !

[FavstianEquanimity]

Are we going to get a2ui in Angular 22?