Skip to content

Known breaking changes from 0.2.x/0.3.x to 1.0 #2219

Closed
@christopherthielen

Description

@christopherthielen

This list is not current. Please see the migration guide

Breaking changes from 0.2.x/0.3.x to 1.0

  • The $stateChange* events are deprecated. The $transitions.on* hooks are generally much more powerful. The events are not included by default, but can be re-enabled by including the stateEvents.js file and depending on the angular module ui.router.state.events (the stateEvents.js was missing in 1.0.0-alpha.1 builds; see 1.0.0-alpha.1: $stateChangeStart and $stateChangeSuccess status #2655)
  • Errors thrown during transitions are printed to the console by default. See $transitions.defaultErrorHandler() to customize
  • A template is required for all views (we are probably going to revert this one)
  • Resolves default to "LAZY" policy (they are invoked when a state is entered, not at the beginning of the transition)
  • onEnter/onExit hooks return value is used to modify and/or cancel the transition
  • Path parameters are no longer optional by default.
  • URL matching is now ordered by most specific to least specific
  • Dropping support for IE8 and angular 1.0.x-1.1.x
  • this no longer binds to the target state in resolves (this backward compatibility of resolve function #2548)
  • We no longer export the angular module name ui.router as CommonJS default export. CommonJS users should either require('angular-ui-router').default, or use ES6 import (1.0.0alpha0 doesn't return module name #2506)
  • Change to "/" handling?
    • virtuwell app doesn't route with .when("", "/")

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions