-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NgxPopperModule.forRoot should be only used with AppModule #117
Comments
just checked the source, you are using the provider to set the default options, and provider is module indepentend, so by your design this is the correct result. you might need to change from plain string
this will make |
no, the problem is not the InjectionToken, because in module you write:
this will make any module import use a empty option, to use a default option, we need to use |
@steve3d , thanks for bringing this up, sorry for the late reply, ill look into your PR |
when can we expect the new version? |
I just stumbled across this, when upgrading a library of mine which uses NgxPopper. |
@steve3d if you're interested I'm about to fork this project because I noticed that MrFrankel has not been answering lately, I need this and I don't want the extra forRoot and I need to make everything work with Angular 9 for a project I'm working on... |
@steve3d just released [email protected] with some improvements, like this and upgrade to @popperjs/core 2 |
to my understanding, the module.forRoot should be only used in bootstrapped module, and any options passed by forRoot should be inherit into any other module.
but now ngx-popper need to use forRoot on every module and repeatly set the options. the options didn't inherit from the bootstrapped module.
So I don't know if this is the design or something wrong?
The text was updated successfully, but these errors were encountered: