Error when splitting configuration in sub/nested commands about bashly

[DannyBen]

Cool. I have added bashly validate --verbose which will show the "compiled" config. Next release.

[DannyBen]

I can't reproduce this.
Followed your instructions, and the actual behavior matches the expected.

# src/bashly.yml
name: cli

commands:
- name: toplevel
  help: "The toplevel command namespace"
  commands:
  - import: src/toplevel_nested_command.sh

# src/toplevel_nested_command.sh
name: nested
help: "The nested command"
---
inspect_args

Output

➜ ./cli
cli

Usage:
  cli COMMAND
  cli [COMMAND] --help | -h
  cli --version | -v

Commands:
  toplevel   The toplevel command namespace


➜ ./cli toplevel
cli toplevel - The toplevel command namespace

Usage:
  cli toplevel COMMAND
  cli toplevel [COMMAND] --help | -h

Commands:
  nested   The nested command

And the second variant works as well (although I did not expect it to).

The import directive is just bringing that YAML snippet to the host file.
Assuming your file is more complex than the example (judging by root.commands[14].name must be a string) - I would guess the error is elsewhere. Possibly indentation issues?

[DannyBen]

Perhaps it would be helpful for such use cases if bashly validate had a flag that if set, would show the "complete" YAML file?

[weierophinney]

I wonder if it's a difference between 0.8.7 and 0.8.8; I'll try to reproduce with 0.8.8.

[weierophinney]

Closing; it turned out to be a configuration issue on my part (I'd included the command file earlier in my script as well).