fix: useSchemaDefinitionFiles typo (#223)

* fix: schemaFileDefinitions typo
* chore: update readme, fix typo

Author: acao

README.md

@@ -127,11 +127,30 @@ Notice that `documents` key supports glob pattern and hence `["**/*.graphql"]` i
 ### Go to definition is using `generated_schema.graphql`, not my schema source files
 
 Ah yes, this is now the default behavior used by most users, who do not have source SDL files.
-If you're using an "SDL first" methodology, such as with apollo, you'll want to enable `useSchemaFileDefinition`.
+If you're using an "SDL first" methodology, such as with apollo, you'll want to enable `useSchemaFileDefinitions`.
 Add this to your settings:
 
 ```json
-"vscode-graphql.useSchemaFileDefinition": true,
+"vscode-graphql.useSchemaFileDefinitions": true,
+```
+
+you can also use graphql config if you need to mix and match these settings:
+
+```yml
+projects:
+  project1:
+    schema: project1/schema/schema.graphql
+    documents: project1/queries/**/*.{graphql,tsx,jsx,ts,js}
+    extensions:
+      languageService:
+        useSchemaFileDefinitions: true
+  project2:
+    schema: https://api.spacex.land/graphql/
+    documents: project2/queries.graphql
+    extensions:
+      endpoints:
+        default:
+          url: https://api.spacex.land/graphql/
 ```
 
 ### The extension fails with errors about duplicate types

package-lock.json

@@ -109,7 +109,7 @@
           "description": "Show codelens to execute operations inline",
           "default": true
         },
-        "vscode-graphql.useSchemaFileDefinition": {
+        "vscode-graphql.useSchemaFileDefinitions": {
           "type": [
             "boolean"
           ],
@@ -202,7 +202,7 @@
     "dotenv": "^8.2.0",
     "graphql": "^15.3.0",
     "graphql-config": "^3.0.3",
-    "graphql-language-service-server": "^2.5.3",
+    "graphql-language-service-server": "^2.5.4",
     "graphql-tag": "^2.11.0",
     "node-fetch": "^2.6.0",
     "ovsx": "0.1.0-next.dacd2fd",