-
Notifications
You must be signed in to change notification settings - Fork 31
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
Fixes deprecation warning regarding using includes
over contains
#43
Conversation
twokul
commented
Sep 22, 2016
•
edited
Loading
edited
/Users/anavasar/Desktop/Screen Shot 2016-09-22 at 8.58.09 AM.png
@@ -2,12 +2,6 @@ | |||
module.exports = { | |||
scenarios: [ | |||
{ | |||
name: 'default', |
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.
not sure what this was for since tests are running against release
, beta
and canary
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.
Good point, probably don't need that. Can you update .travis.yml
to eliminate that test run as well?
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.
will do
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.
@ronco done!
/Users/anavasar/Desktop/Screen Shot 2016-09-22 at 8.58.09 AM.png
@ronco could you publish a new version? |
@twokul Published as 3.0.1 |
@ronco thanks! |
It should be noted that this breaks compatibility with all Ember versions below 2.8. A backward-compatible solution would be to use the ember-runtime-enumerable-includes-polyfill |
Thanks for pointing that out @simenheg . I definitely dropped the ball on the semver compliance there. I'll try to get a version with the polyfill out soon. |