-
Notifications
You must be signed in to change notification settings - Fork 102
Closed
Labels
ComplexPriority: P3May be fixed according to the position in the backlogMay be fixed according to the position in the backlogSeverity: S3Affects non-critical data or functionality and does not force users to employ a workaroundAffects non-critical data or functionality and does not force users to employ a workaroundactioncode generation
Milestone
Description
Extend the new Magento 2 module generation with the ability to set module sequence(s).
Module sequence(s) expected view
- Right-click on the directory
- Click
New
- Select
Magento 2 module
menu item and click on it - In the opened popup, a new
Magento 2 module
form opened - Add to the form a new section under the "Module dependencies"
- The label should be named
Module sequence(s)
and related to the list of Magento project modules. Looks similar to the "Module dependencies".
Module sequence(s) expected behaviour
- At the list of modules, the first item should be "None" and autoselected on form load.
- A developer must be able to select one or several modules in the list.
- Selected modules must be added to the module.xml node of the newly created module.
- If the "None" selected the node should not be added.
Magento dev doc for module dependencies
DmitryFurs
Metadata
Metadata
Assignees
Labels
ComplexPriority: P3May be fixed according to the position in the backlogMay be fixed according to the position in the backlogSeverity: S3Affects non-critical data or functionality and does not force users to employ a workaroundAffects non-critical data or functionality and does not force users to employ a workaroundactioncode generation