SublimeLinter 3 plugin for Puppet, using yaml-lint.
- Total 2K
- Win 516
- OS X 1K
- Linux 503
|Jun 18||Jun 17||Jun 16||Jun 15||Jun 14||Jun 13||Jun 12||Jun 11||Jun 10||Jun 9||Jun 8||Jun 7||Jun 6||Jun 5||Jun 4||Jun 3||Jun 2||Jun 1||May 31||May 30||May 29||May 28||May 27||May 26||May 25||May 24||May 23||May 22||May 21||May 20||May 19||May 18||May 17||May 16||May 15||May 14||May 13||May 12||May 11||May 10||May 9||May 8||May 7||May 6||May 5||May 4|
SublimeLinter 3 must be installed in order to use this plugin. If SublimeLinter 3 is not installed, please follow the instructions here.
Before using this plugin, you must ensure that
yaml-lint >= 0.0.9 is installed on your system. To install
yaml-lint, do the following:
yaml-lintby typing the following in a terminal:
[sudo] gem install yaml-lint
In order for
yaml-lint to be executed by SublimeLinter, you must ensure that its path is available to SublimeLinter.
Once you have installed
yaml-lint, you can proceed to install the SublimeLinter-contrib-yaml-lint plugin if it is not yet installed.
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:
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.
When the plugin list appears, type
yaml-lint. Among the entries you should see
SublimeLinter-contrib-yaml-lint. If that entry is not highlighted, use the keyboard or mouse to select it.
If you would like to contribute enhancements or fixes, please do the following:
- Fork the plugin repository.
- Hack on a separate topic branch created from the latest
- Commit and push the topic branch.
- Make a pull request.
- Be patient ;-)
Please note that modications should follow these coding guidelines:
- Indent is tab.
- Code should pass flake8 and pep257 linters.
- Vertical whitespace helps readability, don’t be afraid to use it.
- Please use descriptive variable names, no abbrevations unless they are very well known.
Thank you for helping out!