[DOCU-1527] Reference fields by name as well as by fully qualified classname Created: 30/May/18  Updated: 22/Jun/18  Resolved: 22/Jun/18

Status: Closed
Project: Documentation
Component/s: None
Affects Version/s: None
Fix Version/s: 5.7

Type: Story Priority: Neutral
Reporter: Christoph Meier Assignee: Martin Drápela
Resolution: Done Votes: 0
Labels: None
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Sub-Tasks:
Key
Summary
Type
Status
Assignee
DOCU-1528 New page "Reference fields by name" Sub-task Closed Martin Drápela  
DOCU-1529 Create an includable to be added to d... Sub-task Closed Martin Drápela  
DOCU-1530 Add the includable to pages which con... Sub-task Closed Christoph Meier  
Template:
Acceptance criteria:
Empty
Date of First Response:
Epic Link: 5.7 release
Sprint: Docu Sprint 52
Story Points: 5

 Description   

With Magnolia 5.7 - it will be possible to reference fields (in forms within dialogs, apps, etc.) by names.
The (now) "old style" to reference the field by its fully qualified class name of the definition class will still work.

For a related dev ticket e.g. see MGNLUI-3882, DEV-338

Docu tasks:

  • Announce it on the release notes
  • Create a new page which explains the concept (and that still both will be possible)
  • Search for doc pages dealing with this - and to start with link to that new page

See DEV-401 for the complete list of changed field names.


Video of the demo:
afp://file.magnolia-cms.com/All/Product Development/Knowledge Transfer/2018/20180528-field-alias_Ilguen.mp4



 Comments   
Comment by Christoph Meier [ 30/May/18 ]

The three subtasks are the basics - which I guess should be sufficient for the 5.7 release.

Step by step we can edit existing form definitions by using the new fieldType property.

If there is more to do - let's see.

Comment by Christoph Meier [ 21/Jun/18 ]

In the context of DOCU-1530 I have edited already a bunch of pages in order to use the new fieldType instead of class to define fields. (For a detailed list about the edited pages see this everrnote.)
When the code snippet can be edited directly on wiki it is "quick and easy" - however, there are cases where we include files from. Such cases I have not tackled - and these may need more love&care.

One special case was the https://documentation.magnolia-cms.com/display/DOCS57/Hello+Magnolia - where the code was directly editable, but where we also offer a zip file which comes from nexus. We may have to change the code for the Hello Magnolia on git and nexus too.

It still needs to be decided what follow-ups are required.

Comment by Christoph Meier [ 22/Jun/18 ]

Reviewed & discussed with Martin.
I close it

Generated at Mon Feb 12 01:18:55 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.