[MGNLUI-6338] JcrDatasourceDefinition#nodeNameProperty should default to null Created: 21/Oct/20  Updated: 28/Oct/20  Resolved: 24/Oct/20

Status: Closed
Project: Magnolia UI
Component/s: None
Affects Version/s: 6.2.4
Fix Version/s: 6.2.4

Type: Improvement Priority: Neutral
Reporter: Šimon Demočko Assignee: Roman Kovařík
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Cloners
is cloned by MGNLPN-508 Set nodeNameProperty of datasources Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Documentation update required:
Yes
Date of First Response:
Epic Link: nodeName
Sprint: UI FW 13

 Description   

Steps to reproduce

Rename a page using rename item (not editing via detail). You can use special characters.

Expected results

Node is renamed, no jcrName property.

Actual results

JcrName property is created.

Workaround

You can still rename the item, just the content of the field might be confusing.

Development notes

Presense of property <field name> now always takes precedence when loading property but should respect if nodeNameProperty of JcrDatasource is null (= use just real node name) instead.

As the default for nodeNameProperty is jcrName and you can't set it to null via config without getting warning in def. app, should we use null as default?



 Comments   
Comment by Ashraf Khamis [ 28/Oct/20 ]

Deleted the default value for nodeNameProperty from https://documentation.magnolia-cms.com/display/DOCS62/JCR+data+source.

Generated at Mon Feb 12 09:35:28 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.