Skip to content
This repository was archived by the owner on May 8, 2025. It is now read-only.
This repository was archived by the owner on May 8, 2025. It is now read-only.

Namespacing in command_names #34

Description

@lenaxus

At the moment it is only possible to run commands in the self-created "dev_cmds" directory.

When running a task with devmd it is only searching in the "dev_cmds"-directory, not in subdirectories. It could therefore be possible that with many self-created tasks it is difficult to structure the tasks.

This issue should adress this problem with the expansion of the namespace of the commands. The easiest way should be this suggestion:

  • It should be possible to save commands in subdirectories. With this approach every user can structure his commands and gets the overview.
  • When running a task with devcmd the script-name is no longer a single file-name. It is a path to the file starting in the "dev_cmds"-directory. This path can be build with slashes or colons. So for example it can look like this when I am trying to run the task foo in a subdirectory tutorial: 'yarn devcmd tutorial/foo'.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions