[mdngtcdr]

Hi, I've been using AngylarJS & UI-Router for about 2 months. It's great. Some of the shortcomings that struck me were-

Lack of "routing state" - integration with the history API or means to go to "previous" state etc.

No clarity in handling errors from "resolve" - Since there is no controller any failed AJAX request fails silently.

Ability to pass data (not params, more like a model) between states. This I think sparks the debate of having services to share data. But there are use cases wherein you would want to transition to-fro controllers (eg. multi page form).

[christhielen]

Hi, ui-router dev here. 1.0 is adding a global transition error handler which you can customize. The handler will be noisy by default (log to the console).

To send data in a transition, add a non-url param to the target state. We added objects-as-params (url based or not) in I think 0.2.12

[nateabele]

> But there are use cases wherein you would want to transition to-fro controllers (eg. multi page form).

This is interesting. Could you post a GitHub issue describing your use case and an pseudocode example of how you'd see it working?