not firing gsapify router on initial app load about angular-gsapify-router HOT 5 CLOSED

could line 146 be optional?

var duration = $state.previous.name === '' ? 0 : from.duration, // don't trigger transition on boot

from angular-gsapify-router.

What are you actually trying to do? Animate a state in at the beginning?

If so then the simplest thing to do is probably just trigger the state by forcing the transition with $state.go('stateName', {reload: true}) or switching to a blank intermediary state and then immediately switching back.

from angular-gsapify-router.

exactly. have been figuring out workarounds to trigger a transition on boot on every site I've used this on, feels a bit hacky though. would making transition on boot configurable cause any issues? if not I don't mind making a pull request...

from angular-gsapify-router.

Well it would be a pretty major change - the reason its setup this way is to mirror the behaviour of ui-router which doesn't cause a transition on initial load, I've taken this to be the expected behaviour now.

The obvious place for this option would be the provider, you'd then set it in the config stage of the app:

gsapifyRouterProvider.initialTransitionEnabled = true; // false by default

Would definitely take a PR for that...

from angular-gsapify-router.

Ah ok, great have sent a PR

from angular-gsapify-router.