transitionTo queryParams on initial render still broken

[zidjian257]

The problem described in #12169 still exists, so I'm filing a new ticket, as the initial ticket is already closed.

[zidjian257]

the only aproach to get around this in ember 2.10 for me was the solution posted by @taras on 23 Dec 2015 in #12169 (the other solutions mentioned didn't work):

let RedirectAfterDidTransition = Ember.Mixin.create({
  redirectAfterDidTransition(...args) {
    this.router.one('didTransition', ()=>{
      this.router.transitionTo(...args);
    });
  }
});

export default Route.extend(RedirectAfterDidTransition, {
  afterModel() {
    this.redirectAfterDidTransition('index');
  }
});

[Serabe]

Updated jsbin to Ember 2.11.
Updated to 2.12 beta 1 and seems fixed can you provide a test that breaks under 2.11 but is fixed in 2.12 to make sure we don't have a regression?

Thank you!

[rafaelbnp]

+1 on this. Having same issue!

[GCheung55]

Seeing this on 2.10.2. Here's the stacktrace:

TypeError: Cannot read property 'name' of undefined
    at Class._queryParamsFor (vendor.js:47541)
    at Class.finalizeQueryParamChange (vendor.js:45361)
    at Router.triggerEvent (vendor.js:47954)
    at trigger (vendor.js:75664)
    at finalizeQueryParamChange (vendor.js:77652)
    at Router.queryParamsTransition (vendor.js:76999)
    at Router.getTransitionByIntent (vendor.js:76908)
    at Router.transitionByIntent (vendor.js:77017)
    at doTransition (vendor.js:77619)
    at Router.transitionTo (vendor.js:77093)

[kbullaughey]

I'm seeing this on 2.13.

[akaravashkin]

+1 on 2.13.3

[jemware]

I’m seeing this in 2.14.0

[gschulze]

Running into the same issue on 2.15.0.

[divmgl]

Ember 2.16.2 still has this issue

[gschulze]

So this still happens on 2.18.0. Really?

[bretjb]

@gschulze I am seeing this on 2.18.

[alvinvogelzang]

I'm still experiencing this issue as well in Ember 2.18

[pixelhandler]

@GCheung55 @akaravashkin @alvinvogelzang @bretjb @divmgl @gschulze @jemware @kbullaughey @locks @rafael-paiva @zidjian257 Just curious is this still an issue in Ember 3?

[rafaelbnp]

@pixelhandler I'm still on the LTS 2.18.2 and I don't have the time now to check Ember 3... sorry