Age | Commit message (Collapse) | Author |
|
* Mimic Prettier's default parser by setting it to `babylon`
* Add tests to check default Prettier `parser`
* Set Prettier default parser based on version
* Update the comment to explain the reason for an explicit default
|
|
* Add textlint for asciidoc
* Add textlint --fix
|
|
|
|
|
|
|
|
|
|
|
|
See: https://github.com/testdouble/standard
StandardRB is to RuboCop what StandardJS is to ESLint. This commit
naively copies the RuboCop linter and fixer to point at the standardrb
executable. Any other adjustments are very minor (the only I can think
of is that standardrb takes a `--fix` option instead of
`--auto-correct`).
This raises a confusing point to me as both developer and a user: since
ale enables all linters by default, won't this run both RuboCop and
StandardRB (the results of which will almost always be in conflict with
one another)? How does ale already solve for this for the similar case
of StandardJS and ESLint?
|
|
Closes #1910
|
|
|
|
Problem: ocamlformat is configured to format files in-place and thus go
via creating a temporary file for that. Because temporary file resides
in a different directory ocamlformat can't find `.ocamlformat`
configuration files in an original location of source files.
Solution: ocamlformat since version 0.8 can read sources on stdin and
spur result on stdout. We reconfigure ocamlformat to use a simpler
interface.
|
|
|
|
|
|
|
|
fix: change google_java_format_* to java_google_java_format_*
|
|
Fix #2011 MS Windows, lint error when current drive and target file drive is different.
|
|
global variables according to doc/ale-java.txt
|
|
See #1718
|
|
|
|
|
|
* Allow the jq filters to receive custom filters.
* Update documentation.
|
|
* Add better support for Haskell stack compiler tools
This commit adds support for `stack` as the executable of a tool. This
follows a pattern that has been implemented for `bundler`'s tool chain.
* Move hlint command to linter file
* Add vader test for stack exec handling
* Update ghc-mod to support stack execution
`ghc-mod` was previously broken into 2 linters.
1. ghc_mod
2. stack_ghc_mod
This additional linter is not necessary with proper support for
executable variables and `stack exec` handling.
* Support stack exec in hfmt
* Support stack in hdevtools
|
|
* Don't add newlines when not a control statement for Python
* Add test for accidental newline fix
* Add docstring detection to avoid adding unnecessarily newlines
* Add tests for docstring detection
|
|
shfmt: Use Vim's indent config as default indent width
|
|
* Add fixer for Go modules
|
|
|
|
|
|
Add support for sqlfmt
|
|
|
|
|
|
Add support for xmllint as a fixer.
|
|
|
|
|
|
|
|
importjs fixer not reading correct executable variable name
|
|
|
|
|
|
* Add stylish-haskell as a fixer
`stylish-haskell` is a common formatting tool for the haskell toolchain.
It is not as advanced as `brittany` or `hindent`, but it is commonly
used for formatting of imports and data declarations. This adds it as a
fixer in ALE.
|
|
|
|
Split Hack out from PHP, modernize
|
|
Support fixing YAML and HTML files with prettier for files without file extensions.
|
|
fixes #1738
- Replace previous `hh_client` usage with LSP client
- Add `HHAST` linter
- Split Hack from PHP: Hack is increasingly diverging from PHP:
- Hack tools do not understand PHP
- Most PHP tools do not handle Hack code well (including vim's syntax
highightling files)
- http://github.com/hhvm/vim-hack now sets filetype to `hack`
|
|
|
|
|
|
* Added dartfmt to Fixers
* Added dartfmt specific documentation
|
|
Add tests for tidy HTML fixer
|
|
* Set `--parser` option in Prettier's fixer
* Add expected `--parser` option to tests
* Disable Prettier `--parser` detection if file extension exists
* Manually default Prettier `--parser` to "babylon"
* Add `--parser` test for TypeScript
* Add tests for Prettier `--parser`
* Add JSON5 to the suggested fixer for Prettier
|
|
* Add support for qmlfmt fixer
|
|
closes https://github.com/w0rp/ale/issues/1299
|
|
|