(bug) Latest ui-router breaks $state.param changes #1589
Labels
Comments
|
We should continue to watch the ui-router issue tracker to see if anyone else runs into these issues. |
jniles
pushed a commit
to jniles/bhima
that referenced
this issue
May 4, 2017
The latest ui-router (v1.0.0) creates breaking changes in state changes that do not seem to be documented anywhere. This is a quick downgrade to allow seamless development while we debug the issue. Closes IMA-WorldHealth#1589
jniles
added a commit
that referenced
this issue
May 4, 2017
The latest ui-router (v1.0.0) creates breaking changes in state changes that do not seem to be documented anywhere. This is a quick downgrade to allow seamless development while we debug the issue. Closes #1589
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The Angular UI Router project just released version 1.0.0. We had upgraded to the first release candidate (RC1), but it seems their
$state.paramprocessing has changed in the latest release.In particular,
ui-srefand$state.go()both do not refresh their parameters after an initial call. There may be a way to coerce this usingui-sref-optsand a similar method for$state.go, but it is undocumented and I do not have enough time to try each permutation of options. Many of the$stateParamDeclarationoptions I have already tried with no success.I propose we revert to a stable
ui-routerversion and calmly upgrade. Ironically, for us this will berc-1. It is this issue that has been breaking Travis.The text was updated successfully, but these errors were encountered: