feat: add autofix for alphabetize rule and change sort order to lexicographic (#936)

* feat: add autofix for `alphabetize` rule

* feat: improve rule-tester

* feat: skip autofix for fields with comments between or around

* should compare with lexicographic order

* add info about autofix in generate-docs script

* update examples deps to trigger patches folder changes

* fix build

* fix test on node 12

* add autofix even for fields with comments

* fix ESTree parser, convert `loc.column` to 0-based column number (#939)

* fixes after rebase

* fixes tests on graphql 15

Author: dimaMachina

.changeset/great-fans-count.md

@@ -0,0 +1,5 @@
+---
+'@graphql-eslint/eslint-plugin': patch
+---
+
+fix ESTree parser, convert `loc.column` to 0-based column number

.changeset/silver-worms-hear.md

@@ -0,0 +1,5 @@
+---
+'@graphql-eslint/eslint-plugin': minor
+---
+
+feat: add autofix for `alphabetize` rule and change sort order to lexicographic

.eslintrc.js

@@ -2,7 +2,7 @@ module.exports = {
   reportUnusedDisableDirectives: true,
   ignorePatterns: ['examples'],
   parser: '@typescript-eslint/parser',
-  extends: ['eslint:recommended', 'plugin:@typescript-eslint/recommended', 'standard', 'prettier'],
+  extends: ['eslint:recommended', 'standard', 'plugin:@typescript-eslint/recommended', 'prettier'],
   plugins: ['unicorn'],
   rules: {
     'no-empty': 'off',

docs/parser.md

@@ -36,7 +36,7 @@ Here's a list of changes that the parser performs, in order to make the GraphQL
 
 **Problem**: GraphQL uses `location` field to store the AST locations, while ESTree also uses it in a different structure.
 
-**Solution**: The parser creates a new `location` field that is compatible with ESTree, and renames the GraphQL `location` to `gqlLocation`.
+**Solution**: The parser creates a new `location` field that is compatible with ESTree.
 
 ### Loading GraphQL Schema
 

docs/rules/alphabetize.md

@@ -1,5 +1,7 @@
 # `alphabetize`
 
+🔧 The `--fix` option on the [command line](https://eslint.org/docs/user-guide/command-line-interface#--fix) can automatically fix some of the problems reported by this rule.
+
 - Category: `Schema & Operations`
 - Rule name: `@graphql-eslint/alphabetize`
 - Requires GraphQL Schema: `false` [ℹ️](../../README.md#extended-linting-rules-with-graphql-schema)

examples/basic/package.json

@@ -13,6 +13,6 @@
   },
   "devDependencies": {
     "@graphql-eslint/eslint-plugin": "3.7.0",
-    "eslint": "8.2.0"
+    "eslint": "8.7.0"
   }
 }

examples/code-file/package.json

@@ -13,6 +13,6 @@
   },
   "devDependencies": {
     "@graphql-eslint/eslint-plugin": "3.7.0",
-    "eslint": "8.2.0"
+    "eslint": "8.7.0"
   }
 }

examples/graphql-config-code-file/package.json

@@ -14,6 +14,6 @@
   },
   "devDependencies": {
     "@graphql-eslint/eslint-plugin": "3.7.0",
-    "eslint": "8.2.0"
+    "eslint": "8.7.0"
   }
 }

examples/graphql-config/package.json

@@ -13,6 +13,6 @@
   },
   "devDependencies": {
     "@graphql-eslint/eslint-plugin": "3.7.0",
-    "eslint": "8.2.0"
+    "eslint": "8.7.0"
   }
 }

examples/prettier/package.json

@@ -13,7 +13,7 @@
   },
   "devDependencies": {
     "@graphql-eslint/eslint-plugin": "3.7.0",
-    "eslint": "8.2.0",
+    "eslint": "8.7.0",
     "eslint-config-prettier": "8.3.0",
     "eslint-plugin-prettier": "4.0.0",
     "prettier": "2.4.1"