Uploaded image for project: 'Magnolia CLI'
  1. Magnolia CLI
  2. NPMCLI-204

Don't run commands on incompatible versions of Magnolia

    XMLWordPrintable

Details

    • Improvement
    • Resolution: Unresolved
    • Neutral
    • None
    • None
    • None

    Description

      As a developer I want to be informed when I try to use a command that will not work on my version of Magnolia.

      Prevent the user from creating mistakes in their project by dissallowing commands and posting useful error messages when users try to use a command that creates a definition that is not supported on their Magnolia version.

      If the CLI cannot determine the current used version of Magnolia for the directory, then do not prevent the command or post the error.

       

      Commands and suggestions for messages:

      create-block (Magnolia 5.5.6)

      Blocks are only compatible with Magnolia 5.5.6, but this project is running on Magnolia 5.3.2 ([path to detected Magnolia instance]). Block has not been created.

      create-virtual-uri (Magnolia 5.5.6)

      Supplying a virtual-uri via YAML definitions is only supported in Magnolia 5.5.6 and newer, but this project is running on Magnolia 5.5.2 ([path to detected Magnolia instance]). Virtual-uri has not been created.

      create-app 

      (Note: feature only supported in 6.0 or with the CT module installed. Probably the check should just check for the CT module.)

      Creating a content-type based app is only supported in Magnolia 6.0 and newer or with the content-types module on 5.7.1 and newer, but this project is running on Magnolia 5.5.2 ([path to detected Magnolia instance]) and the content-types module is not detected. App has not been created. 

      create-content-type 

      (Note: feature only supported in 6.0 or with the CT module installed. Probably the check should just check for the CT module.)

      Content types are only supported in Magnolia 6.0 and newer or with the content-types module on 5.7.1 and newer, but this project is running on Magnolia 5.5.2 ([path to detected Magnolia instance]) and the content-types module is not detected. Content type has not been created. 

      Checklists

        Acceptance criteria

        Attachments

          Issue Links

            Activity

              People

                Unassigned Unassigned
                czimmermann Christopher Zimmermann
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                  Created:
                  Updated:

                  Checklists

                    Task DoD