Feature Summary

Add support for integrating linters into the editor to automatically detect code style violations, potential bugs, and formatting issues. Linters should provide inline feedback and be configurable per mode or project.

Motivation

Linters help maintain consistent code style, catch common mistakes early, and enforce best practices. Manual review is time-consuming and error-prone. Mode-based linter support improves code quality, reduces review overhead, and enhances developer confidence.

Proposed Design

• Detect and run appropriate linter by modes.
• Display linter warnings and errors inline with visual markers.
• Provide a panel with detailed messages and suggested fixes.
• Allow users to configure linter rules and enable/disable specific checks.
• Support project-level configurations.

Acceptance Criteria

• Linter runs automatically or on demand for supported file types.
• Issues are displayed inline and in a summary panel.
• Users can configure linter behavior per project or globally.
• Linter feedback is accurate, non-intrusive, and actionable.
• Integration does not impact editor performance.

Related Issues / Discussions

Nothing

Implementation Notes (Optional)

• Connect modes to this feature.
• Consider asynchronous execution to avoid blocking UI.
• Provide fallback for unsupported file types or missing configs.

Localization & Accessibility

• Localize linter messages and configuration UI.
• Ensure feedback is accessible via keyboard.

Community Feedback (Optional)

Nothing