Signals in ng-bootstrap about ng-bootstrap HOT 7 OPEN

I would first try to be zoneless and then try to move to signals, for the following reasons:

• zoneless support should be possible without moving to signals, with a smaller effort
• moving to signals is a harder task, maybe necessitating breaking changes in the API, and would rely on features that are not stable yet (effect, toSignal, toObservable)

from ng-bootstrap.

Zoneless could probably be achieved by keeping the code as is, but there are usages of NgZone (onStable) that need to be replaced. I started it try doing it by replacing them by afterRender or afterNextRender, but there are places where it's quite hard.

But I agree that, for the long term, using signals where it makes sense would be a good idea.

from ng-bootstrap.

@bastienmoulia as others are saying, signals are not required for zonless

from ng-bootstrap.

• when using ng 18: provideExperimentalZonelessChangeDetection and NgbModal.open(myComponent) is not working
• in dom I see element, but not rendered propery
• the same problem with Toast
• the same problem with Tooltip

from ng-bootstrap.

Please open separate issues for zoneless support with concrete failures.
I think we should release a major first with Angular 18 support and then add zoneless in a feature release, WDYT?

from ng-bootstrap.

Please open separate issues for zoneless support with concrete failures.

I think we should release a major first with Angular 18 support and then add zoneless in a feature release, WDYT?

Sure thing, first Angular 18, then we can add signal everywhere, and then activate zoneless!

from ng-bootstrap.

Indeed, I wasn't talking about signals at all in my comment, it should be last for me too for sure.

from ng-bootstrap.