Resolves being cached / only called once

[rosslavery]

Seems to be a difference in how resolves are handled compared to ngRoute.

In a CRUD application, imagine a list state /accounts/. This state has a resolve to grab the list of accounts before the controller loads.

This view contains a "new account" button which takes you to /accounts/new/ .

The user creates a new account and get's redirected back to the listview /accounts/.

The newly-created account is not visible in this view because the resolve is only called once, not every time the state changes.

Is this expected behaviour? Is there a way I can cache-bust on-demand?

[ghengeveld]

Related issue: #76

[nateabele]

Fixed.

[ghengeveld]

Thanks a lot! A new release would be nice, so Bower will pick it up automatically.

[nateabele]

Soon.