[NPMCLI-236] Update to M6 definitions and also support M5 definitions Created: 09/Apr/20  Updated: 23/Mar/21  Resolved: 22/Mar/21

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

Type: Story Priority: Major
Reporter: Martin Drápela Assignee: Robert Šiška
Resolution: Fixed Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
dependency
is depended upon by NPMCLI-250 Check the final changes for content e... Selected
is depended upon by NPMCLI-248 Restore block template with multifield Closed
is depended upon by NPMCLI-254 DOC: CLI gets version 4.0.0 Closed
supersession
supersedes NPMCLI-241 Fix CLI to not create invalid definit... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[X]* Doc/release notes changes? Comment present?
[X]* Downstream builds green?
[X]* Solution information and context easily available?
[X]* Tests
[X]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:
Epic Link: Content Types phase 2
Sprint: HL & LD 24
Story Points: 5

 Description   

As a developer I want the CLI to create working starting definitions for M6 and M5 projects, so that the CLI helps me rather then possibly confusing me.

Acceptance critiera

  • 'create' commands create definitions using the corect definition style for the project, not old ones. At least:
    • should use '$type' instead of 'class'
    • dialogs should not supply actions.
    • An example of a form layout should be included.
  • One installation of magnolia CLI will work for multiple projects. There is a way that the CLI knows which styule of definition to create for the project that I am currently working on.
  • In one project I want to create m5 definitions for some types (like "blocks" ) and m6 for some thypes (like "components")

Use cases

  • I am working on a 5.7 project. I want the CLI to use the prototypes for 5.7
  • I am working on a 6.2 project I wasnt the CLI to use the prototypes for 6.2
  • I have 2 projects on going, one of them is 5.7, one is 6.2, I want to use different prototypes depending on my project.
  • I am working on a 6.2 project, but we are still using 5.7 version of Pages app.
  • I am working on a 6.2 project, but we are still using 5.7 version of Stories app.

 

 

Please see discussion and other proposals here:
https://wiki.magnolia-cms.com/display/PMTEAM/How+should+CLI+handle+multiple+versions

Have a look at this closely related PR:

https://git.magnolia-cms.com/projects/BUILD/repos/npm-cli/pull-requests/131/

 

 

 



 Comments   
Comment by Christopher Zimmermann [ 09/Apr/20 ]

Not sure if this exactly the approach to take, but for sure we need to come up with something for this

Move
https://git.magnolia-cms.com/projects/BUILD/repos/npm-cli/browse/lib/config/mgnl-cli-prototypes
to
.../npm-cli/browse/lib/config/mgnl-cli-prototypes-m5

Comment by Christopher Zimmermann [ 02/Jul/20 ]

Some options: https://wiki.magnolia-cms.com/display/PMTEAM/How+should+CLI+handle+multiple+versions

Comment by Christopher Zimmermann [ 30/Jul/20 ]

Updated description and proposal of ticket based on the analysis of the situation on that linked page.

Comment by Christopher Zimmermann [ 26/Jan/21 ]

Need to allow that users could be running 6.2, but choosing to work with the m5 pages app or the m5 stories app.

So if we do any "autodetecting", then we should also include a manual override - ideally in the configuration of the CLI

Comment by Christopher Zimmermann [ 26/Jan/21 ]

And consider that new stories app comes in first at 6.2.7 or so.

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