8 commits

Author	SHA1	Message	Date
Ed Page	37f47dd260	docs: Add completion changelogs	2022-01-12 11:04:57 -06:00
Ed Page	d9906eb150	chore: Release	2022-01-04 09:49:41 -06:00
Daniel Eades	7f71d642cd	style: prefer 'char' to 'str' for single character patterns	2022-01-04 09:20:08 -06:00
Ed Page	c01ebbac17	chore: Release	2021-12-31 14:35:02 -06:00
Ed Page	bc951e4e53	chore: Release	2021-12-31 13:37:28 -06:00
Ed Page	19b59a2df8	fix(complete): Better organize the API	2021-12-31 13:25:09 -06:00
Ed Page	8d73a0e80f	chore: Release	2021-12-31 12:23:47 -06:00
Ed Page	88a335ff97	fix(complete): Give crates more specific names ... `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`.	2021-12-31 12:03:29 -06:00