urlForEvent and action now take multiple contexts
corrected path in statemanager
Merge getPath with get and setPath with set - Fixes #1161
Remove odd construct in normalizeTuples
Replaced getPath/setPath with get/set
Also rename trySetPath to trySet
Merge pull request #1176 from wagenet/get-getpath-merge

Merge getPath/setPath with get/set
Added PromiseChain for resolving a chain of promises
Delay routing while contexts are loading
Assert that transitionTo at least matched a state
Merge pull request #1183 from wagenet/delayed-routing

Delay Routing to Wait for Loading
Grammar; indentation
Merge pull request #1200 from joliss/doc

Grammar; indentation
Allow ember-debug to set values for Ember.ENV - Fixes #1185
Add connectControllers convenience
Change {{action}} API for more explicit contexts

Previously, the action helper automatically sent
the current context as the context to the event
it was triggering.

This meant that the router could receive
superfluous contexts that it would try to apply
to a parent state.

Instead of:

  {{action edit context="post"}}

Do:

  {{action edit post}}

If you were relying on the default context,
change:

  {{action edit}}

to:

  {{action edit this}}

This also paves the way for support for multiple
contexts.
Don't pass along superfluous context to events

This finishes up the previous commit.
update docs to reflect new context passing syntax of {{action}} helper and its more typical usage when combined with Router.
Fix failing {{action}} unit test
Merge pull request #1201 from trek/UpdateDocsForAction

update docs to reflect new context passing syntax of {{action}} helper a...