chore(deps): bump clap from 3.1.18 to 4.0.32

[dependabot[bot]]

Bumps clap from 3.1.18 to 4.0.32.

Release notes

Sourced from clap's releases.

v4.0.32

[4.0.32] - 2022-12-22

Fixes

• (parser) When overriding required(true), consider args that conflict with its group

v4.0.31

[4.0.31] - 2022-12-22

Performance

• Speed up parsing when a lot of different flags are present (100 unique flags)

v4.0.30

[4.0.30] - 2022-12-21

Fixes

• (error) Improve error for args_conflicts_with_subcommand

v4.0.29

[4.0.29] - 2022-11-29

v4.0.28

[4.0.28] - 2022-11-29

Fixes

• Fix wasm support which was broken in 4.0.27

v4.0.26

[4.0.26] - 2022-11-16

Fixes

• (error) Fix typos in ContextKind::as_str

v4.0.25

[4.0.25] - 2022-11-15

Features

• (error) Report available subcommands when required subcommand is missing

v4.0.24

[4.0.24] - 2022-11-14

Fixes

... (truncated)

Changelog

Sourced from clap's changelog.

[4.0.32] - 2022-12-22

Fixes

• (parser) When overriding required(true), consider args that conflict with its group

[4.0.31] - 2022-12-22

Performance

• Speed up parsing when a lot of different flags are present (100 unique flags)

[4.0.30] - 2022-12-21

Fixes

• (error) Improve error for args_conflicts_with_subcommand

[4.0.29] - 2022-11-29

[4.0.28] - 2022-11-29

Fixes

• Fix wasm support which was broken in 4.0.27

[4.0.27] - 2022-11-24

Features

• Have Arg::value_parser accept Vec<impl Into<PossibleValue>>
• Implement Display and FromStr for ColorChoice

Fixes

• Remove soundness issue by switching from atty to is-terminal

[4.0.26] - 2022-11-16

Fixes

• (error) Fix typos in ContextKind::as_str

[4.0.25] - 2022-11-15

Features

• (error) Report available subcommands when required subcommand is missing

[4.0.24] - 2022-11-14

... (truncated)

Commits

• ec4ccf0 chore: Release
• 13fdb83 docs: Update changelog
• b877345 Merge pull request #4573 from epage/conflict
• 85ecb3e fix(parser): Override required when parent group has conflict
• d145b8b test(parser): Demonstrate required-overload bug
• 0eccd55 chore: Release
• 1e37c25 docs: Update changelog
• dcd5fec Merge pull request #4572 from epage/group
• dde22e7 style: Update for latest clippy
• dd8435d perf(parser): Reduce duplicate lookups
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[pull-request-quantifier-deprecated[bot]]

This PR has 143 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

---

Quantification details

``` Label : Medium Size : +116 -27 Percentile : 48.6% Total files changed: 2 Change summary by file extension: .lock : +115 -26 .toml : +1 -1 ``` > Change counts above are quantified counts, based on the [PullRequestQuantifier customizations](https://github.com/microsoft/PullRequestQuantifier/blob/main/docs/prquantifier-yaml.md).

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a balance between between PR complexity and PR review overhead. PRs within the optimal size (typical small, or medium sized PRs) mean: - Fast and predictable releases to production: - Optimal size changes are more likely to be reviewed faster with fewer iterations. - Similarity in low PR complexity drives similar review times. - Review quality is likely higher as complexity is lower: - Bugs are more likely to be detected. - Code inconsistencies are more likely to be detected. - Knowledge sharing is improved within the participants: - Small portions can be assimilated better. - Better engineering practices are exercised: - Solving big problems by dividing them in well contained, smaller problems. - Exercising separation of concerns within the code changes. #### What can I do to optimize my changes - Use the PullRequestQuantifier to quantify your PR accurately - Create a context profile for your repo using the [context generator](https://github.com/microsoft/PullRequestQuantifier/releases) - Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the `Excluded` section from your `prquantifier.yaml` context profile. - Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your `prquantifier.yaml` context profile. - Only use the labels that matter to you, [see context specification](./docs/prquantifier-yaml.md) to customize your `prquantifier.yaml` context profile. - Change your engineering behaviors - For PRs that fall outside of the desired spectrum, review the details and check if: - Your PR could be split in smaller, self-contained PRs instead - Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR). #### How to interpret the change counts in git diff output - One line was added: `+1 -0` - One line was deleted: `+0 -1` - One line was modified: `+1 -1` (git diff doesn't know about modified, it will interpret that line like one addition plus one deletion) - Change percentiles: Change characteristics (addition, deletion, modification) of this PR in relation to all other PRs within the repository.

---

Was this comment helpful? :thumbsup:  :ok_hand:  :thumbsdown: (Email) Customize PullRequestQuantifier for this repository.

[dependabot[bot]]

Superseded by #153.