List file creates problem with two main config files in same directory #18

New Issue

CyberShell · 2025-04-21T02:32:56Z

CyberShell commented

2025-04-21 02:32:56 +00:00

As I use my command app more, I start to notice some flaws. For instance, the lists.yml (or lists.yaml) file being in the same directory as the main file creates an issue.

This brings up questions. If two main config files with different names are in the same directory as a lists.yml file, should there be a way to ignore the lists.yml file when running a main file? Should it be a CLI flag or in the main file itself?

As it stands now, if run with the non-relevant main file, the program will error because the main file does not have cmdLists.[name].order references, which are in the lists.yml file. That is, the program can't find any commands.[name] referenced by the cmdLists.[name].order array.

As I use my command app more, I start to notice some flaws. For instance, the lists.yml (or lists.yaml) file being in the same directory as the main file creates an issue. This brings up questions. If two main config files with different names are in the same directory as a lists.yml file, should there be a way to ignore the lists.yml file when running a main file? Should it be a CLI flag or in the main file itself? As it stands now, if run with the non-relevant main file, the program will error because the main file does not have `cmdLists.[name].order` references, which are in the lists.yml file. That is, the program can't find any `commands.[name]` referenced by the `cmdLists.[name].order` array.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: CyberShell/backy#18