Matthieu Riegler

I'm moving this to major / breaking change as it was discovered that there were already usages of a formArray directive (or formArray as input) inside Google.

G3 has been cleaned-up but bummer we missed the v20 breaking change window. This is a breaking change due to the typing change for the `formDirective` getter.

Converting back to draft until we enter the breaking change window.

[Passing TGP](https://fusion2.corp.google.com/presubmit/743508088/OCL:743508088:BASE:793907211:1754992560138:23b43fec;groups=NewlyFailing,PossiblyNewlyFailing,PossiblyAlreadyFailing/targets)

> JS can easily support this type of obfuscation at runtime via [private propties](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Classes/Private_properties) (#value) and abstraction Private properties are kinda bad performance wise if you have to downlevel them,...

This is by design, your resource is awaiting its value and by nature keeps the app unstable.

Hi, could you reformat the file with `yarn ng-dev format files packages/language-service/src/quick_info_built_ins.ts` to satisfy the linting job. Thank you.

Could you please squash both commits, we'd like the change to be a single commit.

It's an interesting approach @OmerGronich Capturing this idea in a typesafe demo: https://stackblitz.com/edit/angular-extended-signals?file=src%2Fmain.ts

A narrowed down repro: https://stackblitz.com/edit/stackblitz-starters-u3sbf6?file=src%2Fmain.ts