| Age | Commit message (Collapse) | Author |
|---|
|
fix link to xmllint
|
|
Check LLVM IR with llc
|
|
Implements suggestions and recommendations suggested by the first review
of the "Advance C# linter based on mcs -t:module (#952)" pull request.
- Clarifies and simplifies description of linters and options
- Added links to help file and marked the mcsc linter as to be run only
when file in buffer is saved or loaded.
- Added comments to the mcsc.vim file to clarify code
- removed type checks considered not necessary be reviewer.
- addresses findings by vader
- removed call to getcwd and cd in vim script
- handler expands file names relative to route of source tree into
absolute pathes. Fixes errors not being marked when vim is started
from subdirectory of source tree.
- implements tests for mcs.vim and mcsc.vim linter
|
|
The existing c-charp linter used the --syntax check mode of the mono mcs
compiler only. The new mcsc linter tries to compile the files located in
a directory tree located bejond the specified source directory or the
current one if no source is explicitly specified. The resulting module
target is placed in a temporary file managed by ale.
|
|
|
|
* Add Elm support for npm local installation
|
|
* Add elm-format as a new fixer
|
|
* Add a glslang linter for GLSL
|
|
* add cuda nvcc linter
|
|
* Add prettier fixer support for typescript
* Add prettier fixer support for css and scss
* Add prettier fixer support for json
* Use getbufvar() to get &filetype
|
|
* Fix an OCaml help tag in the README
|
|
|
|
|
|
This linter works by invoking the `thrift` compiler with the buffer
contents and reporting any parser and code generation issues.
The handler rolls its own output-matching loop because we have the
(unfortunate) requirement of handling error output that spans multiple
lines.
Unit tests cover both the command callback and handler, and there is
initial documentation for all of the option variables.
|
|
|
|
|
|
see and click
|
|
tools, andautomatically demand that they stay in sync
|
|
Add a pycodestyle linter
|
|
* Add clang-format fixer for C/C++
* Document clang-format options
* Refer ale-cpp-clangformat to ale-c-clangformat
|
|
Add erubis linter
|
|
This linter works largely the same as the existing `erubylint` linter,
except it works with `erubis` instead of `erb` as the driving command.
|
|
add phpcbf fixer
|
|
* Added new linter for GraphQL: GQLint
* added help-files
|
|
|
|
|
|
|
|
|
|
* Add linter for Idris
* Fix parsing warnings and column ranges in Idris linter
* Make Idris linter configurable. Fix help tag.
|
|
SwiftFormat is a tool that can be used to format Swift files. This commit adds
support for using SwiftFormat as a fixer from ALE. It looks for executables in
the Pods directory, then the Pods directory for a React Native project, then
finally falls back to the globally installed instance if neither of those were
found.
https://github.com/nicklockwood/SwiftFormat
|
|
|
|
|
|
|
|
A limited number of clang-tidy checks can be used with C, too. I pretty much
copied and refactored the C++ clang-tidy linter, and added some documentation
about C-compatible checks.
|
|
|
|
helptag generation will actually work
|
|
|
|
package system
|
|
|
|
* Add yaml swaglint linter
|
|
Add SyntaxErl linter
|
|
* Added phpstan linter for php.
|
|
These changes add [SyntaxErl][1] integration. SyntaxErl is a syntax
checker tool for Erlang.
[1]: https://github.com/ten0s/syntaxerl
|
|
* 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
|
|
* Add stack-build linter for Haskell
The stack-build linter works better than the other two linters when
you're working with an entire Haskell project. It builds the project
entirely and reports any errors.
The other two Haskell GHC linters only work on single files, which can
result in spurious errors (for example, not being able to find imports).
* Document all available Haskell linters
* Split GHC checkers into separate files
|
|
|
|
|
|
* Add prettier-standard support
* Update ale-javascript.txt
Remove a duplicated header line.
|
|
|
