-
-
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
link-to in integration tests throw: Cannot read property 'applyIntent' of undefined #15831
Comments
@bekzod - Would you mind taking a look at this? This is exactly the scenario (e.g. |
@rwjblue sure I am looking |
@rwjblue sorry couldn't resolve this, dug a bit found |
Hmm. I didn’t think the issue was only for inline link-to. I’ll test though. |
Can confirm this.
This as well: happens for inline as well as block form of |
Fixes emberjs#15831 Fixes a regression introduced by emberjs#15788 by returning early again from `routing.generateURL()` when `router._routerMicrolib` is not present.
Fixes emberjs#15831 Fixes a regression introduced by emberjs#15788 by returning early again from `routing.generateURL()` when `router._routerMicrolib` is not present.
Fixes emberjs#15831 Fixes a regression introduced by emberjs#15788 by returning early again from `routing.generateURL()` when `router._routerMicrolib` is not present.
The following error occurs on canary (but works properly on prior releases) for this test:
The test is attempting to ensure that a component integration test is capable of rendering a
{{link-to}}
even when the router is not booted/available.Demo repo here
I suspect it was caused by one of the following PR's which have changed things in the routing and/or link-to area:
routeArgs
#15788active
computed property #15779_isActive
returns boolean inlink-to
#15762extractQueryParamsArgument
#15811The text was updated successfully, but these errors were encountered: