Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Namespacing in command_names #34

Open
lenaxus opened this issue Aug 11, 2021 · 0 comments
Open

Namespacing in command_names #34

lenaxus opened this issue Aug 11, 2021 · 0 comments

Comments

@lenaxus
Copy link
Contributor

lenaxus commented Aug 11, 2021

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'.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant