-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
[BUGFIX] Don't use destroyApp if new API is being used #16229
Conversation
This seems good, but I think you also need to fixup the fixture that we test against (the blueprint tests are failing)... |
Will fix on Monday.
|
Ping as a friendly reminder @Serabe! |
instance-initializer-test blueprint also needs to be updated. |
Had a tough week. Try to do it tomorrow, as today I am attending a conference. |
Found the problem. I forgot to commit two files (-‸ლ) |
@@ -13,7 +13,7 @@ module('<%= friendlyTestName %>', { | |||
}); | |||
}, | |||
afterEach() { | |||
destroyApp(this.application); | |||
<% if (destroyAppExists) { %>destroyApp(this.application);<% } else { %>run(application, 'destroy');<% } %> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should be run(this.application, ...)
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done. Thank you
@rwjblue I believe this is a bugfix for 3.0 stable? |
Fixes #16180