Activity
Stars and mentions · Last 30 days, Oct 5 – Nov 3
Top repositories
Elringus’s repositories ranked by new stars, as on trending.
Contributes to
Repositories outside Elringus’s account where Elringus opened or reviewed pull requests in the past 365 days.
Who noticed Elringus
Everyone who starred or forked Elringus’s repositories since the archive began in 2011.
Notable accounts
Ordered by the stars their own repositories have received.
Biggest fans
Accounts that starred the most of these repositories.
Breakout weeks
Each repository’s best week of new stars, with the release published around it.
Achievements
Awards earned by the repositories Elringus owns. Select an award to embed its badge.
No awards yet
Repositories earn awards by reaching the top three in a completed trending day or week.
A repository earns an award for finishing first, second or third in a completed trending day or week, ranked by new stars, new forks or pull request authors. Awards follow a repository through renames and transfers and count toward its current owner. Weeks run Monday to Sunday, UTC.
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!