You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our addon uses ember-bootstrap but the element #ember-bootstrap-wormhole is not automatically added to the DOM in the app that uses this addon. The configs (such as insertEmberWormholeElementToDom = true) in the addon's ember-cli-build.js file don't apply to the app AFAIK. So where to put these configs in case of an addon?
It works if ember-bootstrap is added as a dependency of the ember-app. But I does not work if ember-bootstrap is a dependency of an ember-addon which in turn is consumed by the ember-app.
It looks like the contentFor() hook is only called in the first case.
Not sure if this is something we can or should solve in Ember Bootstrap. It seems to be a design decision to not run contentFor hook of indirect v1 dependencies. v2 addons does not have a contentFor hook as far as I know. We likely need to change how the wormhole target gets into the index.html anyways when migrating to a v2 addon. See #1980 (comment) for details.
Our addon uses ember-bootstrap but the element
#ember-bootstrap-wormhole
is not automatically added to the DOM in the app that uses this addon. The configs (such asinsertEmberWormholeElementToDom = true
) in the addon'sember-cli-build.js
file don't apply to the app AFAIK. So where to put these configs in case of an addon?Output from
ember bootstrap:info
(in the addon):The text was updated successfully, but these errors were encountered: