Age | Commit message (Collapse) | Author |
|
|
|
ALE now just modifies every open buffer for rename and actions, and sets
up a one-time use BufEnter event to reload buffers that are changed so
you don't have to think about what to do with changed buffers.
|
|
|
|
feat: add intelephense support for php
|
|
Fix wording in Rust doc
|
|
|
|
Add Elvis handler for Erlang
|
|
Code actions and ALERename now appear in the right click context menu
for GVim by default.
|
|
|
|
* Added tsserver and LSP code action support.
* tsserver refactors support added.
* Handling special case when new text is added after new line symbol.
* ale#code_action#ApplyChanges simplified.
* Initial attempt on LSP Code Actions.
* workspace/executeCommand added.
* Some null checks added.
* Add last column to LSP Code Action message.
* Pass diagnostics to LSP code action.
Previously ApplyChanges code was applied from top-to-bottom that required
extra parameters to track progress and there was bug. I have changed code
to bottom-to-top approach as that does not require those extra parameters
and solved the bug.
Tested with typescript-language-server and it is working.
|
|
|
|
:ALERename! now ignores errors for files that cannot be modified, and
modifies all other files.
|
|
|
|
|
|
|
|
|
|
Newer versions of pylint will now check your code as you type. Older
versions will still only check the file on disk.
Co-authored-by: Oliver Wiegers <oliver.wiegers@gmail.com>
|
|
Add an `ALECompletePost` event along with everything needed to make it
useful for its primary purpose: fixing code after inserting completions.
* `ALEFix` can now be called with a bang (`!`) to suppress errors.
* A new `ALELintStop` command lets you stop linting, and start it later.
|
|
|
|
A new command, `:ALEImport`, has been added, which lets you import words
at your cursor if a completion provider can provide a completion for
that word which includes some additional text changes.
|
|
[Elvis][1] is an Erlang style reviewer.
[1]: https://github.com/inaka/elvis
|
|
Alias ember-template-lint to embertemplatelint so users can use either
string to enable the linter.
|
|
Option `per-file-ignores` was introduced in flake8 version 3.7.0.
It allows to ignore specific errors in specific files using glob syntax.
For example `per-file-ignores = src/generated/*.py:F401` will
ignore `F401` error in all python files in `src/generated`.
Thus ale has to run flake8 from project root where .flake8 config
is placed otherwise glob won't match linted file.
|
|
|
|
|
|
|
|
|
|
|
|
`lint_file` can now be computed dynamically with a callback function,
which can return a deferred result, as per `ale#command#Run`. This
allows linters to dynamically switch between checking files on disk,
or checking code on the fly.
Some tests have been fixed on Windows.
|
|
|
|
|
|
|
|
|
|
Add dhall-format as a Fixer
|
|
|
|
|
|
https://github.com/dhall-lang/dhall-lang
|
|
|
|
ALE now supports mapping files between different systems for running
linters and fixers with Docker, in virtual machines, in servers, etc.
|
|
Users can easily be confused when they set some options for a C or C++
compiler, and another compiler is run with different options, which
still reports errors. To remedy this, the existing `gcc` and `clang`
linters have been replaced with a `cc` linter that will run either
compiler.
This is a breaking change for ALE v3.0.0.
|
|
Enable languagetool for asciidoctor files.
|
|
|
|
Add Apple's swift-format as a linter
|
|
allow passing custom options to markdownlint
|
|
This can avoid having to wait for ALE or ALE being blocked on other
cargo actions within the same crate.
|
|
Alias ps1 filetype to powershell
|
|
|
|
* Restore old behavior of ALEFix command for Rubocop
Since RuboCop 0.60 ALEFix command stopped to fix all found offenses. This change restores the
previous behavior by allowing rubocop to fix all detected offenses.
* Fix tests
* Allow to configure auto-correct option for Rubocop
|
|
|
|
The options for parsing `make -n` and `compile_commands.json` flags
are now enabled by default, so people can start getting better flags
for their files by default.
`compile_commands.json` flags are now preferred over `make -n` results,
to make the options work better by default.
|