Since I no longer use Sublime Text, this package is available to a new maintaner!

SublimeLinter-contrib-elm-make

This linter plugin for SublimeLinter provides linting functionality for the Elm language.

It will be used with files that have the elm syntax package, which can be installed from here.

Installation

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

Required Tools

1. Elm version 0.15.1 must be installed, and the default elm-make command must be in your path.

2. You must ensure that the Elm language Sublime package is installed.

That's it! No other installation is required, as this linter uses the built-in error reporting of the elm compiler itself.

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

Settings

For information on linter settings, please see Linter Settings.

SublimeLinter-contrib-elm-make does not have any special settings.

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!