[MAGNOLIA-5303] wrap Context in CommandsManager Created: 09/Sep/13 Updated: 03/Jun/16 Resolved: 10/Sep/13 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | 5.0.4 |
| Fix Version/s: | 5.1 |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Espen Jervidalo | Assignee: | Espen Jervidalo |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Epic Link: | Workflow for content apps |
| Sprint: | 5.1 Beta1- Backend |
| Description |
|
Currently we pass the Context returned by MgnlContext.getInstance() when executing a command. In the case of workflow you can't distinguish which parameters are relevant for the current command, and we either selectively filter the parameters before passing them to the workflow or we pass all contextual information. |