@XaserAcheron wrote:
I've run into a scenario where I don't know what
queryParams
to put on my heavily data-driven route until after themodel
hook is complete. As far as I can tell, Ember doesn't natively let you do this.The gist of it is I'm looking for some sane way of either:
- hackifying the
queryParams
hash after loading the model, or- just accepting whatever-the-heck parameters I pass to
transitionTo
.The closest I've been able to Google is this Stack Overflow answer in which the OP conceded to base64-encoding the set of parameters and shoving them in a generically named bucket, which is pretty icky.
Now, reading arbitrary query parameters is easily doable, turns out. I just can't figure out how to set them.
Any thoughts? How far into feature-request-ville are we?
Posts: 1
Participants: 1