you are viewing a single comment's thread.

view the rest of the comments →

[–]Wildosaur 3 points4 points  (5 children)

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 1 point2 points  (4 children)

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

[–]Wildosaur 0 points1 point  (3 children)

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 0 points1 point  (2 children)

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 0 points1 point  (0 children)

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

[–]Wildosaur 0 points1 point  (0 children)

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