Paul Gschwendtner

Results 146 comments of Paul Gschwendtner
trafficstars

@JeanMeche I think this still needs a review, or should we ignore?

This PR was merged into the repository by commit d60bb51badd0363505f0892da3c0e84917cf5a20. The changes were merged into the following branches: main, 18.2.x

**Disclaimer**: Just some hint/trick that might be useful as a workaround for some folks. This still needs to be fixed. I just wanted to post what we have been doing...

This PR was merged into the repository by commit 2ece9dff75b0ee8800e78576531c5f042017d97a. The changes were merged into the following branches: main, 18.2.x

This PR was merged into the repository by commit 46a6324c82a41b69c16a4c8c9f3fc52d1ecf6917. The changes were merged into the following branches: main, 18.2.x

Closing as we did submit a couple of updates in between; and let's get a fresh PR.

Just to capture: I think this is not 100% ready, as we could have a "safe" method where possible. Related discussion: [here](https://angular-team.slack.com/archives/C04P61VFM2S/p1727375803119679?thread_ts=1727373634.939839&cid=C04P61VFM2S), or in some other thread.

I might miss something from a quick glance. What would happen if someone wants to explicitly avoid the ng-content default and project zero nodes? Should `null` be used for explicitness...

It does sound like this would be a breaking change though?

I will defer to @crisbeto on how to treat this, as he is the expert on projection and its APIs. @diesieben07 I think it wouldn't be a breaking change, if...