chore: rename to postgrestoosl

Author: juleswritescode

.vscode/launch.json

@@ -9,7 +9,7 @@
  "--disable-extensions",
  "--extensionDevelopmentKind=node",
  "--extensionDevelopmentPath=${workspaceFolder}",
- "--log=supabase.pglt-vscode:debug",
+ "--log=supabase.postgrestools-vscode:debug",
  "${workspaceFolder}/test/fixtures/monorepo-nested-config"
  ],
  "outFiles": ["${workspaceFolder}/out/**/*.js"],
@@ -24,7 +24,7 @@
  "--disable-extensions",
  "--extensionDevelopmentKind=node",
  "--extensionDevelopmentPath=${workspaceFolder}",
- "--log=supabase.pglt-vscode:debug",
+ "--log=supabase.postgrestools-vscode:debug",
  "${workspaceFolder}/test/fixtures/node-modules-strat"
  ],
  "outFiles": ["${workspaceFolder}/out/**/*.js"],
@@ -38,7 +38,7 @@
  "--disable-extensions",
  "--extensionDevelopmentKind=node",
  "--extensionDevelopmentPath=${workspaceFolder}",
- "--log=supabase.pglt-vscode:debug",
+ "--log=supabase.postgrestools-vscode:debug",
  "${workspaceFolder}/test/fixtures/simple-project-download"
  ],
  "outFiles": ["${workspaceFolder}/out/**/*.js"],
@@ -52,7 +52,7 @@
  "--disable-extensions",
  "--extensionDevelopmentKind=node",
  "--extensionDevelopmentPath=${workspaceFolder}",
- "--log=supabase.pglt-vscode:debug",
+ "--log=supabase.postgrestools-vscode:debug",
  "${workspaceFolder}/test/fixtures/simple-project-global-bin"
  ],
  "outFiles": ["${workspaceFolder}/out/**/*.js"],
@@ -66,7 +66,7 @@
  "--disable-extensions",
  "--extensionDevelopmentKind=node",
  "--extensionDevelopmentPath=${workspaceFolder}",
- "--log=supabase.pglt-vscode:debug",
+ "--log=supabase.postgrestools-vscode:debug",
  "${workspaceFolder}/test/fixtures/workspace-with-settings"
  ],
  "outFiles": ["${workspaceFolder}/out/**/*.js"],
@@ -80,7 +80,7 @@
  "--disable-extensions",
  "--extensionDevelopmentKind=node",
  "--extensionDevelopmentPath=${workspaceFolder}",
- "--log=supabase.pglt-vscode:debug",
+ "--log=supabase.postgrestools-vscode:debug",
  "${workspaceFolder}/test/fixtures/yarn-pnp-strat"
  ],
  "outFiles": ["${workspaceFolder}/out/**/*.js"],

README.md

@@ -1,21 +1,21 @@
-# PGLT Extension for VS Code
+# PostgresTools Extension for VS Code
 
-The **PGLT extension for Visual Studio Code** brings PostgreSQL inline suggestions, linting, and type checks to VSCode and VSCode-based editors.
+The **PostgresTools extension for Visual Studio Code** brings PostgreSQL inline suggestions, linting, and type checks to VSCode and VSCode-based editors.
 
 ## Installation
 
-The PGLT extension for VS Code is not yet distributed but will soon be available via the Visual Studio Marketplace and the Open VSX Registry.
+The PostgresTools extension for VS Code is not yet distributed but will soon be available via the Visual Studio Marketplace and the Open VSX Registry.
 
 ## Architecture
 
-The VSCode extension looks for the `pglt` binary and uses it to start an LSP background process. It then creates a VSCode LSP Client and connects it to the server.
+The VSCode extension looks for the `postgrestools` binary and uses it to start an LSP background process. It then creates a VSCode LSP Client and connects it to the server.
 
 It'll try five strategies to find the binary, in the following order:
 
-1. The `pglt.bin` VSCode setting can point to a binary with relative or absolute paths.
-2. If you have installed pglt via node_modules, the extension will look for the matching binary in your `node_modules`.
-3. If you have installed pglt via Yarn Plug'n'Play, the extension will check your `.pnp.cjs` file for a binary.
-4. The extension will scan your $PATH for a `pglt` on Darwin/Linux or `pglt.exe` on Windows.
-5. If no binary will be found, you will be prompted to download a binary from `pglt`'s Github Releases. You can always download a CLI version via VSCode's Command Palette. (If you want to download prereleases, set `pglt.allowDownloadPrereleaes` in your VSCode settings.)
+1. The `postgrestools.bin` VSCode setting can point to a binary with relative or absolute paths.
+2. If you have installed postgrestools via node_modules, the extension will look for the matching binary in your `node_modules`.
+3. If you have installed postgrestools via Yarn Plug'n'Play, the extension will check your `.pnp.cjs` file for a binary.
+4. The extension will scan your $PATH for a `postgrestools` on Darwin/Linux or `postgrestools.exe` on Windows.
+5. If no binary will be found, you will be prompted to download a binary from `postgrestools`'s Github Releases. You can always download a CLI version via VSCode's Command Palette. (If you want to download prereleases, set `postgrestools.allowDownloadPrereleaes` in your VSCode settings.)
 
-To connect to your database, `pglt` needs to read a `pglt.toml` config file. By default, the extension will look for that file in your repository. You can specify an alternative path via the `pglt.configFile` VSCode setting.
+To connect to your database, `postgrestools` needs to read a `postgrestools.toml` config file. By default, the extension will look for that file in your repository. You can specify an alternative path via the `postgrestools.configFile` VSCode setting.