Skip to content

Update and refactor naming convention and patterns for package scripts #287

@bazottie

Description

@bazottie

The naming convention of grouped tasks ie. sequence:task and running the group with sequence which translates to sequence:* is losing its consistency IMHO. May I suggest to rethink convention for other patterns by either creating a more robust CLI tool to be able to add flags, child commands etc. or create a set of alternative naming conventions for other patterns. With an eye on future development, I think making opinionated choices ie. on when groups are to and are not to be made and what patterns the scripts follow can keep the structure clear and allows introduction of CLI tooling down the line.
ATTOW there are groups without a root command, nested groups, non-parallel or non-sequential groups etc.

Am willing to make a proposal when I can.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions