[CONTEDIT-251] Provide compatibility of old and new content editor in widgetset pro Created: 30/Jun/20 Updated: 28/May/21 Resolved: 08/Feb/21 |
|
| Status: | Closed |
| Project: | Content Editor |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 2.0 |
| Type: | Task | Priority: | Major |
| Reporter: | Dai Ha | Assignee: | Dai Ha |
| 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 DoR: |
Empty
|
||||||||||||||||
| Date of First Response: | |||||||||||||||||
| Epic Link: | Stories App Migration | ||||||||||||||||
| Sprint: | CM & OC 21 | ||||||||||||||||
| Story Points: | 8 | ||||||||||||||||
| Description |
|
Problem: widgetset-pro depends on the migrated content-editor-widget, this will lead to issue when legacy content-editor gets bundled in the the webapp instead of migrated one. Possible fix: rename the migrated content-editor-widgetset and include both the legacy and the migrated one into widgetset-pro. |
| Comments |
| Comment by Dai Ha [ 16/Jul/20 ] |
|
Wdyt slutz? To support backward compatibility? |