[MGNLUI-3198] Scope of choose dialog makes it difficult to run multiple implementations of workbench at same time Created: 10/Oct/14 Updated: 09/Mar/21 Resolved: 09/Mar/21 |
|
| Status: | Closed |
| Project: | Magnolia UI |
| Component/s: | app framework, workbench |
| Affects Version/s: | 5.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Jan Haderka | Assignee: | Unassigned |
| Resolution: | Obsolete | Votes: | 0 |
| Labels: | None | ||
| 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)
|
||||||||
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
||||||||
| Description |
|
Currently there is only one choose dialog scope so when you implement different workbench and connector you can't really have all different implementations working easily alongside and have them being used from choose dialog. The provider there needs to know about all workbench implementations and they all need to have common ancestor to make it work. this is inflexible and leads to issues where the last one setting the choosedialog scope needs to know about all other impls out there and have dependency on them in order to write provider that is able to work with all those different implementations. See |