vscode-apollo 1.19.3 → 1.20.0

package/.changeset/README.md

@@ -0,0 +1,8 @@
+# Changesets
+
+Hello and welcome! This folder has been automatically generated by `@changesets/cli`, a build tool that works
+with multi-package repos, or single-package repos to help you version and publish your code. You can
+find the full documentation for it [in our repository](https://github.com/changesets/changesets)
+
+We have a quick list of common questions to get you started engaging with this project in
+[our documentation](https://github.com/changesets/changesets/blob/main/docs/common-questions.md)

package/.changeset/config.json

@@ -0,0 +1,14 @@
+{
+  "$schema": "https://unpkg.com/@changesets/config@2.3.1/schema.json",
+  "changelog": [
+    "@changesets/changelog-github",
+    { "repo": "apollographql/vscode-graphql" }
+  ],
+  "commit": false,
+  "fixed": [],
+  "linked": [],
+  "access": "public",
+  "baseBranch": "main",
+  "updateInternalDependencies": "patch",
+  "ignore": []
+}

package/.circleci/config.yml

@@ -0,0 +1,82 @@
+version: 2.1
+
+orbs:
+  secops: apollo/circleci-secops-orb@2.0.0
+
+executors:
+  node:
+    docker:
+      - image: circleci/node:12.16.1-browsers
+    working_directory: ~/vscode-graphql
+
+commands:
+  npm-install:
+    steps:
+      - restore_cache:
+          name: Restore npm cache
+          keys:
+            - npm-packages-{{ checksum "package-lock.json" }}--{{ checksum ".circleci/config.yml" }}
+      - run:
+          name: Install dependencies
+          command: npm ci --prefer-offline
+      - save_cache:
+          name: Save npm cache
+          key: npm-packages-{{ checksum "package-lock.json" }}--{{ checksum ".circleci/config.yml" }}
+          paths:
+            - ~/.npm
+
+jobs:
+  lint:
+    executor: node
+    steps:
+      - checkout
+      - npm-install
+      - run:
+          name: Ensure test reports output dir exists
+          command: mkdir -p /tmp/test-reports/lint
+      - run:
+          name: Run lint (currenty prettier)
+          command: npm run lint -- --format junit --output-file /tmp/test-reports/lint/results.xml
+      - store_test_results:
+          path: /tmp/test-reports
+
+  typescript:
+    executor: node
+    steps:
+      - checkout
+      - npm-install
+      - run:
+          name: TypeScript Check
+          command: npm run typecheck
+
+  test-unit:
+    executor: node
+    steps:
+      - checkout
+      - npm-install
+      - run:
+          name: Ensure test reports output dir exists
+          command: mkdir -p /tmp/test-reports/test-unit
+      - run:
+          name: Test Unit
+          command: npm run test-unit -- --ci --reporters=jest-junit
+          environment:
+            JEST_JUNIT_OUTPUT_DIR: "/tmp/test-reports/test-unit"
+      - store_test_results:
+          path: /tmp/test-reports
+
+workflows:
+  build-test-deploy:
+    jobs:
+      - lint
+      - typescript
+      - test-unit
+  security-scans:
+    jobs:
+      - secops/gitleaks:
+          context:
+            - platform-docker-ro
+            - github-orb
+            - secops-oidc
+          git-base-revision: <<#pipeline.git.base_revision>><<pipeline.git.base_revision>><</pipeline.git.base_revision >>
+          git-revision: << pipeline.git.revision >>

package/.eslintrc.js

@@ -0,0 +1,10 @@
+module.exports = {
+  parser: "@typescript-eslint/parser",
+  plugins: ["prettier", "@typescript-eslint"],
+  // Skip generated file.
+  ignorePatterns: ["src/language-server/graphqlTypes.ts"],
+  rules: {
+    "prettier/prettier": "error",
+  },
+  extends: ["prettier"],
+};

package/.gitattributes

@@ -0,0 +1 @@
+package-lock.json -diff

package/.github/workflows/release.yml

@@ -0,0 +1,95 @@
+name: Release
+
+on:
+  push:
+    branches:
+      - main
+
+concurrency: ${{ github.workflow }}-${{ github.ref }}
+
+jobs:
+  release:
+    name: Changesets Release
+    # Prevents action from creating a PR on forks
+    if: github.repository == 'apollographql/vscode-graphql'
+    runs-on: ubuntu-latest
+    # Permissions necessary for Changesets to push a new branch and open PRs
+    # (for automated Version Packages PRs), and request the JWT for provenance.
+    # More info: https://docs.github.com/en/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#adding-permissions-settings
+    permissions:
+      contents: write
+      pull-requests: write
+      id-token: write
+    steps:
+      - name: Checkout repo
+        uses: actions/checkout@v4
+        with:
+          # Fetch entire git history so  Changesets can generate changelogs
+          # with the correct commits
+          fetch-depth: 0
+
+      - name: Check for pre.json file existence
+        id: check_files
+        uses: andstor/file-existence-action@v2.0.0
+        with:
+          files: ".changeset/pre.json"
+
+      - name: Append NPM token to .npmrc
+        run: |
+          cat << EOF > "$HOME/.npmrc"
+            //registry.npmjs.org/:_authToken=$NPM_TOKEN
+          EOF
+        env:
+          NPM_TOKEN: ${{ secrets.NPM_TOKEN }}
+
+      - name: Setup Node.js 18.x
+        uses: actions/setup-node@v3
+        with:
+          node-version: 18.x
+
+      - name: Install dependencies
+        run: npm ci
+
+      - name: Create release PR or publish to npm + GitHub
+        id: changesets
+        if: steps.check_files.outputs.files_exists == 'false'
+        uses: changesets/action@v1
+        with:
+          version: npm run changeset-version
+          publish: npm run changeset-publish
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          NPM_TOKEN: ${{ secrets.NPM_TOKEN }}
+
+      - name: Publish to Visual Studio Marketplace
+        if: steps.changesets.outcome == 'success' && steps.changesets.outputs.published == 'true'
+        uses: HaaLeo/publish-vscode-extension@v1
+        with:
+          pat: ${{ secrets.VS_MARKETPLACE_TOKEN }}
+          registryUrl: https://marketplace.visualstudio.com
+          baseContentUrl: https://raw.githubusercontent.com/apollographql/vscode-graphql
+
+      - name: Send a Slack notification on publish
+        if: steps.changesets.outcome == 'success' && steps.changesets.outputs.published == 'true'
+        id: slack
+        uses: slackapi/slack-github-action@v1.24.0
+        with:
+          # Slack channel id, channel name, or user id to post message
+          # See also: https://api.slack.com/methods/chat.postMessage#channels
+          # You can pass in multiple channels to post to by providing
+          # a comma-delimited list of channel IDs
+          channel-id: "C02J316U84V"
+          payload: |
+            {
+              "blocks": [
+                {
+                  "type": "section",
+                  "text": {
+                    "type": "mrkdwn",
+                    "text": "A new version of `vscode-apollo` was released: <https://github.com/apollographql/vscode-apollo/releases/tag/v${{ fromJson(steps.changesets.outputs.publishedPackages)[0].version }}|v${{ fromJson(steps.changesets.outputs.publishedPackages)[0].version }}> :rocket:"
+                  }
+                }
+              ]
+            }
+        env:
+          SLACK_BOT_TOKEN: ${{ secrets.SLACK_BOT_TOKEN }}

package/.gitleaks.toml

@@ -0,0 +1,26 @@
+# This file exists primarily to influence scheduled scans that Apollo runs of all repos in Apollo-managed orgs. 
+# This is an Apollo-Internal link, but more information about these scans is available here:
+# https://apollographql.atlassian.net/wiki/spaces/SecOps/pages/81330213/Everything+Static+Application+Security+Testing#Scheduled-Scans.1
+# 
+# Apollo is using Gitleaks (https://github.com/gitleaks/gitleaks) to run these scans.
+# However, this file is not something that Gitleaks natively consumes. This file is an
+# Apollo-convention. Prior to scanning a repo, Apollo merges
+# our standard Gitleaks configuration (which is largely just the Gitleaks-default config) with
+# this file if it exists in a repo. The combined config is then used to scan a repo.
+# 
+# We did this because the natively-supported allowlisting functionality in Gitleaks didn't do everything we wanted
+# or wasn't as robust as we needed. For example, one of the allowlisting options offered by Gitleaks depends on the line number
+# on which a false positive secret exists to allowlist it. (https://github.com/gitleaks/gitleaks#gitleaksignore).
+# This creates a fairly fragile allowlisting mechanism. This file allows us to leverage the full capabilities of the Gitleaks rule syntax
+# to create allowlisting functionality.
+
+
+[[ rules ]]
+    id = "generic-api-key"
+    [ rules.allowlist ]
+        commits = [
+            # This creates an allowlist for a UUID that was
+            # used as an identifier, but is not secret
+            # See https://github.com/apollographql/vscode-graphql/blob/a905280c143991b3fd675f8b4c3a7da277ccf095/packages/apollo-language-server/src/engine/index.ts#L86
+            "a905280c143991b3fd675f8b4c3a7da277ccf095"
+        ]

package/.nvmrc

@@ -0,0 +1 @@
+v18

package/.prettierrc

@@ -0,0 +1,5 @@
+{
+  "tabWidth": 2,
+  "useTabs": false,
+  "singleQuote": false
+}

package/.vscode/launch.json

@@ -0,0 +1,61 @@
+{
+  "version": "0.2.0",
+  // List of configurations. Add new configurations or edit existing ones.
+  "configurations": [
+    {
+      "name": "Launch VS Code Extension",
+      "type": "extensionHost",
+      "request": "launch",
+      "preLaunchTask": "npm: watch",
+      "runtimeExecutable": "${execPath}",
+      "args": [
+        "--extensionDevelopmentPath=${workspaceRoot}"
+      ],
+      "stopOnEntry": false,
+      "sourceMaps": true,
+      "outFiles": ["${workspaceRoot}/lib/**/*.js"]
+    },
+    {
+      "name": "Attach to TS Server",
+      "type": "node",
+      "request": "attach",
+      "protocol": "inspector",
+      "port": 6009,
+      "sourceMaps": true
+    },
+    {
+      "name": "Extension Tests",
+      "type": "extensionHost",
+      "request": "launch",
+      "runtimeExecutable": "${execPath}",
+      "args": [
+        "--disable-extensions",
+        "--extensionDevelopmentPath=${workspaceFolder}",
+      ],
+      "outFiles": ["${workspaceFolder}/lib/**/*.js"],
+      "preLaunchTask": "npm: watch"
+    },
+    {
+      "name": "Attach to Test Debugger",
+      "type": "node",
+      "request": "attach",
+      "protocol": "inspector",
+      "port": 9001,
+      "sourceMaps": true
+    },
+    {
+      "name": "Attach to CLI Debugger",
+      "type": "node",
+      "request": "attach",
+      "protocol": "inspector",
+      "port": 9002,
+      "sourceMaps": true
+    }
+  ],
+  "compounds": [
+    {
+      "name": "Extension + Server",
+      "configurations": ["Launch VS Code Extension", "Attach to TS Server"]
+    }
+  ]
+}

package/.vscode/settings.json

@@ -0,0 +1,16 @@
+// Place your settings in this file to overwrite default and user settings.
+{
+  "editor.tabSize": 2,
+  "editor.insertSpaces": true,
+  "editor.rulers": [110],
+  "editor.wordWrapColumn": 110,
+  "files.trimTrailingWhitespace": true,
+  "files.insertFinalNewline": true,
+  "files.exclude": {
+    "**/.git": true,
+    "**/.DS_Store": true,
+    "node_modules": false
+  },
+  "typescript.tsdk": "node_modules/typescript/lib",
+  "debug.node.autoAttach": "on"
+}

package/.vscode/tasks.json

@@ -0,0 +1,18 @@
+{
+	"version": "2.0.0",
+	"tasks": [
+			{
+					"type": "npm",
+					"script": "watch",
+					"problemMatcher": "$tsc-watch",
+					"isBackground": true,
+					"presentation": {
+							"reveal": "never"
+					},
+					"group": {
+							"kind": "build",
+							"isDefault": true
+					}
+			}
+	]
+}

package/.vscodeignore

@@ -1 +1,17 @@
-lib/testRunner/**
+.circleci
+.vscode
+.vscode-test
+src
+.env
+.eslintrc.js
+.git
+.gitignore
+.nvmrc
+.prettierrc
+.gitattributes
+codegen.yml
+graphql.configuration.json
+jest.config.ts
+package-lock.json
+tsconfig.build.json
+tsconfig.json

package/CHANGELOG.md

@@ -1 +1,172 @@
-To see release notes and changes for `vscode-apollo`, See the [apollo-tooling changelog](https://github.com/apollographql/apollo-tooling/blob/master/CHANGELOG.md)
+# CHANGELOG
+
+## 1.20.0
+
+### Minor Changes
+
+- [#105](https://github.com/apollographql/vscode-graphql/pull/105) [`43879da4`](https://github.com/apollographql/vscode-graphql/commit/43879da40f3a3b7c6327cf165fca9980e04b4bc7) Thanks [@zovits](https://github.com/zovits)! - Add inline syntax highlighting support for Lua
+
+### Patch Changes
+
+- [#99](https://github.com/apollographql/vscode-graphql/pull/99) [`2a3fc1bb`](https://github.com/apollographql/vscode-graphql/commit/2a3fc1bb3c38245f09a5e5e0a19900ea0cfc58b3) Thanks [@pvinis](https://github.com/pvinis)! - Support tagging inside of parentheses
+
+- [#73](https://github.com/apollographql/vscode-graphql/pull/73) [`d07b303d`](https://github.com/apollographql/vscode-graphql/commit/d07b303d31fdf0810f8be163bb3973c564cf0754) Thanks [@rachsmithcodes](https://github.com/rachsmithcodes)! - Return early instead of erroring on missing fields
+
+- [#97](https://github.com/apollographql/vscode-graphql/pull/97) [`2b57a1af`](https://github.com/apollographql/vscode-graphql/commit/2b57a1afd9882a139a47af9b55496b7aa62fde2b) Thanks [@clf17222592](https://github.com/clf17222592)! - Support configuration files with .cjs file extension
+
+- [#78](https://github.com/apollographql/vscode-graphql/pull/78) [`8b02374a`](https://github.com/apollographql/vscode-graphql/commit/8b02374a355ef9304e1fe9b0d89bcf559e618428) Thanks [@jtgrenz](https://github.com/jtgrenz)! - Fix regex for ruby heredoc
+
+### 1.19.11
+
+- Fix directive highlighting on enums and arguments [#6716](https://github.com/apollographql/vscode-graphql/pull/71)
+
+### 1.19.10
+
+- Fix highlighting on schema extension directives [#66](https://github.com/apollographql/vscode-graphql/pull/66)
+
+### 1.19.9
+
+- Add validation/completion for #graphql annotated strings in js [#47](https://github.com/apollographql/vscode-graphql/pull/47)
+- Add config option for disabling 'Run in Studio' button [#46](https://github.com/apollographql/vscode-graphql/pull/46)
+- Add config option to disable switching to output tab on error [#44](https://github.com/apollographql/vscode-graphql/pull/44)
+
+### 1.19.8
+
+- Move 'Run in Studio' icon to end of line [#42](https://github.com/apollographql/vscode-graphql/pull/42)
+- Fix syntax highlighting for directives on types [#36](https://github.com/apollographql/vscode-graphql/pull/36)
+
+### 1.19.7
+
+- Specify files with conflicting documents for the 'There are multiple definitions' message. [#29](https://github.com/apollographql/vscode-graphql/pull/29)
+- Dont watch non file documents. Diff view will no longer crash extension. [#28](https://github.com/apollographql/vscode-graphql/pull/28)
+- Upgrade graphql version to 15.5 [#34](https://github.com/apollographql/vscode-graphql/pull/34)
+
+### 1.19.6
+
+- Fix 'Run in explorer' link. [#25](https://github.com/apollographql/vscode-graphql/pull/25)
+
+### 1.19.5
+
+- Add a 'Run in explorer' gutter action. [#20](https://github.com/apollographql/vscode-graphql/pull/20)
+- Switch Studio query that fetches timing hints to use a newer field. This should have no user-observable impact, though we may eventually remove the old field once most users have upgraded their extensions. [#22](https://github.com/apollographql/vscode-graphql/pull/22)
+- Add support for highlighting Svelte files [#17](https://github.com/apollographql/vscode-graphql/pull/17)
+- Add support for `.cjs` files [#4](https://github.com/apollographql/vscode-graphql/pull/4)
+- Exclude localSchemaFile when looking for graphql documents. This should fix the common case for hitting `VSCode Plugin: Loading Schema Twice` errors. [#8](https://github.com/apollographql/vscode-graphql/pull/8)
+
+### 1.19.4
+
+- Fix VS Code extension performance issues for larger projects [#1938](https://github.com/apollographql/apollo-tooling/pull/1938)
+
+-> _Note:_ This project used to live in the [apollo-tooling](https://github.com/apollographql/apollo-tooling) repo. Refer to the [apollo-tooling CHANGELOG](https://github.com/apollographql/apollo-tooling/blob/master/CHANGELOG.md) for full list of changes before April 25, 2021. See below for filtered changelog from apollo-tooling.
+
+## Legacy apollo-tooling Changelog
+
+### apollo-tools@0.5.1
+
+- Remove dependency on `apollo-env`, so using this package no longer installs polyfills.
+
+### apollo-env@0.10.0
+
+- deps: Updated `node-fetch` to v2.6.1
+
+### apollo-env@0.9.0
+
+- The following utility functions are no longer exported from `apollo-env` and can now be found in the `apollo-graphql` library:
+  - `createHash`
+  - `isNodeLike`
+  - `mapValues`
+  - `isNotNullOrDefined`
+
+### `apollo-language-server@1.14.3`
+
+- `apollo-language-server@1.14.3`
+  - Fix issue where fragment definitions only included in `@client` fields would not be stripped ((AP-682)(https://golinks.io/AP-682), [#1454](https://github.com/apollographql/apollo-tooling/pull/1454))
+
+### `apollo-language-server@1.14.2`
+
+- `apollo-language-server@1.14.2`
+  - Fix #735 caused #928 error implement [#1461](https://github.com/apollographql/apollo-tooling/pull/1461)
+  - Fix dirname parsing for ts config files [#1463](https://github.com/apollographql/apollo-tooling/pull/1463)
+
+### `vscode-apollo@1.9.1`, `apollo-language-server@1.14.1`
+
+- `apollo-language-server@1.14.1`
+  - Fix cache invalidation bug for reload schema which caused outdated results in autocomplete [#1446](https://github.com/apollographql/apollo-tooling/pull/1446)
+
+### `vscode-apollo@1.9.0`, `apollo-language-server@1.14.0`, `apollo-codegen-swift@0.34.2`
+
+- `vscode-apollo@1.9.0`
+  - Add Dart support for vscode [#1385](https://github.com/apollographql/apollo-tooling/pull/1385)
+- `apollo-language-server@1.14.0`
+  - Add Dart operation extraction [#1385](https://github.com/apollographql/apollo-tooling/pull/1385)
+- `apollo-codegen-swift@0.34.2`
+  - Prevent compiler warnings for redundant access-level modifiers when using `--namespace` [1241](https://github.com/apollographql/apollo-tooling/pull/1241)
+
+### `apollo-language-server@1.5.2`, `vscode-apollo@1.5.2`
+
+- `apollo-language-server@1.5.2`
+  - fix single apollo.config breaking others loaded at the same time [#1055](https://github.com/apollographql/apollo-tooling/pull/1055)
+  - Fix broken fileSet.includesFile to use full filepath [#1055](https://github.com/apollographql/apollo-tooling/pull/1055)
+- `vscode-apollo@1.5.2`
+
+### `apollo-env@0.3.1`
+
+- `apollo-env@0.3.1`
+  - Fix core-js dependency by pinning to `3.0.0-beta.3` [#961](https://github.com/apollographql/apollo-tooling/pull/961)
+
+### `apollo-language-server@1.4.1`
+
+- `apollo-language-server` 1.4.1
+  - Fix edge case for empty operations [#959](https://github.com/apollographql/apollo-tooling/pull/959)
+
+### `apollo-language-server@1.0.0`
+
+> NOTE: Many of the updates and changes in this release came from a complete rebuild of the Apollo CLI in preparation for GraphQL summit. Many of these changes can be traced to [this commit](https://github.com/apollographql/apollo-tooling/commit/d2d73f9c597845355b7ee267e411d80d1c493043) but aren't tied to a specific pull request, and won't be linked.
+
+- `apollo-language-server@1.0.0`
+  - Initial release of `apollo-language-server` to support `vscode-apollo`, and `apollo`
+  - Supports editor features for...
+    - Autocompletion of GraphQL documents
+    - Hover information for fields anr arguments
+    - Type definitions and references
+    - Code lenses for open files
+- `vscode-apollo@1.0.0`
+  - Initial Release of `vscode-apollo`
+  - Switching of schema tags [#632](https://github.com/apollographql/apollo-tooling/pull/632)
+  - Supports all of the editor features exposed by `apollo-language-server`
+
+#### :rocket: Feature
+
+- `apollo-language-server`, `apollo-vscode`
+  - [#536](https://github.com/apollographql/apollo-tooling/pull/536) Display status of loading tasks for config and Engine stats ([@shadaj](https://github.com/shadaj))
+
+#### :bug: Bug Fix
+
+- `apollo-cli`, `apollo-language-server`, `apollo-vscode`
+  - [#519](https://github.com/apollographql/apollo-tooling/pull/519) [VSCode] Fix detection of projects inside folders ([@shadaj](https://github.com/shadaj))
+
+#### :memo: Documentation
+
+- `apollo-cli`, `apollo-vscode`
+  - [#521](https://github.com/apollographql/apollo-tooling/pull/521) Add README for the VS Code extension ([@shadaj](https://github.com/shadaj))
+
+#### :rocket: Feature
+
+- `apollo-language-server`
+  - [#516](https://github.com/apollographql/apollo-tooling/pull/516) Code complete default query variables ([@shadaj](https://github.com/shadaj))
+- `apollo-language-server`, `apollo-vscode`
+  - [#515](https://github.com/apollographql/apollo-tooling/pull/515) Fix missing descriptions and add more hover information for arguments ([@shadaj](https://github.com/shadaj))
+- `apollo-cli`, `apollo-codegen-core`, `apollo-language-server`, `apollo-vscode-webview`, `apollo-vscode`
+  - [#512](https://github.com/apollographql/apollo-tooling/pull/512) React UI for webviews, fix file tracking and fragment spreads ([@shadaj](https://github.com/shadaj))
+- `apollo-cli`, `apollo-language-server`, `apollo-vscode`
+  - [#508](https://github.com/apollographql/apollo-tooling/pull/508) Support jumping to definitions in schema ([@shadaj](https://github.com/shadaj))
+
+#### :house: Internal
+
+- `apollo-cli`, `apollo-language-server`
+  - [#506](https://github.com/apollographql/apollo-tooling/pull/506) Share validation logic between CLI and language server ([@shadaj](https://github.com/shadaj))
+
+#### :rocket: Feature
+
+- `apollo-language-server`, `apollo-vscode`
+  - [#504](https://github.com/apollographql/apollo-tooling/pull/504) Add Apollo VS Code extension ([@shadaj](https://github.com/shadaj))

package/LICENSE

@@ -1,6 +1,6 @@
-The MIT License (MIT)
+MIT License
 
-Copyright (c) 2016 Meteor Development Group, Inc.
+Copyright (c) 2021 Apollo GraphQL
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal

package/README.md

@@ -2,7 +2,7 @@
 
 GraphQL has the potential to create incredible developer experiences, thanks to its strongly typed schema and query language. The Apollo platform brings these possibilities to life by enhancing your editor with rich metadata from your graph API.
 
-![demo](https://raw.githubusercontent.com/apollographql/apollo-tooling/master/packages/vscode-apollo/images/marketplace/jump-to-def.gif)
+![demo](https://raw.githubusercontent.com/apollographql/vscode-graphql/main/images/marketplace/jump-to-def.gif)
 
 The Apollo GraphQL extension for VS Code brings an all-in-one tooling experience for developing apps with Apollo.
 
@@ -17,7 +17,7 @@ The Apollo GraphQL extension for VS Code brings an all-in-one tooling experience
 
 <h2 id="getting-started">Getting started</h2>
 
-Some features of this extension (like syntax highlighting) will work without any configuration, but to get all of the benefits of the VS Code experience, it's best to link the schema that is being developed against **before** installing the extension. The best way to do that is by [publishing a schema](https://www.apollographql.com/docs/platform/schema-registry.html#setup) to the Apollo schema registry. Once that is done, two steps are needed:
+Some features of this extension (like syntax highlighting) will work without any configuration, but to get all of the benefits of the VS Code experience, it's best to link the schema that is being developed against **before** installing the extension. The best way to do that is by [publishing a schema](https://www.apollographql.com/docs/graphos/delivery/) to the Apollo schema registry. Once that is done, two steps are needed:
 
 1. Create an `apollo.config.js` at the root of the project
 2. Copy an API key from the Apollo Studio dashboard of the published graph
@@ -94,7 +94,7 @@ Once you have a config set up and a schema published, **install the Apollo Graph
 
 When a file open, clicking the status bar icon will open the output window and print stats about the project associated with that file. This is helpful when confirming the project is setup properly.
 
-<img src="https://raw.githubusercontent.com/apollographql/apollo-tooling/master/packages/vscode-apollo/images/marketplace/stats.gif"  alt="Clicking the status bar icon to open the output pane">
+<img src="https://raw.githubusercontent.com/apollographql/vscode-graphql/main/images/marketplace/stats.gif"  alt="Clicking the status bar icon to open the output pane">
 
 <h2 id="features">Features</h2>
 
@@ -104,19 +104,19 @@ Apollo for VS Code brings many helpful features for working on a GraphQL project
 
 Once configured, VS Code has full knowledge of the schema clients are running operations against, including client-only schemas (for things like local state mutations). Because of this, it have the ability to autocomplete fields and arguments as you type.
 
-<img src="https://raw.githubusercontent.com/apollographql/apollo-tooling/master/packages/vscode-apollo/images/marketplace/autocomplete.gif"  alt="vscode completing a field when typing">
+<img src="https://raw.githubusercontent.com/apollographql/vscode-graphql/main/images/marketplace/autocomplete.gif"  alt="vscode completing a field when typing">
 
 <h3 id="errors-and-warnings">Inline errors and warnings</h3>
 
 VS Code can use local or published schemas to validate operations before running them. **Syntax errors**, **invalid fields or arguments**, and even **deprecated fields** instantly appear as errors or warnings right in your editor, ensuring all developers are working with the most up-to-date production schemas.
 
-<img src="https://raw.githubusercontent.com/apollographql/apollo-tooling/master/packages/vscode-apollo/images/marketplace/warnings-and-errors.gif"  alt="tooltip showing a field deprecation warning and error">
+<img src="https://raw.githubusercontent.com/apollographql/vscode-graphql/main/images/marketplace/warnings-and-errors.gif"  alt="tooltip showing a field deprecation warning and error">
 
 <h3 id="field-type-info">Inline field type information</h3>
 
 Because of GraphQL's strongly-typed schema, VS Code not only know about which fields and arguments are valid, but also what types are expected. Hover over any type in a valid GraphQL operation to see what type that field returns and whether or not it can be null.
 
-<img src="https://raw.githubusercontent.com/apollographql/apollo-tooling/master/packages/vscode-apollo/images/marketplace/type-info.png" style="max-width:800px;" alt="a tooltip showing a Boolean type for a field">
+<img src="https://raw.githubusercontent.com/apollographql/vscode-graphql/main/images/marketplace/type-info.png" style="max-width:800px;" alt="a tooltip showing a Boolean type for a field">
 
 <h3 id="performance-insights">Performance insights</h3>
 
@@ -126,7 +126,7 @@ To turn on tracing for your GraphQL server, please visit our [guide](https://www
 
 The VS Code extension will show inline performance diagnostics when connected to a service with reported metrics in Apollo Studio. As operations are typed, any fields that take longer than 1ms to respond will be annotated to the right of the field inline! This gives team members a picture of how long the operation will take as more and more fields are added to operations or fragments.
 
-<img src="https://raw.githubusercontent.com/apollographql/apollo-tooling/master/packages/vscode-apollo/images/marketplace/perf-annotation.png"  style="max-width:800px;" alt="Performance annotation next to a field">
+<img src="https://raw.githubusercontent.com/apollographql/vscode-graphql/main/images/marketplace/perf-annotation.png"  style="max-width:800px;" alt="Performance annotation next to a field">
 
 <h3 id="syntax">Syntax highlighting</h3>
 
@@ -136,7 +136,7 @@ Apollo's editor extension provides syntax highlighting for all things GraphQL, i
 
 Navigating large codebases can be difficult, but the Apollo GraphQL extension makes this easier than ever. Right-clicking on any field in operations or schemas gives you the ability to jump to (or peek at) definitions, as well as find any other references to that field in your project. Searching a project for any occurrence of a certain field is now a thing of the past!
 
-<img src="https://raw.githubusercontent.com/apollographql/apollo-tooling/master/packages/vscode-apollo/images/marketplace/jump-to-def.gif"  alt="Using jump to definition on a fragment">
+<img src="https://raw.githubusercontent.com/apollographql/vscode-graphql/main/images/marketplace/jump-to-def.gif"  alt="Using jump to definition on a fragment">
 
 <h3 id="commands">Schema tag switching</h3>
 
@@ -151,6 +151,6 @@ Other errors may be caused from an old version of a published schema. To reload
 
 Sometimes errors will show up as a notification at the bottom of your editor. Other, less critical messages may be shown in the output pane of the editor. To open the output pane and get diagnostic information about the extension and the current service loaded (if working with a client project), just click the "Apollo GraphQL" icon in the status bar at the bottom.
 
-<img src="https://raw.githubusercontent.com/apollographql/apollo-tooling/master/packages/vscode-apollo/images/marketplace/stats.gif"  alt="Clicking the status bar icon to open the output pane">
+<img src="https://raw.githubusercontent.com/apollographql/vscode-graphql/main/images/marketplace/stats.gif"  alt="Clicking the status bar icon to open the output pane">
 
 If problems persist or the error messages are unhelpful, an [issue](https://github.com/apollographql/apollo-tooling/issues) can be opened on the `apollo-tooling` repository.

package/codegen.yml

@@ -0,0 +1,12 @@
+# Would be better to get the schema from the Studio registry once it can be a public variant.
+schema: https://graphql.api.apollographql.com/api/graphql
+generates:
+  ./src/language-server/graphqlTypes.ts:
+    documents:
+      - src/**/*.ts
+      - "!src/**/__tests__**/*.ts"
+    plugins:
+      - typescript
+      - typescript-operations
+    config:
+      avoidOptionals: true