I’ve been hacking on a pure client side pagination / filtering / sorting mixin for some time and recently I got it working for RC1.
The fiddle above is what I have currently and it does work … if you only use 1 part of the mixin at a time.
For example, if I got to page 2 but then decide to filter the content down my window.location drops the page # and throws up the filter.
Or if I start filtering, but then decide to hit page #2 the filter is dropped from window.location and the page is added.
The reason my use case requires this is for a simple “copy / paste” situation where my customers want to share a url and in doing so they really benefit from the full context (ie- what page/search/sort was used to achieve the desired view into the controllers model)
So a legit url with all the data might look like this
My question here is really about the ember v2 router api -was it designed for this scenario? If not today could it be in the future? What would need to change to support this?
Also for the stackoverflow like response -is there something I’m doing above in the fiddle that is causing this not to work when it is technically possible?