DetachHead

from my understanding `$schema` is [only meant to be used in json schemas](https://json-schema.org/understanding-json-schema/reference/schema#schema) to specify which dialect of JSON Schema the schema was written for, not json files that are...

hmm looks like this is a vscode-specific feature: > Note that this syntax is VS Code-specific and not part of the [JSON Schema specification](https://json-schema.org/specification). Adding the `$schema` key changes the...

Or just ban accessing private members outside of the instance like I suggested in https://github.com/DetachHead/basedpyright/issues/698#issuecomment-3345263658, because the fact that you can even do this at all is really stupid

i found a workaround that *kind of* works: ```json { "jest.jestCommandLine": "\"./pw\" uv run npm run jest --" } ``` but it crashes on both windows and linux when running...

actually i can't seem to get this to work on linux at all. i think instead i need an option to specify the node executable

thanks, i was eventually able to get it working using a debug config like that, a `.bat` script for windows and a bash script for linux: ### `.vscode/jest.bat`: ```cmd @echo...

> how often would do you annotate function variables with `Final`? At least from my experience, this isn't something I normally do. To be honest I rarely used it either...

just cleanliness

hmm that doesn't seem to work: ```jsonc { "rust-analyzer.server.extraEnv": { // also tried ".venv/bin/cargo" as well as the full non-relative path "CARGO": "${workspaceFolder}/.venv/bin/cargo" } } ``` i also tried setting...

ideally i want to keep all the config isolated to the vscode project without having to change any environment variables globally. i did try modifying the path from within the...