search

sdttttt / gcr

📑 Compact specification git commit tool, it has a variety of practical small functions. (Inspired by git-cz on Node.js)
https://crates.io/crates/grc
The Unlicense
28 stars 6 forks source link

chore(deps): bump dialoguer from 0.8.0 to 0.10.0 #100

Closed dependabot[bot] closed 2 years ago

dependabot[bot] commented 2 years ago

Bumps dialoguer from 0.8.0 to 0.10.0.

Changelog

Sourced from dialoguer's changelog.

0.10.0

Enhancements

  • Loosen some trait bounds
  • Improve keyboard interactions (#141, #162)
  • Added max_length to MultiSelect, Select and Sort
  • Allow completion support for Input::interact_text* behind completion feature

Breaking

  • All prompts *::new will now don't report selected values unless report(true) is called on them.

0.9.0

Enhancements

  • Apply input validation to the default value too in Input
  • Added FuzzySelect behind fuzzy-select feature
  • Allow history processing for Input::interact_text* behind history feature
  • Added interact_*_opt methods for MultiSelect and Sort.

Breaking

  • Updated MSRV to 1.51.0
  • Editor is gated behind editor feature
  • Password, Theme::format_password_prompt and Theme::format_password_prompt_selection are gated behind password feature
  • Remove Select::paged(), Sort::paged() and MultiSelect::paged() in favor of automatic paging based on terminal size
Commits
  • e93d993 Release 0.10.0
  • c93224a Merge pull request #162 from craciuncezar/limit-visible-options-in-fuzzy-select
  • dee84e9 Merge pull request #169 from bryanhitc/bryanhitc/fix-completion-buffer-overflow
  • e4ffea8 fix formatting and improve naming
  • cb1e9a5 Fix buffer overflow for completion example
  • 252a183 Fix linting warnings
  • f1e46a5 Add scroll functionality
  • 94a276d Limit the number of visible options in fuzzy select
  • 29da763 Merge pull request #153 from danieleades/refactor/clippy
  • 8fde6ae lint examples and tests
  • Additional commits viewable in compare view


Dependabot compatibility score

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 will merge this PR once CI passes on it, as requested by @sdttttt.

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)
codecov[bot] commented 2 years ago

Codecov Report

Merging #100 (71e93c5) into master (11e747e) will not change coverage. The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #100   +/-   ##
=======================================
  Coverage   43.38%   43.38%           
=======================================
  Files          11       11           
  Lines         597      597           
=======================================
  Hits          259      259           
  Misses        338      338

Continue to review full report at Codecov.

Legend - Click here to learn more Δ = absolute <relative> (impact), ø = not affected, ? = missing data Powered by Codecov. Last update 11e747e...71e93c5. Read the comment docs.

pull-request-quantifier-deprecated[bot] commented 2 years ago

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

Quantification details

``` Label : Extra Small Size : +5 -25 Percentile : 12% Total files changed: 2 Change summary by file extension: .lock : +4 -24 .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 detetcted. - 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.

sdttttt commented 2 years ago

@dependabot merge