gcr
gcr copied to clipboard
chore(deps): bump dialoguer from 0.10.1 to 0.10.3
Bumps dialoguer from 0.10.1 to 0.10.3.
Changelog
Sourced from dialoguer's changelog.
0.10.3
Enhancements
- Fix various issues with fuzzy select
- Enable customization of number of rows for fuzzy select
- Added post completion text for input
- Various cursor movement improvements
- Correctly ignore unknown keys.
- Reset prompt height in
TermThemeRenderer::clear.0.10.2
Enhancements
- Fix fuzzy select active item colors.
- Fix fuzzy search clear on cancel.
- Clear everything on cancel via escape key.
Commits
d54c4280.10.3e898041Added .vscode config63bdd06Update changelog565d64ffix: also reset self.prompt_height in TermThemeRenderer::clear. (#191)8d39d79Update readmea6659ceReturn Err on Confirm's read_key when not a terminal (#229)1a7f120Fix long lines in select failing size calcuations (#239)9bc846eMake clippy happy7d5488eFixed CI workflow for macos and added makefiled35b5deIgnore Unknown keys (#192)- 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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
This PR has 12 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 : +9 -3
Percentile : 4.8%
Total files changed: 2
Change summary by file extension:
.lock : +8 -2
.toml : +1 -1
Change counts above are quantified counts, based on the PullRequestQuantifier customizations.
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
- 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
Excludedsection from yourprquantifier.yamlcontext profile. - Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your
prquantifier.yamlcontext profile. - Only use the labels that matter to you, see context specification to customize your
prquantifier.yamlcontext 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).
- For PRs that fall outside of the desired spectrum, review the details and check if:
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.
Codecov Report
Base: 51.81% // Head: 38.78% // Decreases project coverage by -13.03% :warning:
Coverage data is based on head (
4daeb6a) compared to base (2aaadf2). Patch has no changes to coverable lines.
Additional details and impacted files
@@ Coverage Diff @@
## master #151 +/- ##
===========================================
- Coverage 51.81% 38.78% -13.04%
===========================================
Files 10 10
Lines 577 446 -131
===========================================
- Hits 299 173 -126
+ Misses 278 273 -5
| Impacted Files | Coverage Δ | |
|---|---|---|
| src/util.rs | 66.66% <0.00%> (-13.71%) |
:arrow_down: |
| src/extensions.rs | 79.41% <0.00%> (-8.31%) |
:arrow_down: |
| src/arguments.rs | 81.53% <0.00%> (-5.06%) |
:arrow_down: |
| src/message.rs | 13.04% <0.00%> (-4.99%) |
:arrow_down: |
| src/config.rs | 71.79% <0.00%> (-2.68%) |
:arrow_down: |
| src/log.rs | 100.00% <0.00%> (ø) |
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.
:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.