Skip to content
This repository was archived by the owner on Feb 24, 2020. It is now read-only.

Conversation

@euank
Copy link
Member

@euank euank commented Jul 27, 2016

The error messages are user visible and a bit confusing

@jonboulle
Copy link
Contributor

this is awkward.... but is this change in the right direction, or does --caps-retain make more sense?

@euank
Copy link
Member Author

euank commented Jul 27, 2016

I personally prefer caps-* because it takes a list of options.

I s'pose the other option is to convert everything to --caps and retain a hiddne --cap for backwards compatibility? I'd be happy to make that change if you and the original author (cc @alban) think that's better as well.

@jonboulle
Copy link
Contributor

+1

On 27 July 2016 at 10:55, Euan Kemp [email protected] wrote:

I personally prefer caps-* because it takes a list of options.

I s'pose the other option is to convert everything to --caps and retain a
hiddne --cap for backwards compatibility?


You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#2994 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/ACewN8XYQQsBzlnIUp06r-43-55lpPnMks5qZ5uggaJpZM4JWaF6
.

@iaguis
Copy link
Member

iaguis commented Jul 28, 2016

sgtm

@alban
Copy link
Member

alban commented Jul 28, 2016

I am fine either way. If we add --caps and hide --cap, the bash completion should only show one of them, right?

@jonboulle
Copy link
Contributor

Don't think that matters too much

On 28 July 2016 at 04:14, Alban Crequy [email protected] wrote:

I am fine either way. If we add --caps and hide --cap, the bash
completion should only show one of them, right?


You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#2994 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/ACewN209MrgPypMRiEMDPidPN_HNib-aks5qaI8TgaJpZM4JWaF6
.

@alban alban added this to the v1.12.0 milestone Aug 1, 2016
@alban
Copy link
Member

alban commented Aug 1, 2016

There was a discussion on naming the --cap-remove and --cap-retain flags: #2771 (comment)

@lucab do you agree on the suggestion to rename to --caps-remove and --caps-retain?

@lucab
Copy link
Member

lucab commented Aug 2, 2016

The renaming suggestion sounds good to me.

euank added a commit to euank/rkt that referenced this pull request Aug 2, 2016
euank added a commit to euank/rkt that referenced this pull request Aug 2, 2016
@euank
Copy link
Member Author

euank commented Aug 2, 2016

Experimentally, bash completion shows both --cap-* and --caps-* when using hidden flags. Similarly it shows the other hidden flags (e.g. --cpuprofile). Since it makes sense for hidden flags to, by default, not tab-complete either, I'll file an issue against upstream for that. I don't think we should let it block this since it doesn't seem like a big deal though.

Moving back to ready for review.

euank added a commit to euank/rkt that referenced this pull request Aug 2, 2016
@euank euank changed the title cli: Update cap-retain typo in errors / comments cli: Rename cap-retain and cap-remove to caps-* Aug 2, 2016
@lucab
Copy link
Member

lucab commented Aug 3, 2016

Changes LGTM, however this PR now has some conflicts which need a rebase.

@lucab lucab self-assigned this Aug 3, 2016
@euank
Copy link
Member Author

euank commented Aug 3, 2016

rebased, and next time we update cobra the deprecated flags will be hidden too (spf13/cobra#313)

@lucab
Copy link
Member

lucab commented Aug 3, 2016

LGTM

@lucab lucab merged commit 219e0c4 into rkt:master Aug 3, 2016
@euank euank deleted the caps-cap-ca-c branch August 3, 2016 18:27
antoni pushed a commit to intelsdi-x/rkt that referenced this pull request Sep 9, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants