A linting tool for HAML that enforces style consistency and integrates with RuboCop for static analysis.
HAML-Lint is a static analysis tool designed to keep HAML files clean, readable, and consistent. It provides HAML-specific style checks and integrates with RuboCop to bring Ruby static analysis capabilities to HAML templates, helping teams maintain code quality.
Ruby on Rails developers and teams using HAML for templating who need to enforce consistent style and catch potential issues in their view files. It's particularly useful for projects with multiple contributors where maintaining a uniform codebase is a priority.
Developers choose HAML-Lint because it offers a low-cost, automated way to enforce HAML-specific style conventions and integrates seamlessly with RuboCop for analyzing embedded Ruby code. Its auto-correction features, customizable configuration, and extensive editor integrations make it a pragmatic tool for improving code quality with minimal manual effort.
Tool for writing clean and consistent HAML
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Seamlessly leverages RuboCop for analyzing Ruby code within HAML templates, bringing comprehensive static analysis to embedded logic without separate tools.
Offers both safe and unsafe auto-correction via command-line flags (-a and -A), automatically fixing common lint violations to reduce manual cleanup.
Configurable via YAML files with options to enable/disable linters, set severity, and exclude files, plus support for writing custom linters to enforce project-specific standards.
Integrates with popular editors (Vim, VS Code, RubyMine), Git hooks via Overcommit, and Rake tasks, fitting smoothly into existing development workflows.
The auto-correction feature is labeled as experimental in the README, which may lead to unpredictable behavior or incomplete fixes in edge cases.
Requires Ruby 3+ and HAML 5+, locking out projects on older versions and potentially forcing costly upgrades before adoption.
With options for file exclusion, linter inheritance, and custom linters, initial setup can be complex and time-consuming for teams new to linting tools.