Show HN: WGSL linter with Tint parity and a full suite of LSP niceties
Made a WGSL linter for a VS Code extension with validation matching Chrome's Tint compiler. Plus navigation, rename, layout hints and other LSP niceties; in template strings too. Feedback is very welcome!
1 point
VS Code WGSL extension that validates the way Chrome does. Plus navigation, rename, layout hints and other useful stuff (in template strings too).
I was surprised none of the existing VS Code extensions provided the complete LSP experience for WGSL, with all the niceties like rename refactoring, semantic highlighting, navigation, offset/size/align hints for custom structs, etc. Plus I needed it to closely check against the Chrome's Tint compiler, so decided to make one.
Figured someone else might find it useful, so sharing it here:
- VS Code: marketplace.visualstudio.com
- GitHub: elringus/wgsl-linter
Feedback and bug reports are welcome!
2 points
Figured someone else might find it useful:
👉 VS Code: marketplace.visualstudio.com
👉 GitHub: elringus/wgsl-linter
Feedback and bug reports are welcome!
Figured someone else might find it useful:
👉 VS Code: marketplace.visualstudio.com
👉 GitHub: elringus/wgsl-linter
Feedback and bug reports are welcome!
4 views
I built a WGSL extension for VS Code that validates shaders the way Chrome does. Plus completion, navigation, rename and formatting (in template strings too)
I wasn't happy with the existing WGSL VS Code extensions, so I made my own. It closely follows Chrome's compiler (Tint) on diagnostics, provides full semantic highlighting, completion, rename refactoring, type inference, specs and layout details on hover and other useful stuff.
Figured someone else might find it useful:
- VS Code: marketplace.visualstudio.com
- GitHub: elringus/wgsl-linter
Feedback and bug reports are welcome!
13 points · 1 comment
Mentions
Show HN: WGSL linter with Tint parity and a full suite of LSP niceties Made a WGSL linter for a VS Code extension with validation matching Chrome's Tint compiler. Plus navigation, rename, layout hints and other LSP niceties; in template strings too. Feedback is very welcome!
VS Code WGSL extension that validates the way Chrome does. Plus navigation, rename, layout hints and other useful stuff (in template strings too). I was surprised none of the existing VS Code extensions provided the complete LSP experience for WGSL, with all the niceties like rename refactoring, semantic highlighting, navigation, offset/size/align hints for custom structs, etc. Plus I needed it to closely check against the Chrome's Tint compiler, so decided to make one. Figured someone else might find it useful, so sharing it here: - VS Code: marketplace.visualstudio.com - GitHub: elringus/wgsl-linter Feedback and bug reports are welcome!
Figured someone else might find it useful: 👉 VS Code: marketplace.visualstudio.com 👉 GitHub: elringus/wgsl-linter Feedback and bug reports are welcome!
Figured someone else might find it useful: 👉 VS Code: marketplace.visualstudio.com 👉 GitHub: elringus/wgsl-linter Feedback and bug reports are welcome!
I built a WGSL extension for VS Code that validates shaders the way Chrome does. Plus completion, navigation, rename and formatting (in template strings too) I wasn't happy with the existing WGSL VS Code extensions, so I made my own. It closely follows Chrome's compiler (Tint) on diagnostics, provides full semantic highlighting, completion, rename refactoring, type inference, specs and layout details on hover and other useful stuff. Figured someone else might find it useful: - VS Code: marketplace.visualstudio.com - GitHub: elringus/wgsl-linter Feedback and bug reports are welcome!