[MGNLUI-4919] Labels supplied in CT definition properties are shown in App Created: 10/Sep/18  Updated: 24/Dec/18  Resolved: 18/Dec/18

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

Type: Improvement Priority: Major
Reporter: Christopher Zimmermann Assignee: Hieu Nguyen Duc
Resolution: Fixed Votes: 1
Labels: None
Remaining Estimate: 3.5h
Time Spent: 2d 4.5h
Original Estimate: 3d

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: Content Types finalization
Sprint: Saigon 160
Story Points: 5

 Description   

If labels are supplied in the CT definition, they should then be used in the Detail editor of an app.

This is fundamental for people to be able to use the new Content Types feature simply, and without additional complex configuration for straightforward cases.

Acceptance criteria:

  • If a developer supplies a "label" on a property in a CT file, then this label is shown on the app.
  • If an i18n property key also exists - it overrides the value supplied with the label property.
  • If an i18n property key also exists - the label overrides the value supplied by the key.


 Comments   
Comment by Christopher Zimmermann [ 13/Sep/18 ]

Requires decision about how to implement. If we mix presentation and model.

Comment by Mikaël Geljić [ 01/Oct/18 ]

If an i18n property key also exists - it overrides the value supplied with the label property.

In every I18nized definition, it's the opposite: label overrides the i18n translation.

As a prerequisite, we should implement an I18nKeyGenerator on ContentTypeDefinition, and then figure out where/when to "i18nize" CT defs; since generated apps are somewhat "statically" stored into the registry... As for the first AC, I got from oanh.thai that this is working already, isn't it?

Comment by Christopher Zimmermann [ 01/Oct/18 ]

OK, sorry for the mixup. I CHANGE THE AC now to be in line with standard magnolia i18n behaviour.

Comment by Dai Ha [ 19/Dec/18 ]

Verified wth magnolia-community-demo-bundle-6.0.1-20181218.183328-65-tomcat-bundle

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