Alex
Alex
@SergeAstapov any idea why the try scenario might be failling now? they are all fine locally I'm just about giving up on those try scenarios as something is not working...
all green 🎉 @SergeAstapov
> @void-mAlex let me know if I understood it correctly: Can't we use the query params with these changes? If yes I think that's a big regression > > [#855...
so to clarify for anyone not following the links, you can still use query params, there is a specific subcase where you transtition without a route name that appears to...
Hello @LucasHillDex we're working tightly with the ember routing work to make sure engines are better supported going forward out of the box would love to know what workaround you...
> Any update on this team? We were also facing this issue. Kindly do the needful. @runspired @rwjblue @SergeAstapov this is already fixed and merged, just waiting on a release...
fixed by https://github.com/ember-engines/ember-engines/pull/849
the are one or two small blockers to clear still, but roughly things should start rolling in the next two to three weeks sooner if things go well
hello @yandiro I can tell you about my use case for not having a rootURL set or more precisely for having it be a relative one to where the build...
having just upgraded to v2 we also saw issues with `miragejs` and a few others ending up in production build when they are only referenced in test files we temporarily...