Hi there. Thank you for your contribution to Angular.

I'm sorry but at the moment we are not interested in allowing the default strategy to be part of our public API and to be extended by third parties because it would tie our hands in improving and modifying this default in the future.

Please feel free to implement the NgElementStrategy strategy api and feel free to use the ComponentNgElementStrategy as an inspiration for your implementation.

It was suggested yesterday by @gkalpak, in #24181, based on the publicApi annotations in the code.

If you don't want to expose the strategy, just exposing the ComponentNgElementStrategyFactory (and changing the create() signature to return NgElementStrategy) would let you change the strategy at will, but still let library developers wrap existing behavior.
Right now to do this, I have to create a dummy element with the default strategy, just so I can reach into it and get the strategy to wrap it.

thanks for the additional context @remackgeek. I just spoke with @gkalpak and suggested some alternative solutions. He's going to post a comment with the details. I think the problem you are trying to fix is worth fixing, it's just that the change you proposed here is not heading in the right direction. @gkalpak will share more details. thanks!

So, basically, making the strategy (and corresponding factory) part of the public API will increase the maintenance cost by making it harder for us to make changes to them in the future (either fixinf bugs or making improvements).

If anyone wants to define their own strategy, they need to implement the NgElementStrategy interface. This makes things a little more complicated/verbose for people wanting to make a small change to the ComponentNgElementStrategy by entending it, but we feel the benefits are worth it.

Regarding the problem with Zones (#24181) in particular, we decided it is worth fixing in @angular/elements, i.e. with something similar to #24185. So, let's continue the discussion on #24185.

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}