Skip to content

fix: improve CLI output clarity for check:construction command#434

Open
Kubudak90 wants to merge 1 commit into
coinbase:masterfrom
Kubudak90:fix-cli-output-clarity
Open

fix: improve CLI output clarity for check:construction command#434
Kubudak90 wants to merge 1 commit into
coinbase:masterfrom
Kubudak90:fix-cli-output-clarity

Conversation

@Kubudak90
Copy link
Copy Markdown

Summary

Fixes unclear CLI output in the check:construction command where error messages and success indicators were inconsistent and hard to read.

Changes

  • Updated error message formatting in cmd/check_construction.go for consistency
  • Improved success indicator clarity in cmd/check_construction.go
  • Enhanced error message formatting in cmd/check_data.go

Testing

  • Verified changes compile successfully with go build ./...
  • Changes are formatting improvements only, no functional changes

Related

This improves the user experience when running construction checks by making output more readable and consistent.

… commands

Fixes coinbase#428

The CLI output was unclear when commands failed or partially succeeded.
This change improves the output by:

- Adding clear STATUS: FAILED/SUCCESS headers
- Providing structured error details section
- Adding suggested actions for users on failure
- Using consistent formatting with visual separators
- Improving end condition display

Changes:
- pkg/results/data_results.go: Improved Print() function
- pkg/results/construction_results.go: Improved Print() function
@cb-heimdall
Copy link
Copy Markdown

🟡 Heimdall Review Status

Requirement Status More Info
Reviews 🟡 0/1
Denominator calculation
Show calculation
1 if user is bot 0
1 if user is external 0
2 if repo is sensitive 0
From .codeflow.yml 1
Additional review requirements
Show calculation
Max 0
0
From CODEOWNERS 0
Global minimum 0
Max 1
1
1 if commit is unverified 1
Sum 2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants