-
Notifications
You must be signed in to change notification settings - Fork 391
refactor: more API naming work #990
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I suppose these functions are renamed to _comp_compgen_NAME
like _comp_compgen_filedir
as discussed in
- Use _comp_split and _comp_compgen in completions/* #948 (comment)
- Customizability and naming conventions for each completion #539 (comment) (the third item in the list)
Also, small implementation adjustments might be needed so that they can be called with _comp_compgen [options] NAME ...
. I submitted PR #993 (which I was originally planning to submit later) because it contains some hints on _comp_compgen_NAME
.
Per current naming convention.
Removal of these is a breaking change, but the replacements are not public, and we don't want possible users to move to using the private ones.
Per current naming convention.
Per current naming convention.
Per current naming convention.
Per current naming convention.
aa4d4bb
to
cac2724
Compare
12c2eee
to
213dabe
Compare
213dabe
to
f475b2e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, approved (but I'm not allowed to mark a PR I started as approved), please feel free to merge if you're happy with it 👍
Thanks! |
No description provided.