[MGNLUI-6134] Content-type apps definitions are registered under filename, ignoring name property Created: 17/Aug/20  Updated: 03/Mar/21  Resolved: 02/Mar/21

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

Type: Bug Priority: Neutral
Reporter: Robert Šiška Assignee: Canh Nguyen
Resolution: Cannot Reproduce Votes: 0
Labels: VN-Analysis
Remaining Estimate: 0d
Time Spent: 1.75d
Original Estimate: Not Specified

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)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:
Epic Link: Content Types phase 2
Sprint: HL & LD 23
Story Points: 2

 Description   

Given an app named books.yaml with following content:

!content-type:book
name: book-app

Although the app-launcher links to book-app, AppController fails to open the app, as the app is called books in AppDescriptorRegistry.



 Comments   
Comment by Christopher Zimmermann [ 24/Aug/20 ]

See "Customizing the app descriptor", here https://documentation.magnolia-cms.com/display/DOCS62/Part+I+-+Creating+a+basic+content+app

  • Line 2: You give the app the name bookshelf-app, under which the app is known to other resources and systems in Magnolia.
Comment by Christopher Zimmermann [ 24/Aug/20 ]

Is the problem only happening for content-type based apps - or all app definitions?

Comment by Christopher Zimmermann [ 24/Aug/20 ]

'name' property for an app documented here: https://documentation.magnolia-cms.com/display/DOCS62/App+descriptor

"optional
App name. If no value is specified, either the file name (without the suffix .yaml) or the JCR node name will be used."

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