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
Hi, there. I have an addon which uses and extends ember-modal-dialog . However, when running tests of our addon, the test suddenly fail after adding ember-cli-addon-docs. Specifically, the dialog no longer inserts its overlay (and our tests verify this). This appears to be due to the fact that ember-cli-addon-docs extends the default dialog in this file: addon/components/modal-dialog/component.js therefore, our unit-tests fail because we are in a testing mode.
How should we proceed? We do not want to change our tests, because clearly this will be testing the wrong thing. Is there a reason why this has to be in place for ember-cli-addon-docs ?
The text was updated successfully, but these errors were encountered:
and changing all references to modal-dialog elsewhere in the addon to our-modal-dialog. It would seem that a better approach would be to have ember-cli-addon-docs re-export its version of modal-dialog as a different name so as to avoid colliding with dialogs in an addon when testing.
Hi, there. I have an addon which uses and extends
ember-modal-dialog
. However, when running tests of our addon, the test suddenly fail after addingember-cli-addon-docs
. Specifically, the dialog no longer inserts its overlay (and our tests verify this). This appears to be due to the fact thatember-cli-addon-docs
extends the default dialog in this file:addon/components/modal-dialog/component.js
therefore, our unit-tests fail because we are in a testing mode.How should we proceed? We do not want to change our tests, because clearly this will be testing the wrong thing. Is there a reason why this has to be in place for
ember-cli-addon-docs
?The text was updated successfully, but these errors were encountered: