vello/.vscode/settings.json

{
  "wgsl-analyzer.customImports": {
    "config": "${workspaceFolder}/piet-wgsl/shader/shared/config.wgsl",
    "segment": "${workspaceFolder}/piet-wgsl/shader/shared/segment.wgsl",
    "pathtag": "${workspaceFolder}/piet-wgsl/shader/shared/pathtag.wgsl"
  },
  "wgsl-analyzer.diagnostics.nagaVersion": "main"
}
Use 'C style' preprocessing in piet-wgsl (#194) This lets us use https://github.com/wgsl-analyzer/wgsl-analyzer for writing the wgsl files. The imports (for wgsl-analyzer) have to be machine specific at the moment - to use this you need to configure .vscode/settings.json yourself. The alternative is to point them at static files on GitHub, which is tempting to make things easier, but would potentially go out of sync with what is actually used. 2022-10-28 01:27:46 +11:00			`{`
			`"wgsl-analyzer.customImports": {`
Prepare for wgsl-analyzer upgrades (#195) * Prepare for wgsl-analyzer upgrades * Fix the exponentials 2022-10-28 04:45:48 +11:00			`"config": "${workspaceFolder}/piet-wgsl/shader/shared/config.wgsl",`
			`"segment": "${workspaceFolder}/piet-wgsl/shader/shared/segment.wgsl",`
			`"pathtag": "${workspaceFolder}/piet-wgsl/shader/shared/pathtag.wgsl"`
Use 'C style' preprocessing in piet-wgsl (#194) This lets us use https://github.com/wgsl-analyzer/wgsl-analyzer for writing the wgsl files. The imports (for wgsl-analyzer) have to be machine specific at the moment - to use this you need to configure .vscode/settings.json yourself. The alternative is to point them at static files on GitHub, which is tempting to make things easier, but would potentially go out of sync with what is actually used. 2022-10-28 01:27:46 +11:00			`},`
			`"wgsl-analyzer.diagnostics.nagaVersion": "main"`
			`}`