Skip to content
This repository has been archived by the owner on Aug 3, 2023. It is now read-only.

Fix panic when kv: command does not have subcommand #579

Merged
merged 3 commits into from
Sep 12, 2019

Conversation

gabbifish
Copy link
Contributor

@gabbifish gabbifish commented Sep 12, 2019

This PR closes #572.

I have to provide alternative help messages for kv:key and kv:bulk because we don't want folks to specify --binding or --namespace-id anywhere but the last subcommand in the sequence; this is because Clap doesn't allow us to place .global() on ArgGroups yet, so we can't enforce logic requiring one of --binding or --namespace-id in kv: subcommands; instead, we can only place them in the final subcommand :(

Let me know if this doesn't make sense.

…e help messages because we need to ensure those are passed into the final subcommand and not earlier in the chain
@gabbifish gabbifish changed the base branch from master to feat-kv-commands September 12, 2019 21:22
… in these help messages because we need to ensure those are passed into the final subcommand and not earlier in the chain"

This reverts commit d4bca99.
@gabbifish gabbifish merged commit 81ac1e6 into feat-kv-commands Sep 12, 2019
@delete-merged-branch delete-merged-branch bot deleted the gabbi/fix-panic-kv-command branch September 12, 2019 23:14
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants