This replaces the original proof-of-concept backend that simply used the code from Microsoft's [vscode extension](https://github.com/microsoft/vscode-lsif-extension/tree/master/server). This held all LSIF dumps in memory, which was an untenable solution at scale.
The new server uses SQLite databases to store LSIF data for a repository and commit pair.
It is much easier to configure, just requiring a single `.graphqlconfig` file (also added in this commit). This gives us go-to-definition in the `schema.graphql` file.
The VS Code extension is https://github.com/prisma/vscode-graphql.
* dev env: launch prometheus if desired
* remove network
* pair up prometheus with grafana
* declare new files in code owners
* prettier
* sh comment cleanup
- Add CHANGELOG entry mentioning compatibility with the Bitbucket Server plugin.
- Edit Bitbucket Server integration, external service docs.
- Edit `corsOrigin` schema.
- Edit browser extension pull request template to add Bitbucket Server integration to test plan.
TSLint is being deprecated in favor of ESLint (https://github.com/palantir/tslint/issues/4534). We are not yet ready to fully migrate to ESLint because we rely on some TSLint-specific rules, but there is one set of particularly valuable ESLint-only rules: https://www.npmjs.com/package/eslint-plugin-react-hooks.
This introduces ESLint to our codebase and uses it only for those rules, to avoid duplication with TSLint.
GitHub doesn't suppor the front matter for PR templates,
only the `?template=` parameter. The front matter was added to the body, which is undesirable.
* github: update PR template to require testing + make changelog notice more prominent
Fixes#2312
I have intentionally made this short and concise. The point is to make both the author and reviewer think about updating the changelog and verifying the change is well tested, but not to be over-prescriptive.
* Update pull_request_template.md
* Update pull_request_template.md
We discovered that the migration library does not use transactions, nor has it
ever used transactions. The only place it uses transactions is for SetVersion,
not the actual migrations. The [README][1] for the postgres driver encourages
the use of transactions for multi-statement migrations. We believe it is better
to just always use transactions.
We added a template for the created migrations. It uses a transaction and it includes comments with advice from the README.
[1]: https://sourcegraph.com/github.com/golang-migrate/migrate@v4.2.5/-/blob/database/postgres/README.md?view=code#L26
* feat: remove synthesized extensions for site config langservers entries
The `sourcegraph-langserver-http` repository's Sourcegraph extension was previously used as the extension for all language servers present in the site configuration `langservers` property. This commit makes it so that Sourcegraph no longer synthesizes extensions for these languages.
* feat: remove lsp-proxy, xlang-*, indexer, builtin code intelligence
This commit makes it so language servers, cross-repository refs/defs/deps/packages search, and all other code intelligence features are provided by extensions only.
BREAKING CHANGE
NOCHANGELOG
* remove lsp-proxy from vscode launch.json
* move code related to godoc links to go_symbol_url.go
