Struct inquire::DateSelect

pub struct DateSelect<'a> {
    pub message: &'a str,
    pub week_start: Weekday,
    pub starting_date: NaiveDate,
    pub min_date: Option<NaiveDate>,
    pub max_date: Option<NaiveDate>,
    pub help_message: Option<&'a str>,
    pub vim_mode: bool,
    pub formatter: DateFormatter<'a>,
    pub validators: Vec<DateValidator<'a>>,
    pub render_config: RenderConfig,
}

Prompt that allows user to select a date (time not supported) from an interactive calendar. Available via the date feature.

By default, the initial selected date is the current date. The user can navigate through the calendar by pressing the keyboard arrows. If the user also presses the control key along with the arrows, the user will be able to “fast-forward” to previous or next months or years.

More specifically:

• Left arrow moves to the day previous to the one selected, and to the month previous to the one selected when pressed with ctrl.
• Analogously, right arrow does the same, but moving to the next day or month.
• Up arrow moves to the day above to the one selected, basically a week before the selected date. When pressed with ctrl, it moves to the previous year.
• Analogously, the down arrow moves to a week later or a year later.

Finally, the user selects a date by pressing the space or enter keys.

DateSelect prompts provide several options of configuration:

• Prompt message: Required when creating the prompt.
• Default value: Default value selected when the calendar is displayed and the one select if the user submits without any previous actions. Current date by default.
• Help message: Message displayed at the line below the prompt.
• Formatter: Custom formatter in case you need to pre-process the user input before showing it as the final answer.
  • Formats to “Month Day, Year” by default.
• Validators: Custom validators to the user’s selected date, displaying an error message if the date does not pass the requirements.
• Week start: Which day of the week should be displayed in the first column of the calendar, Sunday by default.
• Min and max date: Inclusive boundaries of allowed dates in the interactive calendar. If any boundary is set, the user will not be able to move past them, consequently not being able to select any dates out of the allowed range.

Example

use chrono::{NaiveDate, Weekday};
use inquire::DateSelect;

let date = DateSelect::new("When do you want to travel?")
    .with_default(NaiveDate::from_ymd(2021, 8, 1))
    .with_min_date(NaiveDate::from_ymd(2021, 8, 1))
    .with_max_date(NaiveDate::from_ymd(2021, 12, 31))
    .with_week_start(Weekday::Mon)
    .with_help_message("Possible flights will be displayed according to the selected date")
    .prompt();

match date {
    Ok(_) => println!("No flights available for this date."),
    Err(_) => println!("There was an error in the system."),
}

Fields

message: &'a str

Message to be presented to the user.

week_start: Weekday

First day of the week when displaying week rows.

starting_date: NaiveDate

Starting date to be selected.

min_date: Option<NaiveDate>

Min date allowed to be selected.

max_date: Option<NaiveDate>

Max date allowed to be selected.

help_message: Option<&'a str>

Help message to be presented to the user.

vim_mode: bool

Whether vim mode is enabled. When enabled, the user can navigate through the options using hjkl.

formatter: DateFormatter<'a>

Function that formats the user input and presents it to the user as the final rendering of the prompt.

validators: Vec<DateValidator<'a>>

Collection of validators to apply to the user input.

Validators are executed in the order they are stored, stopping at and displaying to the user only the first validation error that might appear.

The possible error is displayed to the user one line above the prompt.

render_config: RenderConfig

RenderConfig to apply to the rendered interface.

Note: The default render config considers if the NO_COLOR environment variable is set to decide whether to render the colored config or the empty one.

When overriding the config in a prompt, NO_COLOR is no longer considered and your config is treated as the only source of truth. If you want to customize colors and still suport NO_COLOR, you will have to do this on your end.

Implementations

impl<'a> DateSelect<'a>

pub const DEFAULT_FORMATTER: DateFormatter<'a>

Default formatter, set to DEFAULT_DATE_FORMATTER

pub const DEFAULT_VIM_MODE: bool

Default value of vim mode. It is true because there is no typing functionality to be lost here.

pub const DEFAULT_HELP_MESSAGE: Option<&'a str>

Default help message.

pub const DEFAULT_VALIDATORS: Vec<DateValidator<'a>>

Default validators added to the DateSelect prompt, none.

pub const DEFAULT_WEEK_START: Weekday

Default week start.

pub const DEFAULT_MIN_DATE: Option<NaiveDate>

Default min date.

pub const DEFAULT_MAX_DATE: Option<NaiveDate>

Default max date.

pub fn new(message: &'a str) -> Self

Creates a DateSelect with the provided message, along with default configuration values.

pub fn with_help_message(self, message: &'a str) -> Self

Sets the help message of the prompt.

pub fn without_help_message(self) -> Self

Removes the set help message.

pub fn with_default(self, default: NaiveDate) -> Self

Sets the default date.

pub fn with_week_start(self, week_start: Weekday) -> Self

Sets the week start.

pub fn with_min_date(self, min_date: NaiveDate) -> Self

Sets the min date.

pub fn with_max_date(self, max_date: NaiveDate) -> Self

Sets the max date.

pub fn with_validator(self, validator: DateValidator<'a>) -> Self

Adds a validator to the collection of validators. You might want to use this feature in case you need to limit the user to specific choices, such as not allowing weekends.

Validators are executed in the order they are stored, stopping at and displaying to the user only the first validation error that might appear.

The possible error is displayed to the user one line above the prompt.

pub fn with_validators(self, validators: &[DateValidator<'a>]) -> Self

Adds the validators to the collection of validators in the order they are given. You might want to use this feature in case you need to limit the user to specific choices, such as not allowing weekends.

Validators are executed in the order they are stored, stopping at and displaying to the user only the first validation error that might appear.

The possible error is displayed to the user one line above the prompt.

pub fn with_vim_mode(self, vim_mode: bool) -> Self

Enables or disabled vim_mode.

pub fn with_formatter(self, formatter: DateFormatter<'a>) -> Self

Sets the formatter.

pub fn with_render_config(self, render_config: RenderConfig) -> Self

Sets the provided color theme to this prompt.

Note: The default render config considers if the NO_COLOR environment variable is set to decide whether to render the colored config or the empty one.

When overriding the config in a prompt, NO_COLOR is no longer considered and your config is treated as the only source of truth. If you want to customize colors and still suport NO_COLOR, you will have to do this on your end.

pub fn prompt_skippable(self) -> InquireResult<Option<NaiveDate>>

Parses the provided behavioral and rendering options and prompts the CLI user for input according to the defined rules.

This method is intended for flows where the user skipping/cancelling the prompt - by pressing ESC - is considered normal behavior. In this case, it does not return Err(InquireError::OperationCanceled), but Ok(None).

Meanwhile, if the user does submit an answer, the method wraps the return type with Some.

pub fn prompt(self) -> InquireResult<NaiveDate>

Parses the provided behavioral and rendering options and prompts the CLI user for input according to the defined rules.

Trait Implementations

impl<'a> Clone for DateSelect<'a>

fn clone(&self) -> DateSelect<'a>

Returns a copy of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.