[NPMCLI-20] Update mgnl-cli.json "lightDevFoldersInModule" to create common folders for light development Created: 08/Jul/16  Updated: 22/Aug/16  Resolved: 03/Aug/16

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

Type: Improvement Priority: Neutral
Reporter: Tomáš Gregovský Assignee: Federico Grilli
Resolution: Fixed Votes: 1
Labels: quickwin
Remaining Estimate: 0d
Time Spent: 1.5h
Original Estimate: Not Specified

Issue Links:
relation
is related to NPMCLI-26 Define prototype for light module in ... 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)
Date of First Response:
Sprint: Basel 55
Story Points: 1

 Description   

Add these directories:

decorations
i18n



 Comments   
Comment by Christopher Zimmermann [ 14/Jul/16 ]

I think for now we should only add things which will be commonly used for light development:
decorations
i18n

Comment by Christopher Zimmermann [ 14/Jul/16 ]

Please see linked ticket npmcli-26 for alternative way to define the prototype light module.

Comment by Tomáš Gregovský [ 15/Jul/16 ]

czimmermann I just read somewhere that fieldTypes are also allowed in LM, if not then ignore ti. And yes, idea is to pre-generate all folders which are "hardcoded" in Magnolia. Thanks!

Generated at Mon Feb 12 04:45:45 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.