Fix VSCode config and dev instructions

This commit is contained in:
Joscha 2023-08-05 23:01:29 +02:00
parent 755f23dbb9
commit 732c33d6f7
2 changed files with 4 additions and 4 deletions

View file

@ -4,7 +4,7 @@
"files.associations": { "files.associations": {
"**/templates/**/*.html": "jinja-html", "**/templates/**/*.html": "jinja-html",
}, },
"rust-analyzer.check.extraEnv": { "rust-analyzer.server.extraEnv": {
"SQLX_OFFLINE": "false", "SQLX_OFFLINE": "false",
}, },

View file

@ -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 `target/dev.db`. You will need to rerun this command whenever you change or add
a migration. a migration.
Then, if you don't use VSCode, configure your `rust-analyzer` to run Then, if you don't use VSCode, configure your `rust-analyzer` to run with the
`cargo check` with the environment variable `SQLX_OFFLINE=false` using the with the environment variable `SQLX_OFFLINE=false` using the
[`rust-analyzer.check.extraEnv` option][ra-opt]. This signals to sqlx that it [`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. should use the dev database instead of `.sqlx/`, but only in your IDE.
**Important:** Before committing any changed SQL query, you **must** run **Important:** Before committing any changed SQL query, you **must** run