[MGNLUI-4581] Migrate more Vaadin fields to the improved UI framework Created: 28/May/18 Updated: 26/Jun/19 Resolved: 20/Jul/18 |
|
| Status: | Closed |
| Project: | Magnolia UI |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.0 |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Aleksandr Pchelintcev | Assignee: | Ilgun Ilgun |
| Resolution: | Done | Votes: | 0 |
| Labels: | databinding, resurface, vaadin8, vaadin8-databinding, vaadin8-fields | ||
| 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: | UI framework: forms, dialogs, content editing | ||||||||||||
| Sprint: | Basel 151 | ||||||||||||
| Story Points: | 8 | ||||||||||||
| Description |
|
While researching the form framework improvements, we didn't pay too much attention to the field-set that we port: text fields were pretty much enough to validate the approach. However, to bring the real value, we need more of those fields in:
Typically this would be about migrating the field factory to the new (quite similar) version and porting the field component to Vaadin 8 if needed. (TODO - create the sub-tasks if required!) |