Skip to content
This repository has been archived by the owner on Aug 7, 2023. It is now read-only.

Fix/one spawn per project #83

Merged
merged 11 commits into from
Apr 21, 2018
1 change: 1 addition & 0 deletions .codeclimate.yml
Original file line number Diff line number Diff line change
Expand Up @@ -7,3 +7,4 @@ ratings:
- "**.js"
exclude_paths:
- node_modules/**/*
- spec/**/*
12 changes: 0 additions & 12 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -49,15 +49,3 @@ And you should see some progress, and most likely, some results. Cool! Now it's
Once you have a functioning installation of the Code Climate CLI, you're ready to see the same results within the comfort of your favorite text editor. Install the `linter` package, the `linter-codeclimate` package, and make sure any of the language modes you prefer are also installed.

Once these are installed, reload your editor (`View` -> `Reload` from the Atom menu), open a file of your choice, and save it. Code Climate analysis will run in the background and then pop up results that you can inspect right inside Atom. Awesome! You're now linting with superpowers.

## Installation: Special Considerations

Note that currently `linter-codeclimate` works only on single file analysis types, not on engines which analyze the entire codebase at once. The following engines currently work with the Atom package (this will soon be all packages - thanks for your patience as we work out some kinks):


* All Languages: fixme
* Python: Radon, Pep8
* Ruby: Rubocop
* CoffeeScript: CoffeeLint
* JavaScript: ESLint
* PHP: PHPCodeSniffer, PHPMD
Loading