ctrl+shift+p filters: :st2 :st3 :win :osx :linux
Browse

Sublime​Linter-contrib-slim-lint

by elstgav ST3

SublimeLinter plugin for slim templates, using slim-lint

Details

Installs

  • Total 4K
  • Win 863
  • OS X 2K
  • Linux 904
Apr 23 Apr 22 Apr 21 Apr 20 Apr 19 Apr 18 Apr 17 Apr 16 Apr 15 Apr 14 Apr 13 Apr 12 Apr 11 Apr 10 Apr 9 Apr 8 Apr 7 Apr 6 Apr 5 Apr 4 Apr 3 Apr 2 Apr 1 Mar 31 Mar 30 Mar 29 Mar 28 Mar 27 Mar 26 Mar 25 Mar 24 Mar 23 Mar 22 Mar 21 Mar 20 Mar 19 Mar 18 Mar 17 Mar 16 Mar 15 Mar 14 Mar 13 Mar 12 Mar 11 Mar 10 Mar 9
Windows 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 1 0 0 0 0 2 0 1 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 1 0 1 0
OS X 0 1 0 0 0 1 3 0 0 0 1 0 0 1 1 0 1 0 4 1 2 1 0 0 0 1 0 0 0 2 0 0 0 2 0 0 0 0 0 1 1 0 2 0 0 0
Linux 0 1 0 0 1 0 0 1 0 0 0 0 0 2 1 1 0 0 1 2 0 0 1 0 0 0 0 1 0 0 0 1 0 1 0 0 0 0 0 0 0 0 0 1 0 1

Readme

Source
raw.​githubusercontent.​com

SublimeLinter-slim-lint

Release Version

This linter plugin for SublimeLinter provides an interface to slim-lint. It will be used with files that have the “Ruby Slim” syntax.

Installation

SublimeLinter 4 must be installed in order to use this plugin. If SublimeLinter 4 is not installed, please follow the instructions here.

Linter installation

Before using this plugin, you must ensure that slim-lint is installed on your system. To install slim-lint, do the following:

  1. Install Ruby.

  2. Install slim-lint by typing the following in a terminal:

    gem install slim_lint
    
  3. If you are using rvm or rbenv, ensure that they are loaded in your shell’s correct startup file. See here for more information.

Note: This plugin requires slim-lint 0.4.0 or later.

Linter configuration

In order for slim-lint to be executed by SublimeLinter, you must ensure that its path is available to SublimeLinter. Before going any further, please read and follow the steps in “Finding a linter executable” through “Validating your PATH” in the documentation.

Once you have installed and configured slim-lint, you can proceed to install the SublimeLinter-slim-lint plugin if it is not yet installed.

Plugin installation

Please use Package Control to install the linter plugin. This will ensure that the plugin will be updated when new versions are available. If you want to install from source so you can modify the source code, you probably know what you are doing so we won’t cover that here.

To install via Package Control, do the following:

  1. Within Sublime Text, bring up the Command Palette and type install. Among the commands you should see Package Control: Install Package. If that command is not highlighted, use the keyboard or mouse to select it. There will be a pause of a few seconds while Package Control fetches the list of available plugins.

  2. When the plugin list appears, type slim-lint. Among the entries you should see SublimeLinter-slim-lint. If that entry is not highlighted, use the keyboard or mouse to select it.

Settings

For general information on how SublimeLinter works with settings, please see Settings. For information on generic linter settings, please see Linter Settings.

You can configure slim-lint options in the way you would from the command line, with .slim-lint.yml files. If a .slim-lint.yml file is not found in the file hierarchy starting with the linted file, your home directory will also be searched. For more information, see the slim-lint page. Default configuration file can be found here.

To override the config file path, you would add this to the Sublime Linter User Settings:

"slimlint": {
    "args": ["--config", "path/to/.slim-lint.yml"]
}

If you are using Bundler and would like to use the locked slim_lint version, you must set use_bundle_exec to true:

"slimlint": {
    "use_bundle_exec": true
}

You can configure the rubocop config file location:

"slimlint": {
    "env": "{'SLIM_LINT_RUBOCOP_CONF': 'path/to/.rubocop.yml'}"
}

Release History

See the CHANGELOG

Contributing

If you would like to contribute enhancements or fixes, please do the following:

  1. Fork the plugin repository.
  2. Hack on a separate branch created from the latest master.
  3. Commit and push the branch.
  4. Make a pull request.
  5. Be patient. ;-)

Please note that modifications should follow these coding guidelines:

  • Indent is 4 spaces.
  • Code should pass flake8 and pep257 linters.
  • Vertical whitespace helps readability, don’t be afraid to use it.
  • Please use descriptive variable names, no abbreviations unless they are very well known.

Thank you for helping out!