[MGNLCT-348] DOC: nameField Created: 11/Jan/23  Updated: 13/Jun/23  Resolved: 13/Jun/23

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

Type: Task Priority: Neutral
Reporter: Martin Drápela 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

Attachments: PNG File Screenshot at 2023-01-13 12-26-03.png     PNG File image-2023-06-13-08-59-46-396.png    
Issue Links:
Relates
documentation
documents MGNLCT-347 Norsu-based contenttype uses '$type: ... Closed
Sub-Tasks:
Key
Summary
Type
Status
Assignee
MGNLCT-349 Implementation Sub-task Completed Martin Drápela  
MGNLCT-350 Review Sub-task Closed Oanh Thai Hoang  
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Epic Link: Content Types v2 - documentation phase 1
Sprint: DevX 39
Story Points: 1
Team: DeveloperX
Work Started:

 Description   

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

(MGNLCT-347)

 

we should update the document that name will be added automatically to content types (sub models not included). If users add name to content types will be ignored (because we always change its type to nameField).

 nameField should only use for root node only. For submodels we don't generate nameField  but textField instead.  In case Submodel, developer supplies a property "name", then textField is generated.

*

subModels:
    - name: Guide
      properties:
        - name: name
          label: Name 

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