state.query not set until navigate

[jondashkyle]

When going to a direct link with a query string, such as /example?foo=bar, the state object does not contain query. But, if you navigate to that URL by clicking a link, it’ll appear as expected.

That seems to be a bug, but just checking the intent before filing a PR. One other question; should query always be in state, similar to params? Could reduce a check or two.

[yoshuawuyts]

Yeah, it should always be in there. Definitely sounds like a bug.

…

On Fri, Aug 18, 2017 at 5:38 AM Jon-Kyle ***@***.***> wrote: When going to a direct link with a query string, such as /example?foo=bar, the state object does not contain query. But, if you navigate to that URL by clicking a link, it’ll appear as expected. That seems to be a bug, but just checking the intent before filing a PR. One other question; should query always be in state, similar to params? Could reduce a check or two. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#549>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACWleo4VXSL6HVDL25ZiJCUzldwDdG7-ks5sZQc4gaJpZM4O7EEL> .

[mantoni]

Just ran into this as well. The state.query object is populated properly, but I have to delay reading from it. It's not yet populated during model initialization.

[yoshuawuyts]

Yeah, we should probably document properly that all of these values are only initialized _after_ DOMContentLoaded

…

On Mon, Sep 4, 2017, 19:01 Maximilian Antoni ***@***.***> wrote: Just ran into this as well. The state.query object is populated properly, but I have to delay reading from it. It's not yet populated during model initialization. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#549 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACWleqRx0zJ7FPzsTYeQHKDr3m-kPJ6sks5sfCz_gaJpZM4O7EEL> .

[yoshuawuyts]

Should be fixed in choo@6.7.0 🎉