commands keys are ordered; might an object be more meaningful?

[jpluscplusm]

Both the Exec and Parent commands keys are an array. This implies there's some meaning to the ordering, which I don't believe is used. I.e. there's no "this command runs X, then Y, then Z" at present.

I can sort of see the forward-looking logic in having Parent's commands being ordered, as there might be a flag introduced for "this parent command is runnable and it invokes its child commands, in order, and isn't just a container for individually addressable sub-commands". But it feels like the combinatorial complexity of "this parent is both runnable, and this+this+this child is runnable, but this specific child isn't individually runnable .." might suggest that an adding a dedicated, ordered, "compound" command, later, would be the better DevX.

Might it be more meaningful to recast commands as an object, given that order's not currently A Thing?

[ripienaar]

In the demo we in the readme we see:

usage: mycorp [<flags>] <command> [<args> ...]

A hello world sample Choria App

Contact: R.I.Pienaar <[email protected]>

Flags:
  --help  Show context-sensitive help (also try --help-long and --help-man).

Commands:
  help [<command>...]
    Show help.

  demo hello
    Displays the word 'hello'

  demo world
    Displays the word 'world'

Here demo is a command with [hello, world] as sub commands. The ordering there matters you want to put things together or order them logically or so.

[ripienaar]

It's purely cosmetic/organisational though