google/closure-compiler

Option to fail on warnings

Open

#3,451 建立於 2019年8月13日

在 GitHub 查看
 (4 留言) (2 反應) (0 負責人)Java (7,176 star) (1,197 fork)batch import
help wantedinternal-issue-created

描述

I would like to propose an option that could make the compiler fail if at least one warning is encountered, regardless of errors and exit with a non-zero exit code.

This could be a simple flags such as --fail-on-warnings or a more sophisticated setting like --error-level that could introduce more granular control, i.e. still exit with 0 if compilation failed with errors.

Use case for this is either a purist approach when no warnings are tolerated or code quality control CI job that verifies new code with --checks-only.

貢獻者指南

技術棧
javajavascript
領域
toolingbuild system
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-2 days
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
mostly clear
前置要求
Javafamiliarity with closure compiler codebase
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
40
研究方向
The issue requests a command line flag to fail on warnings. Look at how existing flags are implemented in the compiler's main entry point, likely in CommandLineRunner.java or similar. Check the warning reporting mechanism and exit code handling. It may require adding an option to the Options class and modifying the compilation process to exit with non zero code when warnings are present.
Option to fail on warnings · google/closure-compiler#3451 | Good First Issue