Mirrors/clap
2
0
Fork 0
mirror of https://github.com/clap-rs/clap synced 2024-12-15 15:22:30 +00:00
Code Issues Projects Releases Packages Wiki Activity
clap/clap_complete/Cargo.toml

63 lines
2.2 KiB
TOML
Raw Normal View History

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 17:59:15 +00:00
[package]
name = "clap_complete"
chore: Release
2024-09-17 21:12:36 +00:00
version = "4.5.28"
style: Normalize manifests
2022-05-18 15:33:37 +00:00
description = "Generate shell completion scripts for your clap::Command"
categories = ["command-line-interface"]
keywords = [
"clap",
"cli",
"completion",
"bash",
]
docs: Link to repo, not webpage inside repo
2024-06-04 20:36:17 +00:00
repository.workspace = true
chore: Switch to workspace inheritance
2023-01-09 18:35:54 +00:00
license.workspace = true
edition.workspace = true
rust-version.workspace = true
include.workspace = true
style: Normalize manifests
2022-05-18 15:33:37 +00:00
[package.metadata.docs.rs]
docs: Include more content on docs.rs
2023-12-27 17:30:42 +00:00
features = ["unstable-doc"]
rustdoc-args = ["--cfg", "docsrs", "--generate-link-to-definition"]
cargo-args = ["-Zunstable-options", "-Zrustdoc-scrape-examples"]
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 17:59:15 +00:00
[package.metadata.release]
pre-release-replacements = [
docs: Add completion changelogs
2022-01-12 17:04:57 +00:00
{file="CHANGELOG.md", search="Unreleased", replace="{{version}}", min=1},
{file="CHANGELOG.md", search="\\.\\.\\.HEAD", replace="...{{tag_name}}", exactly=1},
{file="CHANGELOG.md", search="ReleaseDate", replace="{{date}}", min=1},
{file="CHANGELOG.md", search="<!-- next-header -->", replace="<!-- next-header -->\n## [Unreleased] - ReleaseDate\n", exactly=1},
{file="CHANGELOG.md", search="<!-- next-url -->", replace="<!-- next-url -->\n[Unreleased]: https://github.com/clap-rs/clap/compare/{{tag_name}}...HEAD", exactly=1},
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 17:59:15 +00:00
{file="README.md", search="github.com/clap-rs/clap/blob/[^/]+/", replace="github.com/clap-rs/clap/blob/{{tag_name}}/", exactly=4, prerelease = true},
]
[lib]
bench = false
[dependencies]
chore(complete): Update require clap
2024-09-20 20:02:49 +00:00
clap = { path = "../", version = "4.5.18", default-features = false, features = ["std"] }
chore: Release
2024-02-08 16:33:13 +00:00
clap_lex = { path = "../clap_lex", version = "0.7.0", optional = true }
feat(complete): Minimal rust-completion Inspired by argcomplete, this provides Rust-implemented completions - Only bash for now - No subcommand support - No flag value support - No special settings support - No handling of positions within positionals - No prioritizing of required or removing of conflicts (including self-conflicts)
2022-04-15 21:08:11 +00:00
is_executable = { version = "1.0.1", optional = true }
chore: Bump shlex in clap_complete to 1.3.0
2024-08-27 07:14:23 +00:00
shlex = { version = "1.3.0", optional = true }
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 17:59:15 +00:00
[dev-dependencies]
chore: Upgrade snapbox
2024-05-24 15:13:50 +00:00
snapbox = { version = "0.6.0", features = ["diff", "dir", "examples"] }
test(complete): Option to verify examples
2022-04-27 13:54:39 +00:00
# Cutting out `filesystem` feature
chore(deps): update compatible (dev) (#5477) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
2024-05-01 01:04:57 +00:00
trycmd = { version = "0.15.1", default-features = false, features = ["color-auto", "diff", "examples"] }
chore: Update completest
2024-09-04 15:42:22 +00:00
completest = "0.4.2"
chore(complete): Update completest
2024-09-04 16:21:43 +00:00
completest-pty = "0.5.5"
chore(complete): Update require clap
2024-09-20 20:02:49 +00:00
clap = { path = "../", version = "4.5.18", default-features = false, features = ["std", "derive", "help"] }
chore: Update from template
2024-05-04 19:59:40 +00:00
automod = "1.0.14"
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 17:59:15 +00:00
feat(complete): Minimal rust-completion Inspired by argcomplete, this provides Rust-implemented completions - Only bash for now - No subcommand support - No flag value support - No special settings support - No handling of positions within positionals - No prioritizing of required or removing of conflicts (including self-conflicts)
2022-04-15 21:08:11 +00:00
[[example]]
name = "dynamic"
fix(complete)!: Remove CompleteCommand This just has too many caveats to be worth maintaining
2024-08-29 02:02:32 +00:00
required-features = ["unstable-dynamic"]
feat(complete): Minimal rust-completion Inspired by argcomplete, this provides Rust-implemented completions - Only bash for now - No subcommand support - No flag value support - No special settings support - No handling of positions within positionals - No prioritizing of required or removing of conflicts (including self-conflicts)
2022-04-15 21:08:11 +00:00
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 17:59:15 +00:00
[features]
default = []
fix(complete)!: Remove CompleteCommand This just has too many caveats to be worth maintaining
2024-08-29 02:02:32 +00:00
unstable-doc = ["unstable-dynamic"] # for docs.rs
fix(complete): Preserve absolute paths
2024-08-21 16:58:11 +00:00
unstable-dynamic = ["dep:clap_lex", "dep:shlex", "dep:is_executable", "clap/unstable-ext"]
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 17:59:15 +00:00
debug = ["clap/debug"]
chore: Update from template
2024-05-04 19:59:40 +00:00
[lints]
workspace = true
Reference in a new issue Copy permalink