annotate rust/rhg/src/commands/debugrhgsparse.rs @ 50427:98fc949bec14

rhg: support `status --print0`

This seems very easy to support, and useful because it makes it possible
to parse the [hg status] output even if the user creates files
with '\n' characters by accident.

use std::{
    ffi::{OsStr, OsString},
    os::unix::prelude::OsStrExt,
};

use crate::error::CommandError;
use hg::{self, utils::hg_path::HgPath};

pub const HELP_TEXT: &str = "";

pub fn args() -> clap::Command {
    clap::command!("debugrhgsparse")
        .arg(
            clap::Arg::new("files")
                .value_name("FILES")
                .required(true)
                .num_args(1..)
                .value_parser(clap::value_parser!(std::ffi::OsString))
                .help("Files to check against sparse profile"),
        )
        .about(HELP_TEXT)
}

pub fn run(invocation: &crate::CliInvocation) -> Result<(), CommandError> {
    let repo = invocation.repo?;

    let (matcher, _warnings) = hg::sparse::matcher(repo).unwrap();
    let files = invocation.subcommand_args.get_many::<OsString>("files");
    if let Some(files) = files {
        let files: Vec<&OsStr> = files
            .filter(|s| !s.is_empty())
            .map(|s| s.as_os_str())
            .collect();
        for file in files {
            invocation.ui.write_stdout(b"matches: ")?;
            invocation.ui.write_stdout(
                if matcher.matches(HgPath::new(file.as_bytes())) {
                    b"yes"
                } else {
                    b"no"
                },
            )?;
            invocation.ui.write_stdout(b" | file: ")?;
            invocation.ui.write_stdout(file.as_bytes())?;
            invocation.ui.write_stdout(b"\n")?;
        }
    }
    Ok(())
}