Liquid-Lint

liquid-lint is a tool to help keep your Liquid files clean and readable. In addition to style and lint checks, it integrates with RuboCop to bring its powerful static analysis tools to your Liquid templates.

You can run liquid-lint manually from the command line, or integrate it into your SCM hooks.

• Requirements
• Installation
• Usage
• Configuration
• Linters
• Editor Integration
• Git Integration
• Rake Integration
• Documentation
• Contributing
• Changelog
• License

• Ruby 2.4+
• Liquid 3.0+

gem install liquid_lint, github: 'zeusintuivo/liquid-lint'

Run liquid-lint from the command line by passing in a directory (or multiple directories) to recursively scan:

liquid-lint app/views/

You can also specify a list of files explicitly:

liquid-lint app/**/*.liquid

liquid-lint will output any problems with your Liquid, including the offending filename and line number.

liquid-lint will automatically recognize and load any file with the name .liquid-lint.yml as a configuration file. It loads the configuration based on the directory liquid-lint is being run from, ascending until a configuration file is found. Any configuration loaded is automatically merged with the default configuration (see config/default.yml).

Here's an example configuration file:

exclude:
  - 'exclude/files/in/this/directory/from/all/linters/**/*.liquid'

linters:
  EmptyControlStatement:
    exclude:
      - 'app/views/directory_of_files_to_exclude/**/*.liquid'
      - 'specific/file/to/exclude.liquid'

  LineLength:
    include: 'specific/directory/to/include/**/*.liquid'
    max: 100

  RedundantDiv:
    enabled: false

All linters have an enabled option which can be true or false, which controls whether the linter is run, along with linter-specific options. The defaults are defined in config/default.yml.

The exclude global configuration option allows you to specify a list of files or glob patterns to exclude from all linters. This is useful for ignoring third-party code that you don't maintain or care to lint. You can specify a single string or a list of strings for this option.

Some static blog generators such as Jekyll include leading frontmatter to the template for their own tracking purposes. liquid-lint allows you to ignore these headers by specifying the skip_frontmatter option in your .liquid-lint.yml configuration:

skip_frontmatter: true

To disable a liquid-lint linter, you can use a liquid comment:

/ liquid-lint:disable TagCase
IMG src="images/cat.gif"
/ liquid-lint:enable TagCase

To disable Rubocop cop, you can use a coment control statement:

- # rubocop:disable Rails/OutputSafety
p = raw(@blog.content)
- # rubocop:enable Rails/OutputSafety

You can find detailed documentation on all supported linters by following the link below:

Install the Sublime liquid-lint plugin.

If you use Flycheck, support for liquid-lint is included as of version 20160718.215 installed from MELPA.

Install the linter-liquid-lint plugin by running apm install linter-liquid-lint.

Install the VS Code liquid-lint plugin.

If you'd like to integrate liquid-lint into your Git workflow, check out overcommit, a powerful and flexible Git hook manager.

To execute liquid-lint via a Rake task, make sure you have rake included in your gem path (e.g. via Gemfile), and add the following to your Rakefile:

require 'liquid_lint/rake_task'

LiquidLint::RakeTask.new

By default, when you execute rake liquid_lint, the above configuration is equivalent to running liquid-lint ., which will lint all .liquid files in the current directory and its descendants.

You can customize your task by writing:

require 'liquid_lint/rake_task'

LiquidLint::RakeTask.new do |t|
  t.config = 'custom/config.yml'
  t.files = ['app/views', 'custom/*.liquid']
  t.quiet = true # Don't display output from liquid-lint to STDOUT
end

You can also use this custom configuration with a set of files specified via the command line:

# Single quotes prevent shell glob expansion
rake 'liquid_lint[app/views, custom/*.liquid]'

Files specified in this manner take precedence over the task's files attribute.

Code documentation is generated with YARD and hosted by RubyDoc.info.

We love getting feedback with or without pull requests. If you do add a new feature, please add tests so that we can avoid breaking it in the future.

Speaking of tests, we use rspec, which can be run by executing the following from the root directory of the repository:

bundle exec rspec

If you're interested in seeing the changes and bug fixes between each version of liquid-lint, read the Liquid-Lint Changelog.

This project is released under the MIT license.