[NPMCLI-36] Improve descriptions for create-component and add-availability Created: 20/Jul/16  Updated: 22/Aug/16  Resolved: 15/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: Christopher Zimmermann Assignee: Unassigned
Resolution: Obsolete Votes: 0
Labels: quickwin
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to NPMCLI-40 Get rid of module specifier for the 2... 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:

 Description   

Some of the "create-component" self documentation is not clear.
Also the abiltiy to specify

[moduleName:]

should be removed as it makes referencing pages more complicated. (The addAvailability command should be updated in this way.)

Fix to:
Creates a component and optionally makes it available (or autogenerated) in a given area of a page. E.g. mgnl create-component foo -a myPage@main -p /path/to/module

-a, --available <[relPath/]page@area> Make available on page in area
-g, --autogenerate <[relPath/]page@area> Autogenerate on page in area



 Comments   
Comment by Christoph Meier [ 15/Aug/16 ]

This one is already tackled by NPMCLI-12

Comment by Christoph Meier [ 15/Aug/16 ]

Obsolete due to NPMCLI-12

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