##// END OF EJS Templates
rhg: extract function handle_stdout_error...
rhg: extract function handle_stdout_error Avoid repeating the logic of handling stdout write errors. Differential Revision: https://phab.mercurial-scm.org/D8870

File last commit:

r45922:5dbf875b default
r45925:10c36ead default
Show More
root.rs
34 lines | 731 B | application/rls-services+xml | RustLexer
use crate::commands::Command;
use crate::error::CommandError;
use crate::ui::Ui;
use hg::operations::FindRoot;
use hg::utils::files::get_bytes_from_path;
pub const HELP_TEXT: &str = "
Print the root directory of the current repository.
Returns 0 on success.
";
pub struct RootCommand<'a> {
ui: &'a Ui,
}
impl<'a> RootCommand<'a> {
pub fn new(ui: &'a Ui) -> Self {
RootCommand { ui }
}
}
impl<'a> Command<'a> for RootCommand<'a> {
fn run(&self) -> Result<(), CommandError> {
let path_buf = FindRoot::new().run()?;
let bytes = get_bytes_from_path(path_buf);
// TODO use formating macro
self.ui.write_stdout(&[bytes.as_slice(), b"\n"].concat())?;
Ok(())
}
}