f9b3bc7b2b
The scope being handed to (and retained on) the action service was being used for two purposes: 1. handing data down to the underlying wizard steps, and 2. receiving data back from the underlying wizard steps. This patch provides a mechanism for passing data down through injection, and removes the need for event-based data return by explicitly passing the captured wizard data to the submit() resolution. It also adds the controller scope to the allowed() and perform() action service handlers to grant access to contextual information without needing to attach state to the service. Change-Id: Ieb293d0a849cd84d15e7aae0a68558fde80fd2c2 Fixes-Bug: 1640049
11 lines
437 B
YAML
11 lines
437 B
YAML
---
|
|
deprecations:
|
|
- The initScope method for action services has been
|
|
deprecated, with the new method initAction added
|
|
which does not get passed a scope. The allowed and
|
|
perform method are now passed a scope for context
|
|
in addition to the first item/items argument.
|
|
The "scope" parameter to the WizardModalService modal()
|
|
method has also been deprecated, and will be ignored
|
|
in a future release of Horizon.
|