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

Sublime​Linter-contrib-CFLint

by ckaznocha ST3

SublimeLinter plugin for Adobe ColdFusion, using CFLint.

Details

Installs

  • Total 801
  • Win 511
  • OS X 236
  • Linux 54
Feb 21 Feb 20 Feb 19 Feb 18 Feb 17 Feb 16 Feb 15 Feb 14 Feb 13 Feb 12 Feb 11 Feb 10 Feb 9 Feb 8 Feb 7 Feb 6 Feb 5 Feb 4 Feb 3 Feb 2 Feb 1 Jan 31 Jan 30 Jan 29 Jan 28 Jan 27 Jan 26 Jan 25 Jan 24 Jan 23 Jan 22 Jan 21 Jan 20 Jan 19 Jan 18 Jan 17 Jan 16 Jan 15 Jan 14 Jan 13 Jan 12 Jan 11 Jan 10 Jan 9 Jan 8
Windows 0 0 0 0 1 5 0 0 2 1 0 0 1 1 1 1 1 0 0 1 3 1 0 1 0 0 0 3 0 0 0 0 0 0 2 1 0 0 0 0 0 0 1 2 1
OS X 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 1 0 0 0 0 0 0 0 1 0 0 0 1 0 0 1 0 0 0 0 0 0 1 1 0 0 0 5 1 0
Linux 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0

Readme

Source
raw.​githubusercontent.​com

SublimeLinter-contrib-CFLint

Build Status

This linter plugin for SublimeLinter 3 provides an interface to CFLint. It will be used with files that have the CFML syntax.

Installation

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

Linter installation

Before using this plugin, you must ensure that CFLint and SublimeText-CFML are installed on your system.

To install CFLint, do the following:

  1. Download and install latest Java SE 8+ JRE, or JDK if you plan to build it yourself.
  2. Download latest CFLint standalone JAR (CFLint-1.2.0-all.jar or newer) from the GitHub releases or Maven repository. Alternatively, build it yourself using these instructions. This is the JAR file that will be provided to jar_file in the settings.

To install SublimeText-CFML, do the following:

  1. Follow the instructions from jcberquist/sublimetext-cfml.

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 cflint. Among the entries, you should see SublimeLinter-contrib-CFLint. If that entry is not highlighted, use the keyboard or mouse to select it.

Settings

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

Plugin-specific settings

Once you have installed both the SublimeLinter 3 and SublimeLinter-contrib-CFLint plugins you will need to edit the CFLint settings.

Preferences > Package Settings > SublimeLinter > Settings

You will see a CFLint section under the user settings (SublimeLinter.sublime-settings – User):

"linters": {
    "cflint": {
        "@disable": false,
        "args": [],
        "aux_config_dirs": [],
        "config_file_name": "cflintrc.xml",
        "excludes": [],
        "jar_file": ""
    }
},

Add the full path to your CFLint JAR file and optionally add config file information:

  • jar_file (required): This must contain the absolute path to the CFLint-*-all.jar file.
  • config_file_name (optional): This must contain just the file name for the CFLint config file. [default: .cflintrc]
  • aux_config_dirs (optional): An array of paths that will act as auxiliary directories in which to search for the config file if not found for the file being linted.

Contributing

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

  1. Fork the plugin repository.
  2. Hack on a separate topic branch created from the latest master.
  3. Commit and push the topic 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!