[MGNLUI-2657] As a developer I do not have to adapt BrowserSubApp/BrowserPresenter in case my Workbench is JCR-agnostic. Created: 07/Feb/14 Updated: 20/Mar/14 Resolved: 13/Mar/14 |
|
| Status: | Closed |
| Project: | Magnolia UI |
| Component/s: | content app, framework |
| Affects Version/s: | 5.2 |
| Fix Version/s: | 5.3 |
| Type: | Story | Priority: | Major |
| Reporter: | Aleksandr Pchelintcev | Assignee: | Aleksandr Pchelintcev |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | next | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||||||
| 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: | JCR-agnostic content apps | ||||||||||||||||||||||||||||||||||||
| Sprint: | 5.3 Preparation 2, 5.3 Sprint 3, 5.3 Sprint 4 | ||||||||||||||||||||||||||||||||||||
| Description |
|
Item selection and other item operations including action availability checking should not depend on JCR API and JcrItemAdapters so that the developers of custom non-JCR related apps could use BrowserSubApp and BrowserPresenter out of the box. |