From 732c33d6f75d6b0672c6c6e4fe6466987a927af8 Mon Sep 17 00:00:00 2001 From: Joscha Date: Sat, 5 Aug 2023 23:01:29 +0200 Subject: [PATCH] Fix VSCode config and dev instructions --- .vscode/settings.json | 2 +- README.md | 6 +++--- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/.vscode/settings.json b/.vscode/settings.json index bf9da13..d4a7a5c 100644 --- a/.vscode/settings.json +++ b/.vscode/settings.json @@ -4,7 +4,7 @@ "files.associations": { "**/templates/**/*.html": "jinja-html", }, - "rust-analyzer.check.extraEnv": { + "rust-analyzer.server.extraEnv": { "SQLX_OFFLINE": "false", }, diff --git a/README.md b/README.md index c48fc43..771565b 100644 --- a/README.md +++ b/README.md @@ -34,9 +34,9 @@ First, run `./meta/setup`. This creates or updates the dev database at `target/dev.db`. You will need to rerun this command whenever you change or add a migration. -Then, if you don't use VSCode, configure your `rust-analyzer` to run -`cargo check` with the environment variable `SQLX_OFFLINE=false` using the -[`rust-analyzer.check.extraEnv` option][ra-opt]. This signals to sqlx that it +Then, if you don't use VSCode, configure your `rust-analyzer` to run with the +with the environment variable `SQLX_OFFLINE=false` using the +[`rust-analyzer.server.extraEnv` option][ra-opt]. This signals to sqlx that it should use the dev database instead of `.sqlx/`, but only in your IDE. **Important:** Before committing any changed SQL query, you **must** run