[DOCU-2019] type must now be a fully qualified class name Created: 09/Jun/20 Updated: 16/Jun/20 Resolved: 16/Jun/20 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | 6.1, 6.2 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | High |
| Reporter: | Marty Glaubitz | Assignee: | Ashraf Khamis |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
||||||||
| Date of First Response: | |||||||||
| Sprint: | Docu Sprint 79 | ||||||||
| Story Points: | 1 | ||||||||
| Description |
|
The documentation should mention, that now one has to specify the fully qualified class name when overriding types. For example Whereas previously one could just write type: Long, now one must now write: type: java.lang.Long This took me half an hour to figure out, as you only get a generic bean exception... |
| Comments |
| Comment by Marty Glaubitz [ 09/Jun/20 ] |
|
I am referring to the confluence page: https://documentation.magnolia-cms.com/display/DOCS62/Field+definition |
| Comment by Julie Legendre [ 12/Jun/20 ] |
|
Hi, Thanks for reporting this martyglaubitz. We'll add it to the docs. Regards, Julie |
| Comment by Ashraf Khamis [ 16/Jun/20 ] |
|
Added the following description to the type property at https://documentation.magnolia-cms.com/display/DOCS62/Field+definition and https://documentation.magnolia-cms.com/display/DOCS62/Column+definition:
Adam reviewed the issue and created an improvement ticket (https://jira.magnolia-cms.com/browse/MGNLUI-5966) to allow the use of basic type names in Magnolia 6 UI. Since this affects Magnolia 6.2 & 6.1, backported all changes to DOCS61. |