-
-
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
Cleanup Ember.Test, Ember.testing, Ember.onerror #13440
Conversation
Looks great @krisselden one more step towards tree shaking. |
a984954
to
5b3aa53
Compare
|
||
deepEqual(caught, thrown); | ||
|
||
Ember.onerror = undefined; | ||
setOnerror(undefined); |
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.
I realize that this was already like this, but we should probably reset in a tear down in case the test dies.
5b3aa53
to
1103968
Compare
RSVP.configure('async', function(callback, promise) { | ||
var async = !run.currentRunLoop; | ||
const backburner = run.backburner; | ||
run._addQueue('rsvpAfter', '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 we use a private symbol for this? I'd hate for folks to try and schedule into our special queue.
Then again, arguably all of the backburner queues are private so....
@krisselden - This looks very good to me. I would like to test ember-qunit with these changes to make sure things work properly. I should be able to finish that tonight or first thing tomorrow morning... |
@rwjblue anything I can do to help verify ember-qunit? Would it just be running its test suite against this? I also will update if issues come to light. |
☔ The latest upstream changes (presumably #13447) made this pull request unmergeable. Please resolve the merge conflicts. |
1103968
to
d9f57e8
Compare
Originally [this line](https://github.com/emberjs/ember.js/blob/3ab8ba2af6551a174f3b91ac9b202bc9f27c09a4/packages/ember-views/lib/system/jquery.js#L8) was checking for a global `require`, but as of #13440 we changed to import or own internal `require`. At the moment, that `require('jquery')` (using our internal loader's version of `require`) will never find a module named `jquery` and will error. I believe we should just remove this guard/check completely. We can always reevaluate if folks still need this for something...
Remove broken `require('jquery')`. Originally [this line](https://github.com/emberjs/ember.js/blob/3ab8ba2af6551a174f3b91ac9b202bc9f27c09a4/packages/ember-views/lib/system/jquery.js#L8) was checking for a global `require`, but as of #13440 we changed to import or own internal `require`. At the moment, that `require('jquery')` (using our internal loader's version of `require`) will never find a module named `jquery` and will error. I believe we should just remove this guard/check completely. We can always reevaluate if folks still need this for something... /cc @krisselden
Originally [this line](https://github.com/emberjs/ember.js/blob/3ab8ba2af6551a174f3b91ac9b202bc9f27c09a4/packages/ember-views/lib/system/jquery.js#L8) was checking for a global `require`, but as of emberjs#13440 we changed to import or own internal `require`. At the moment, that `require('jquery')` (using our internal loader's version of `require`) will never find a module named `jquery` and will error. I believe we should just remove this guard/check completely. We can always reevaluate if folks still need this for something...
No description provided.