beautifier/js-beautify

Add option to run js-beautify as check with fail on change

Open

#741 建立於 2015年7月20日

在 GitHub 查看
 (12 留言) (10 反應) (0 負責人)JavaScript (8,342 star) (1,460 fork)batch import
good first issuetype: enhancement

描述

In order to run js-beautify as a non-intrusive pre-commit hook in git (or any other place where you wish to check that the code is beautified, but not actually change it), it would help immensely to have an option not to actually save the beautified version of a file anywhere, but to just have js-beautify fail with a non-zero exit code and some reasonable message.

貢獻者指南

技術棧
javascriptnodejs
領域
clitooling
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
2
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-3 hours
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
JavaScriptCLI basicsNode.js
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
85
研究方向
Examine the main entry point of js beautify (likely in bin/js beautify.js) to understand how options are parsed and how files are processed. Look at how the current beautification is performed and where the output is written. The goal is to add a ' check' flag that runs beautification but instead of saving, compares the result to the original and fails with exit code 1 if different. Review any existing configuration options for similar behavior.