cjoudrey/graphql-schema-linter

Add --fix option

Open

#23 建立於 2017年8月9日

在 GitHub 查看
 (24 留言) (2 反應) (0 負責人)JavaScript (669 star) (62 fork)batch import
enhancementhelp wanted

描述

In some error cases, the linter can programmatically know what the schema should have been.

It would be awesome to provide a --fix option that would automatically resolve these errors.

Some example rules that could be fixed by the linter this way:

  • EnumValuesAllCaps
  • EnumValuesSortedAlphabetically
  • FieldsAreCamelCased
  • InputObjectValuesAreCamelCased
  • TypesAreCapitalized

貢獻者指南

技術棧
javascriptnodejs
領域
clideveloper experience
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-2 days
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
mostly clear
前置要求
GraphQL schema linter internalsunderstanding of lint rule structure
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
35
研究方向
First, examine the existing rule implementations to understand how errors are detected and reported. Look at the CLI entry point (likely in bin/ or src/cli.js) to see how options are parsed. Investigate the test suite for examples of rule testing. Then, propose a design for how the fix flag would integrate, perhaps by adding an optional fix method to each rule. Check if any existing PRs or comments discuss implementation details.