-
-
Notifications
You must be signed in to change notification settings - Fork 154
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
Deprecate legacy test APIs #483
Conversation
5f2a4ee
to
247482d
Compare
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.
We might need to do a deprecation RFC for this 🤔
addon-test-support/ember-qunit/legacy-2-x/module-for-component.js
Outdated
Show resolved
Hide resolved
addon-test-support/ember-qunit/legacy-2-x/module-for-component.js
Outdated
Show resolved
Hide resolved
2e46809
to
c7987d2
Compare
As we discussed, these deprecations were laid out in RFC#232 |
addon-test-support/ember-qunit/legacy-2-x/module-for-component.js
Outdated
Show resolved
Hide resolved
I'm 👍 on this change. I think it's a good time to start moving apps/addons off the older APIs. |
c7987d2
to
6e4d155
Compare
lol, I totally missed this PR but did pretty much the same thing for |
This deprecates the
moduleFor
,moduleForComponent
andmoduleForModel
APIs. This implements the deprecation section of RFC#232.