-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
Remove @ember/runloop from initializer test blueprints #21067
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
base: main
Are you sure you want to change the base?
Conversation
Estimated Asset SizesDiff Details
|
| import { module, test } from 'qunit'; | ||
| import Resolver from 'ember-resolver'; | ||
| <% if (destroyAppExists) { %>import destroyApp from '../../helpers/destroy-app'; <% } else { %>import { run } from '@ember/runloop'; <% } %> | ||
| <% if (destroyAppExists) { %>import destroyApp from '../../helpers/destroy-app'; <% } %> |
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.
do we really still support destroy-app? O>o
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.
That's part of that old-style of testing that we talked about that I don't think was ever deprecated. It is possible it was broken at the blueprint side, though.
NullVoxPopuli
left a comment
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.
Thanks for doing this -- there is potential we could remove more tho -- trying to figure that out 🤔
Summary
Remove @ember/runloop usage in initializer/instance-initializer test blueprints and fixtures by calling destroy directly when destroyApp helper is unavailable.
Testing
Fixes #20690