The One Where They Finally Included Release Notes
diff
Nate and I are excited to release UI.Router 0.2.8! Many thanks goes to @nateabele and
various contributors for continuing to maintain the ui-router code base. If you follow the repo, you've noticed that popularity and adoption of ui-router is increasing steadily. We truly believe ui-router represents the future of routing and UI management within Angular and the core team agrees. We hear all the time that ui-router serves as the cornerstone of many applications, bringing sanity to routing and organization of developers' applications.
On to what's new in 0.2.8!
- One big problem we started to run into is that ui-router is used with many versions of Angular. This means we need to be backwards-compatible even as Angular's API changes. Nate did great work to set up tests that now run against 1.0.8, 1.1.5, and 1.2.4. With this foundation in place it should be easy to test against newer versions as they are released. Thanks also to @dlukez for help with many broken tests.
- With the above implemented, we had tons of breaking tests. One large feature that comes from fixing these tests is support for the 1.2 animation syntax (as opposed to the previous syntax which is also still supported). I'll be updating the FAQ soon to have a working example of this new syntax.
- You can now specify a
target
attribute on youra[ui-sref]
links and it will be respected. Thanks to @roryf! - A much-requested feature: the
autoscroll
attribute. This adds anautoscroll="expr"
attribute touiView
, just likengInclude
has. It also replaces the$anchorScroll
call inuiView
with a custom
provider which scrolls the element attached touiView
into the current view instead. This should allow a more fine-tuning for designers by scrolling automatically to the activateuiView
without
manipulating anchors. Calling$uiViewScrollProvider.useAnchorScroll()
will restore the current
behavior or calling$anchorScroll
instead. Docs are forthcoming! Thanks to @ysbaddaden for the efforts on this. - Fixed param inheritance issue for siblings. Now, if two siblings share a parameter, that param will not be retained when traveling from one sibling to the other. Thanks, @mikekap.
- Lastly, thanks to @PascalPrecht for various improvements and optimizations to our build process. Two cool items he added that we've yet to really use (but plan on using soon) are changelog and ngdoc support. We hope to fully implement these items by 0.3.0 (but you can preview the pre-release docs here!).
Thanks,
Tim