Chris Thielen
Chris Thielen
Agreed, but very low on my priorities list. PR welcomed.
@chrisguerrero that's happening because of Future States retrying the initial transition. Future states resyncs the URL after all the async state loading is complete. It does this in case the...
PR welcomed.
So it happens for unminified build too, I see
Sorry I didn't respond sooner. Future states should be intercepting the `.otherwise()` call and checking if the URL `/some2` matches any of the pending future states. Here's how it does...
It's not by design. Before ui-router 0.2.16 or so, the options was not available in the $stateChangeStart event, so it wasn't even possible. However, it's certainly possible now. I'd love...
I haven't found a clear solution to implement that use case with ui-router states. Maybe you can ng-repeat some custom directive, then show/hide the appropriate one. What goes on in...
future states are not compatible with ui-router 1.0, sorry. UI-Router 1.0 final will probably be released without any future states support. I'd like to bake something like future states (but...
See https://github.com/christopherthielen/ui-router-extras/issues/336
If you're using ui-router-extras only for future states, you might have better luck with ui-router 1.0 beta. It has support for lazy loading and adding/removing states on the fly baked...