build(deps): update inquire requirement from 0.6.2 to 0.7.5

[dependabot]

Updates the requirements on inquire to permit the latest version.

Release notes

Sourced from inquire's releases.

v0.7.5

• Fix user-provided ANSI escape codes from being removed when rendering.
  • Introduced on 0.7.0, this regression was making it impossible to have colorised text inside the prompt.
  • Now ANSI escape codes are properly emitted when rendering the prompt in the terminal.
  • Thanks @​leoetlino!

v0.7.4

• Fix unexpected behaviors of keep_filter option in MultiSelect prompts:
  • Filter input is now correcly getting reset only when keep_filter == false.
  • When the filter input is reset, the list of options is now correctly reset as well. Thanks @​Swivelgames for reporting #238.

v0.7.3

• Fix cursor occasionally blinking in unexpected places.

v0.7.2

• Pressing Ctrl+D now cancels the prompt. Thanks @​mikecvet for the PR!
• Add support for h and l bindings when vim_mode is enabled on MultiSelect prompts, clearing or selecting all options respectively. Thanks @​afh for the PR!
• Fix render issue #233 where cursor positioning at the end of a prompt was incorrect. Thanks @​msrd0 and @​Sydonian for reporting!

v0.7.1

• Fix render issue mikaelmello/inquire#228 when using console crate as the terminal backend. Thanks @​maospr for reporting.

v0.7.0

Breaking Changes

• The Select and Multiselect Filter now scores input and is now expected to return an Option<i64>, making it possible to order/rank the list of options. #176 None: Will not be displayed in the list of options. Some(score): score determines the order of options, higher score, higher on the list of options.
• Improved user experience on Password prompts. When there is a validation error, the input is cleared if the password is rendered using the Hidden display mode, matching the user expectation of having to write the password from scratch again. Thanks to @​CM-IV for the questions on #149!
• Allow lifetime customization of RenderConfig. #101. Thanks to @​arturfast for the suggestion #95.
• Implement fuzzy search as default on Select and MultiSelect prompts. Thanks @​Baarsgaard! #176
• Revamped keybindings for DateSelect.

Features

• Add one-liner helpers for quick scripts. #144.
• Add new option on MultiSelect prompts to set all options to be selected by default. Thanks to @​conikeec for the suggestion (#151)!
• Add new option on Select/MultiSelect prompts allowing to reset selection to the first item on filter-input changes. #176
• Emacs-like keybindings added where applicable (@​jasonish, @​EnigmaCurry):
  • Ctrl-p/Ctrl-n for up/down
  • Ctrl-b/Ctrl-f for left/right
  • Ctrl-j/Ctrl-g for enter/cancel
• Vim keybindings are always supported in DateSelect prompts.
• Added 'with_starting_filter_input' to both Select and MultiSelect, which allows for setting an initial value to the filter section of the prompt.

... (truncated)

Changelog

Sourced from inquire's changelog.

[0.7.5] - 2024-04-23

• Fix user-provided ANSI escape codes from being removed when rendering.
  • Introduced on 0.7.0, this regression was making it impossible to have colorised text inside the prompt.
  • Now ANSI escape codes are properly emitted when rendering the prompt in the terminal.

[0.7.4] - 2024-03-25

• Fix unexpected behaviors of keep_filter option in MultiSelect prompts:
  • Filter input is now correcly getting reset only when keep_filter == false.
  • When the filter input is reset, the list of options is now correctly reset as well. Thanks @​Swivelgames for reporting #238.

[0.7.3] - 2024-03-21

• Fix cursor occasionally blinking in unexpected places.

[0.7.2] - 2024-03-17

• Pressing Ctrl+D now cancels the prompt. Thanks @​mikecvet for the PR!
• Add support for h and l bindings when vim_mode is enabled on MultiSelect prompts, clearing or selecting all options respectively. Thanks @​afh for the PR!
• Fix render issue #233 where cursor positioning at the end of a prompt was incorrect. Thanks @​msrd0 and @​Sydonian for reporting!

[0.7.1] - 2024-03-10

• Fix render issue #228 when using console crate as the terminal backend. Thanks @​maospr for reporting.

[0.7.0] - 2024-02-24

Breaking Changes

• The Select and Multiselect Filter now scores input and is now expected to return an Option<i64>, making it possible to order/rank the list of options. #176 None: Will not be displayed in the list of options. Some(score): score determines the order of options, higher score, higher on the list of options.
• Improved user experience on Password prompts. When there is a validation error, the input is cleared if the password is rendered using the Hidden display mode, matching the user expectation of having to write the password from scratch again. Thanks to @​CM-IV for the questions on #149!
• Allow lifetime customization of RenderConfig. #101. Thanks to @​arturfast for the suggestion #95.
• Implement fuzzy search as default on Select and MultiSelect prompts. #176
• Revamped keybindings for DateSelect.

Features

• Add one-liner helpers for quick scripts. #144.
• Add new option on MultiSelect prompts to set all options to be selected by default. Thanks to @​conikeec for the suggestion (#151)!
• Add new option on Select/MultiSelect prompts allowing to reset selection to the first item on filter-input changes. #176
• Emacs-like keybindings added where applicable:
  • Ctrl-p/Ctrl-n for up/down
  • Ctrl-b/Ctrl-f for left/right
  • Ctrl-j/Ctrl-g for enter/cancel
• Vim keybindings are always supported in DateSelect prompts.
• Added 'with_starting_filter_input' to both Select and MultiSelect, which allows for setting an initial value to the filter section of the prompt.
• Added starting_input for CustomType. #194

... (truncated)

Commits

• 0e39b45 chore: release v0.7.5
• e3db8d1 Add changelog entry
• bf40860 Fix ANSI escape codes provided in input from being stripped when rendering
• 7fe8e5e Improve changelog messaging of v0.7.4
• 4ac91f3 chore: release v0.7.4
• 2b1c882 Reset list of options when filter input is reset (#240)
• 62ecc2e Fix unexpected behaviour of keep_filter option in MultiSelect prompts (#239)
• 82ab0e4 chore: release v0.7.3
• 8225428 Fix cursor occasionally blinking in unexpected places
• 724c7e6 chore: release v0.7.2
• 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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @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)

[coderabbitai]

Important

Review Skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.