[BLOSSOM-291] Migrate magnolia-blossom-sample-module to UI 6 framework Created: 25/Mar/22 Updated: 18/Dec/23 |
|
| Status: | Accepted |
| Project: | Blossom |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Neutral |
| Reporter: | Canh Nguyen | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Task DoR: |
Empty
|
||||||||
| Date of First Response: | |||||||||
| Epic Link: | DevX Bucket | ||||||||
| Story Points: | 5 | ||||||||
| Team: | |||||||||
| Description |
|
The current magnolia-blossom-sample-module is based on UI 5 framework. We need to migrate the module to UI 6 framework and move the old code to compatibility module. EDIT: From the discussion below, we don't need to create a compatibility module. As there are already examples of working UI 6 definitions, migrating the rest of the sample should be trivial. |
| Comments |
| Comment by Roman Kovařík [ 25/Mar/22 ] |
|
Do we really need to have a compatibility module for a sample module? |
| Comment by Canh Nguyen [ 29/Mar/22 ] |
|
I think we don't need a compatibility module for this. People can find the old code on older versions. WDYT mgeljic ? |
| Comment by Mikaël Geljić [ 29/Mar/22 ] |
|
Totally agree, I think we mentioned compatibility briefly for blossom module itself (not samples), re: how to remove all compatibility code eventually (breaking change, might as well bump version to 4.0.0, according to SemVer, and then no need to bother with a compatibility module either). |
| Comment by Christopher Zimmermann [ 04/Apr/22 ] |
|
Can we close this ticket then? Or is there something to be done in the scope of thhis ticket? |
| Comment by Mikaël Geljić [ 06/Apr/22 ] |
|
canh.nguyen introduced a couple of 6 UI component samples (e.g. TextUi6Component), but all other page/component samples are still using old 5 UI defs. We should consider reducing the amount of page and component templates in this sample project too, to reduce effort. |