Controller initialised after a $state.go with {notify: false}

[caillou]

The Bug

When a $state.go is called with {notify: false} as follows, a bug occurred:

$state.co('foo', {}, {notify: false})

On the next state change, the current controller will be initialised a second time.

Plunker Link

Follow the steps to reproduce on Plunker:

http://plnkr.co/edit/wMiVOb?p=preview

[eddiemonge]

It does indeed look like a bug.

[PhiLhoSoft]

See #2087, looks similar. Very annoying when a controller loads data on initialization.

[RickWalker]

This is the same issue as #1673 which is apparently fixed by PR #2003, so hopefully it should be easy enough to solve.

[eddiemonge]

similar to #1673 but slightly different I think

[jessezhang91]

It's a little different from #1673 but should still be fixed by PR #2003. The actual issue I was having is described in this bug.

[eddiemonge]

marking as duplicate of #2087