Skip to content
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

fix(complete): Give crates more specific names #3235

Merged
merged 1 commit into from Dec 31, 2021
Merged

Conversation

epage
Copy link
Member

@epage epage commented Dec 31, 2021

clap_generate originally intended to be "generate anything". With
fig, we already broke one part out. With #3174's man support, we are
also looking at keeping it separate:

  • More freedom to iterate on the API
  • Uniqueness (and potential weight) of its dependencies
  • man generation is normally more for distribution while completions are
    a mix of being distributed with the app or the app generating the
    completions (which will be exacerbated if we move most completion
    parsing logic to be in Rust)

So clap_generate is having a lot more limited of a role than the
original name conveys. I worry the generic name will be a hindrance to
people discovering and using it (yes, documentation can help but there
are limits).

I hesitated because we are on the verge of releasing 3.0. However, doing
it even later will be even more disruptive because more people will be
using it (crates.io lists ~70 people using clap_generate).

To ease things, we are still releasing clap_generate as a wrapper
around clap_complete.

`clap_generate` originally intended to be "generate anything".  With
`fig`, we already broke one part out.  With clap-rs#3174's man support, we are
also looking at keeping it separate:
- More freedom to iterate on the API
- Uniqueness (and potential weight) of its dependencies
- man generation is normally more for distribution while completions are
  a mix of being distributed with the app or the app generating the
  completions (which will be exacerbated if we move most completion
  parsing logic to be in Rust)

So `clap_generate` is having a lot more limited of a role than the
original name conveys.   I worry the generic name will be a hindrance to
people discovering and using it (yes, documentation can help but there
are limits).

I hesitated because we are on the verge of releasing 3.0. However, doing
it even later will be even more disruptive because more people will be
using it (crates.io lists ~70 people using `clap_generate`).

To ease things, we are still releasing `clap_generate` as a wrapper
around `clap_complete`.
@epage epage merged commit 24a2f3a into clap-rs:master Dec 31, 2021
@epage epage deleted the complete branch December 31, 2021 18:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant