[MGNLCT-347] Norsu-based contenttype uses '$type: nameField' Created: 10/Jan/23  Updated: 14/Feb/23  Resolved: 01/Feb/23

Status: Closed
Project: Content Types
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Story Priority: Neutral
Reporter: Christopher Zimmermann Assignee: Oanh Thai Hoang
Resolution: Done Votes: 0
Labels: None
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: 0.5d Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Attachments: PNG File don't override label name.png     Zip Archive norsu-slug-test.zip     PNG File override lable name.png    
Issue Links:
causality
dependency
documentation
to be documented by MGNLCT-348 DOC: nameField Closed
supersession
supersedes MGNLCT-310 'name' property on Submodel is not st... Closed
supersedes MGNLCT-311 'name' property on Model is not retur... Closed
Sub-Tasks:
Key
Summary
Type
Status
Assignee
MGNLCT-366 Implement Sub-task Closed Oanh Thai Hoang  
MGNLCT-367 Review Sub-task Completed Dai Ha  
MGNLCT-368 piQA Sub-task Closed Dai Ha  
MGNLCT-369 QA Sub-task Completed Canh Nguyen  
Template:
Acceptance criteria:
Empty
Task DoD:
[X]* Doc/release notes changes? Comment present?
[X]* Downstream builds green?
[X]* Solution information and context easily available?
[X]* Tests
[X]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Documentation update required:
Yes
Date of First Response:
Epic Link: SaaS TPR - ContentTypes
Sprint: DevX 29
Story Points: 5
Team: DeveloperX
Work Started:

 Description   

Contenttypes on Norsu include the new '$type: nameField' in the forms that they create. 

nameField is the new field developed in order to give an author the ability to enter a 'Name' and have a 'Slug' autocreated for them.

nameField is introduced in: https://jira.magnolia-cms.com/browse/NORSU-912

The contentType implementation of nameField should be as described here:
https://wiki.magnolia-cms.com/display/PMTEAM/Names+on+Norsu+-+Decision+-+2023-01-10

 

Acceptance Criteria:

  • In a content type - a nameField  will be automatically added to the top of the generated form.
  • If a developer supplies a property called "name", then it is replaced/merged with a nameField . At the least, if there is a "label" property supplied, then this "label" property should be used on the generated nameField.
  • When the content item is saved,
    • then the "slug" field should be used for the node name.
    • the "name" field should be saved as a content property.

Update AC: 

  • a nameField is intended only generated form for root node only. In case Submodel, developer supplies a property "name", then textField is generated.
  • subModels:
        - name: Guide
          properties:
            - name: name
              label: Name 

Update AC: from 17 Jan 2023: There are possible e2e test can be affected. See https://jira.magnolia-cms.com/browse/CLOUD-3286

Note:

It is anticipated that this resolves the other two related tickets. Maybe we can already close them as obsolete.

https://jira.magnolia-cms.com/browse/MGNLCT-310

https://jira.magnolia-cms.com/browse/MGNLCT-311

 



 Comments   
Comment by Christopher Zimmermann [ 16/Jan/23 ]

Flag added

Waiting for related ticket from Nucleus team.

Comment by Oanh Thai Hoang [ 17/Jan/23 ]

Here is sample light dev for testing with proposed PR norsu-slug-test.zip

Generated at Mon Feb 12 00:39:27 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.