Adding "args" Before Command

[rience]

Hi,

I'm trying to write script to help managing Kubernetes pods. These pods have metadata like app or branch. An idea is that I'd have bash script that will take name of an app and then name of branch and then run passed command in pod. Something like this

./kube app-name branch-name ls

So I tried to do it this way

args:
  - name: app
  - name: branch

commands:
  - name: command

However, Bashly does not allow to use args at root level and commands in the same time. I can do it this way

./kube ls app-name branch-name

But for usability - it'd be great to have name of command at the end, since that's something that people would change very often. Thank you in advance for any ideas.

[DannyBen]

What other CLI that you know has this kind of syntax?

[DannyBen]

I have merged the fix to allow multiple global flags, and pushed a docker edge version.
If you wish to try the new version prior to a version bump, you can.

Otherwise, I will probably release towards the end of the week, unless it is urgent for you.

[rience]

Thank you. It works great :)

There is one more thing though - completion for global flags works globally for all flags. Sorry :(

[DannyBen]

There is one more thing though - completion for global flags works globally for all flags. Sorry :(

Hmm... I will need to check this. Not sure I can fix it.
And nothing to be sorry about, on the contrary - appreciate the report.

[DannyBen]

Okay @rience - it seems you have opened a can of worms... (thank you for that).

This discussion has helped in uncovering several bugs:

• Wildcards after the first word are not working completely#37
• Running completely test should also show a warning when the file is invalid completely#38
• Bad completions generated when global flags are in use #296

I am not 100% that fixing them will solve your issue, but right now completions for CLIs with global flags is completely broken.

I will need to fix these first, and then we can see where we stand.

[DannyBen]

So - I hope I got all the quirks out of the system.

The fixed bashly (together with completely 0.5.1) is on the master branch and the edge docker.

My test case that matches your scenario (as I understand) is this:

# bashly.yml
name: cli

flags:
- long: --app
  arg: app
  allowed: [app1, app2]
  required: true

- long: --branch
  arg: branch
  default: master

commands:
- name: ls

  flags:
  - long: --all
  - long: --compact

Then, you can run this shell script below to test the different completion cases:

#!/usr/bin/env bash
bashly add comp yaml completely.yaml --force

run() {
  echo "$ $@<tab>"
  completely test "$@"
  echo
}

run "cli "
run "cli --"
run "cli --app "
run "cli --app app1 ls --"

The output:

$ cli <tab>
ls

$ cli --<tab>
--app
--branch
--help
--version

$ cli --app <tab>
app1
app2

$ cli --app app1 ls --<tab>
--all
--compact
--help

You can also notice that the generated completely.yaml now contains a wildcard (*) wherever the completion is allowed to have other words.

# completely.yaml
---
cli:
- "--app"
- "--branch"
- "--help"
- "--version"
- "-h"
- "-v"
- ls
cli*--app:
- app1
- app2
cli*ls*:
- "--all"
- "--compact"
- "--help"
- "-h"