-
Notifications
You must be signed in to change notification settings - Fork 268
refactor: remove deprecated wrappers, dead code, and orphaned symbols #18873
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -14,11 +14,7 @@ | |
| // # Key Functions | ||
| // | ||
| // Summary Output: | ||
| // - formatCompilationSummary() - Format compilation statistics | ||
| // - formatValidationOutput() - Format validation results as JSON | ||
|
Comment on lines
14
to
17
|
||
| // | ||
| // These functions abstract output formatting, allowing the main compile | ||
| // orchestrator to focus on coordination while these handle presentation. | ||
|
|
||
| package cli | ||
|
|
||
|
|
@@ -31,12 +27,6 @@ import ( | |
|
|
||
| var compileOutputFormatterLog = logger.New("cli:compile_output_formatter") | ||
|
|
||
| // formatCompilationSummary formats compilation statistics for display | ||
| // This is a wrapper around printCompilationSummary for consistency | ||
| func formatCompilationSummary(stats *CompilationStats) { | ||
| printCompilationSummary(stats) | ||
| } | ||
|
|
||
| // formatValidationOutput formats validation results as JSON | ||
| func formatValidationOutput(results []ValidationResult) (string, error) { | ||
| compileOutputFormatterLog.Printf("Formatting validation output for %d workflow(s)", len(results)) | ||
|
|
@@ -52,15 +42,3 @@ func formatValidationOutput(results []ValidationResult) (string, error) { | |
|
|
||
| return string(jsonBytes), nil | ||
| } | ||
|
|
||
| // formatActionlintOutput displays the actionlint summary | ||
| // This is a wrapper around displayActionlintSummary for consistency | ||
| func formatActionlintOutput() { | ||
| displayActionlintSummary() | ||
| } | ||
|
|
||
| // formatStatsTable displays the workflow statistics table | ||
| // This is a wrapper around displayStatsTable for consistency | ||
| func formatStatsTable(statsList []*WorkflowStats) { | ||
| displayStatsTable(statsList) | ||
| } | ||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The batch strict/warning messages became less descriptive and inconsistent with the per-file validation errors (e.g.,
compile_validation.gouses "actionlint linter failed" / "zizmor security scan failed"). Consider lettingrunBatchLockFileToolaccept tool-specific message templates (or an operation description) so strict-mode errors and verbose warnings remain clear and consistent across batch vs per-file paths.