[DOCU-2057] Add column type JcrTypeColumnDefinition Created: 05/Oct/20 Updated: 05/Oct/20 Resolved: 05/Oct/20 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | 6.2.3 |
| Fix Version/s: | None |
| Type: | Task | Priority: | Neutral |
| Reporter: | Jonathan Ayala | Assignee: | Ashraf Khamis |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | 5m | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoR: |
Empty
|
| Date of First Response: | |
| Epic Link: | 2020 mgnl-staff requests |
| Sprint: | Docu Sprint 79 |
| Story Points: | 0.5 |
| Description |
|
Since Magnolia 6.2.3, JcrTypeColumnDefinition is available. It should be included in the column types list, specifying that it is available from 6.2.3. $type: jcrTypeColumn |
| Comments |
| Comment by Roman Kovařík [ 05/Oct/20 ] |
|
This column is not part of the framework but part of jcr-browser module thus not available if it's not part of your webapp. Either should be internal and don't have an alias... ...or if there is a use case in a common app, should be moved to the framework. |
| Comment by Ashraf Khamis [ 05/Oct/20 ] |
|
As mentioned above, this $type alias should not be documented since it is not part of the default UI framework. It could be removed altogether if it was not meant to be used in a common app. Closing the ticket as Won't Do. |