Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(chisel): enforce common::shell for chisel binary #9177

Draft
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

zerosnacks
Copy link
Member

Motivation

Enforces common::shell as added in #9109 for the chisel binary

Solution

Splits out the enforcement of the common shell per binary / large crate to avoid huge diffs making reviews easier

@zerosnacks zerosnacks changed the title chore(chisel): enforce common::shell for chisel binary chore(chisel): enforce common::shell for chisel binary Oct 23, 2024
@zerosnacks zerosnacks marked this pull request as ready for review October 23, 2024 15:00
@zerosnacks zerosnacks self-assigned this Oct 23, 2024
@zerosnacks zerosnacks added the T-blocked Type: blocked label Oct 23, 2024
@@ -205,7 +207,7 @@ async fn main_args(args: Chisel) -> eyre::Result<()> {
}

// Print welcome header
println!("Welcome to Chisel! Type `{}` to show available commands.", "!help".green());
sh_println!("Welcome to Chisel! Type `{}` to show available commands.", "!help")?;
Copy link
Member Author

@zerosnacks zerosnacks Oct 23, 2024

Choose a reason for hiding this comment

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

cc @DaniPopes in #9109 you noted messages ought not to be painted in color except for the warn / error keyword, is removing this here correct? Where yellow is used for warnings we use sh_warn!, for red (if an error) we use sh_err! and success (or used in an random way) should not be painted green, correct?

Copy link
Member

Choose a reason for hiding this comment

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

Yeah but that's for err and warn, and here it's in a REPL too, so it's fine

Copy link
Collaborator

@grandizzy grandizzy left a comment

Choose a reason for hiding this comment

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

lgtm!

@zerosnacks zerosnacks marked this pull request as draft October 23, 2024 17:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
T-blocked Type: blocked
Projects
Status: Ready For Review
Development

Successfully merging this pull request may close these issues.

4 participants