In Ember this was easily solved by query parameter bindings on the controller (http://emberjs.com/guides/routing/query-params/). As stated in the Ember documentation "By default, a query param property change won't cause a full router transition (i.e. it won't call model hooks and setupController, etc.); it will only update the URL.", meaning that if I changed the bound values on the controller the URL would change without a transition, however if the URL was changed by others means (link etc.) a transition would normally occur. This is essentially the behaviour I'm looking for.
-ra Den måndag 12 januari 2015 kl. 08:14:56 UTC+1 skrev Sander Elias: > > Hi Rasmus, > > Yes that would require a bit of work indeed. If I'm informed correctly the > new router coming in 1.4 will have the handles you need to tackle this. I'm > not that familiar with ui-router enough to know if there is a solution for > this. > The problem is, how does the router "know" when it needs to route, and > when not? > > Regards > Sander > -- You received this message because you are subscribed to the Google Groups "AngularJS" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
