Open mpanic opened 4 years ago
Hi! sorry I've been away from this project for a while. :(
Is there code you can provide to help me more explicitly / accurately reproduce your scenario?
I finally got around to doing some maintenance on this repo and released a new version (as a v2 addon, and basically no other changes).
Any chance you can create a failing test that describes the desired behavior? thank you!!
I have the following routes:
application/route.js
(defines queryParampreCheck
)application/controll.js
(defines aliasqueryParams.current.preCheck
)master/route.js
(defines queryParamsearch
)master/controller
(defined alias for queryParamqueryParams.current.search
)Both routes have the same path: '/'
When I load the page, it throughs the following error:
If I try to use
preCheck
it works just fine. NOTE: it's in theapplication
routeIf I try to reference query param
search
from both router and controller, I get the error. If I don't use it in either router or controller, it works just fine. NOTE: it's in the "nested"master
route, which is underapplication
route.What are the chances that we can't use queryParam from both router and controller in nested routes?
UPDATE:
After some debugging of the addon, looks like it fails as the
transition.from
andtransition.to
are bothnull
and that makes sense as I'm loading the route for the first time. But the error message is saying that "same query param" cannot be refered from both router and controller: