| Age | Commit message (Collapse) | Author |
|---|
|
* Add support for scalastyle
* Add scalastyle docs
* scalastyle support for column numbers
* off by one column
* Add tests for scalastyle command and handler
* update readme for scalastyle
* allow full scalastyle options instead of just config file
* fix indentation
* allow scalastyle config file in parent directories by a couple names.
* check for missing match args with empty
* remove echo
* use a for loop
|
|
* Move FindRailsRoot() to more general location
* Add rails_best_practices handler (resolves #655)
* Update documentation for rails_best_practices
Also add brakeman to *ale* documentation.
* rails_best_practices: allow overriding the executable
* rails_best_practices: format help correctly
* rails_best_practices: capture tool output on Windows
|
|
The real fix was not using absolute paths anymore (so not expanding with the `:p` option). The regex was correct and should at least include the `^` character to make sure the string starts with the given path/filename and not references the path/filename in some error description.
|
|
which uses RE2
|
|
Make gometalinter work again
|
|
* Look for ini file to spot project root
When looking for the project root folder it would be better
to check for some well-known init file instead of __init__.py.
Indeed, with python3 it is now possible to have namespace modules
where intermediate dirs are not required to include the __init__.py file.
* Break if statement conditions over several lines
* Add blank lines for the if block
* Add test for FindProjectRoot
* Typo: missing / for MANIFEST.in
* Fix test for non-namespace package
* Add more test cases
|
|
They changed their logic to use related paths instead of absoluut paths (see [here](https://github.com/alecthomas/gometalinter/commit/a04df08be5899be3c7ad69aa379858dcb660c709#diff-04424ed7c660c10495a54e8d11be89eaR253))
This fixes the linter by also using relative paths…
|
|
fix some missing escaping for the rubocop linter
|
|
* Use rubocop's JSON output format (resolves #339)
Rubocop's emacs formatter seems to have changed format in some
not-so-ancient version. The JSON formatter should provide a more stable
interface than parsing lines with a regex.
The JSON formatter was introduced in mid-2013, so it should be safe to
assume available in any reasonably-modern environment. The oldest
currently-supported version of ruby (according to ruby-lang.org) was
not supported by rubocop until 2014.
* Rubocop: Use global function for GetType
* Rubocop: Use scope prefix in GetType
* Rubocop: Update command_callback test
* Rubocop: add end_col to Handle
|
|
* Use different reporter to support older versions of jscs
* Add test and make more consistent with other code
* Add documentation for jscs
* Add more test coverage
|
|
most things. Clear errors when linters are removed
|
|
|
|
|
|
like the other linters
|
|
* Add puppet-lint fixer
* Add vader test for puppetlint fixer
* Ensure puppetlint variables are initialized
|
|
|
|
* add ruby fixer for `rubocop --auto-correct`
|
|
|
|
* Add `fusion-lint` for first FusionScript linter
* Add documentation over `fusion-lint`
* Add tests for `fusion-lint` command callback
|
|
* Search python fixers in virtual environment
* Add tests for python fixers
|
|
* Add xmllint linter for xml
|
|
|
|
|
|
|
|
|
|
|
|
lint_file for mypy
|
|
|
|
|
|
|
|
* Add brakeman for Ruby on Rails
|
|
on disk instead
|
|
|
|
|
|
src/main/java paths
|
|
|
|
|
