Real-time validation for mtlog message templates in Go code.
Features
🔍 Real-time diagnostics - See template errors as you type
🎯 Precise error locations - Jump directly to problematic code
📊 Severity levels - Errors, warnings, and suggestions
⚡ Quick fixes - Automatic fixes for common issues
⚙️ Configurable - Customize analyzer path and flags
What it catches
// ❌ Error: Template has 2 properties but 1 argument
logger.Information("User {UserId} logged in from {IP}", userId)
// ^^^^^^ Quick fix: Add 1 missing argument
// ⚠️ Warning: Using @ prefix with basic type
logger.Debug("Count is {@Count}", 42)
// 💡 Suggestion: Property name should be PascalCase
logger.Information("User {userId} completed action", "user123")
// ^^^^^^ Quick fix: Change to 'UserId'
Quick Fixes
The extension provides automatic fixes for common issues:
PascalCase property names - Converts userId to UserId, user_id to UserId, etc.
Argument mismatches - Adds placeholder arguments for missing properties or removes excess arguments
Apply fixes by clicking the light bulb (💡) or pressing Ctrl+. (Windows/Linux) or Cmd+. (macOS) when your cursor is on the diagnostic.
The extension runs mtlog-analyzer when you save Go files, parsing the output and displaying diagnostics directly in the editor. It's designed to work alongside gopls without interference.
Troubleshooting
"mtlog-analyzer not found"
Ensure mtlog-analyzer is installed: go install github.com/willibrandon/mtlog/cmd/mtlog-analyzer@latest
Add Go bin directory to PATH: export PATH=$PATH:$(go env GOPATH)/bin
Or specify full path in settings: "mtlog.analyzerPath": "/full/path/to/mtlog-analyzer"
No diagnostics appearing
Check Output panel (View → Output → mtlog-analyzer) for errors
Verify the analyzer works: mtlog-analyzer your-file.go
Ensure you're saving the file (analysis runs on save)
