[BLOSSOM-51] Allow registering dialog descriptions directly and enable subclassing of DialogDescriptionBuilder Created: 21/Nov/11 Updated: 06/Dec/14 Resolved: 22/Nov/11 |
|
| Status: | Closed |
| Project: | Blossom |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.2.3 |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Tobias Mattsson | Assignee: | Tobias Mattsson |
| Resolution: | Fixed | 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)
|
||||||||
| Date of First Response: | |||||||||
| Description |
|
To make it possible to register dialog descriptions directly BlossomDialogRegistry needs to have a method that takes only the description, currently it takes the dialog factory and builds the description. BlossomDialogDescription should also have a property for the class of dialog to use and BlossomDialogRegistry should use that when saving to the repository. |
| Comments |
| Comment by Jan Haderka [ 06/Dec/14 ] |
|
Bulk close of old resolved issues. |