Skip to content

Conversation

@kevgo
Copy link
Contributor

@kevgo kevgo commented Nov 15, 2025

resolves #174

@kevgo kevgo changed the title Print configuartion when receiving mismatching trigger Print configuration when receiving mismatching trigger Nov 15, 2025
Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bug: Unexpected Blank Lines Mar Error Output

The Display implementation for Configuration calls table.printstd() which prints directly to stdout as a side effect during string formatting. Combined with the \n prefixes in print_error()'s println! calls, this produces extra blank lines in error output that don't match the test expectations in the feature files.

src/config/data/configuration.rs#L94-L109

#[allow(clippy::str_to_string)]
impl Display for Configuration {
fn fmt(&self, f: &mut fmt::Formatter<'_>) -> fmt::Result {
let mut table = Table::new();
table.set_format(*FORMAT_NO_BORDER_LINE_SEPARATOR);
table.add_row(prettytable::row!["TRIGGER", "RUN"]);
for action in &self.actions {
table.add_row(prettytable::row![action.pattern, action.run]);
}
table.printstd();
f.write_str("Options:\n")?;
f.write_fmt(format_args!("- beforeRun.clearScreen: {}\n", self.options.before_run.clear_screen))?;
Ok(())
}
}

Fix in Cursor Fix in Web


# Conflicts:
#	src/client/trigger.rs
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

command or flag to print the configuration

1 participant