-
-
Notifications
You must be signed in to change notification settings - Fork 259
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
Do not register a router service for Ember <1.13 #100
Conversation
@@ -4,6 +4,13 @@ import { Klass } from 'klassy'; | |||
import { getResolver } from './test-resolver'; | |||
import buildRegistry from './build-registry'; | |||
|
|||
function hasEmberVersion(major, minor) { |
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.
Can you move this to its own file? We have a scenario in tests (for closure actions) where we are using a regexp to determine if a given test should run, and this is a much cleaner solution.
Something like /lib/ember-test-helpers/has-ember-version.js
?
Can you confirm that the test added here failed prior to the changes? |
BTW - The failure in Travis is for canary builds and is being tracked in #99. |
34e13b9
to
efe7690
Compare
Confirmed that the only failure here is the one in #99 |
Versions of Ember prior to 1.13 require a full router booted by the app, or no router at all. This ensures they receive no router at all instead of the 1.13-safe one.
efe7690
to
7df5b66
Compare
Do not register a router service for Ember <1.13
Thank you! |
Supposedly fixed with emberjs/ember-test-helpers#100 , but still seeing the same problem.
Versions of Ember prior to 1.13 require a full router booted by the app, or no router at all. This ensures they receive no router at all instead of the 1.13-safe one. Result is that the link-to helper can be used in Ember 1.11 and 1.12 component tests (unit and integration).
See also these PRs that attempted to fix the issue in Ember:
IMO, it is more appropriate that it be fixed here, since ember-test-helpers is basically dealing with fragile/intimate API surface when it sets up a router in the container.