[NPMCLI-218] Create-app, create-content-type with a specific workspace Created: 16/May/19  Updated: 25/Mar/22

Status: Accepted
Project: Magnolia CLI
Component/s: None
Affects Version/s: 3.0.7
Fix Version/s: None

Type: Improvement Priority: Neutral
Reporter: Martin Drápela Assignee: Unassigned
Resolution: Unresolved Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Problem/Incident
is caused by NPMCLI-210 DOC: A tutorial showcasing creation o... Closed
dependency
depends upon NPMCLI-149 create-app and create-content-type co... 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)
Epic Link: Content Types phase 2
Story Points: 3

 Description   

Currently, create-app and create-content-type commands also create a same-name workspace:

mgnl create-content-type a

mgnl create-app a

/light-modules/foo/contentTypes/a.yaml

 

# Automatically generated contentType demonstrates usage of the common properties.
# Modify them to match your requirements.
datasource:
    workspace: a

<...>

Improvement

For both commands, allow the user to set the name of the workspace, e.g. with a switch `-w`.

This will give the user more flexibility by linking up the newly created app/CT to an already existing workspace: e.g.

`mgnl create-app bookshelf-app-enterprise -w books`

Note

If the workspace already exists, the contenttypes system will work with it seamlessly.

 


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