angular-ui/ui-router

fix(urlRouter): add check using `$sniffer`

Fixes #2221

- Add additional check for situations where `pushState` is not properly supported

docs(sample): change from plural 'states' to singular 'state'

feat($stateChangeStart): Add options to event

- Add options as a 5th parameter to the $stateChangeStart event
- As per #1620

fix(UrlMatcherFactory): Correct trailing slash of terminal optional parameter

$stateParams reset between tests

A fresh object is created each time $stateParams is initialized, instead of reusing the same instance. This prevents leaking state between unit tests.

…arameter

Fixes #1902

Fixes #2091

fix(urlMatcherFactory): include the slash in squashed params

feat(uiState): add ui-state directive

 - Refactor StateRefDirective for better modularity
 - Drop key restrictions on ui-sref-opts
 - Improves performance over prior implementation with no extra $eval()’s

Fixes #395, #900, #1932

fix(ui-view): change $viewContentLoading to pair with $viewContentLoaded

Squashed params were ignoring a missing slash before the param so things
like /users123 would match /url/:id

Fixes #2064

feat(uiSrefActive): allow active & active-eq on same element

closes #1997

The old $viewContentLoaded event wasn't needed for the one internal
client (ui-view) because ui-view always ignores that event and acts on
a $stateChangeSuccess event that follows right behind anyway.

And it wasn't as useful to external clients as it could be because
it wasn't delivered on every view update -- it was delivered only
on state transitions that activate a state defining a view, and
didn't deal with inheritance.

Also, neither $viewContentLoading nor $viewContentLoaded events
contained the name of the view loading or loaded.

This change makes $viewContentLoading and $viewContentLoaded be
emitted always in pairs, before/after updateView does the work of
actually loading the view, and both events include the name of the
view being loaded.

This is a breaking change for users of the old $viewContentLoading
event that relied on it being broadcast from the root scope, the
precise time it was broadcast, the fact that it wasn't always sent
when a view is loaded even if $viewContentLoaded will be sent, or the
"options" parameter that was emitted with it. If people rely on any of
that behavior and we can't break it, then we can restore the old
behavior but I think there needs to be some other event which is
reliably paired with $viewContentLoaded and contains the view name,
and I can't think of a better name than $viewContentLoading for that
event.

Closes #685.

docs(repo): updated contributing label images

refactor(commonjs): Added support for commonjs

…rameters are considered optional

fix(urlRouter): When reloadOnSearch is false, also update the URL.
Fixes #1963
Fixes #1803
Fixes #1079

Fixes #1965

…tate.go()

- This partially reverts a change from 0.2.13 intended to stop infinite redirects.
  - b267ecd
  - #1573
- This will be likely be re-reverted in 1.0

Closes #1584

The handling of `reloadOnSearch: false` caused ui-router to avoid
reloading the state in more cases than it should. The designed and
documented behavior of this flag is to avoid state reload when the
URL search string changes. It was also avoiding state reload when
the URL path (or any non-search parameters to the state) changed,
and even when state reload was explicitly requested.

This change

- flips the name of shouldTriggerReload (and the accompanying guard
  boolean, skipTriggerReloadCheck) to match the direction of the
  logic: shouldSkipReload and allowSkipReloadCheck

- teaches shouldSkipReload to look at the types of the differing
  parameters, and only skip the reload if the only parameters that
  differ were search parameters

- pulls the test for options.reload to the front of the complex
  boolean expression.

- Updates $state.params and $stateParams when skipping reload

Fixes #1079. Helps with one of the cases broken in #582.