Age | Commit message (Collapse) | Author |
|
|
|
* feat: prettier for astro
* feat: eslint for astro
* feat: doc for astro
|
|
|
|
The only option available to biome's `lsp-proxy` command used for
linting is `--config-path`. However, we are using ALE to find and set
the project root, and have a way to manually override, so that is no
longer necessary.
The LSP proxy also used the `g:ale_biome_options` config, which is
shared with the fixer's `check` command, but `lsp-proxy` will throw an
error if unknown options are included, making it so that option is only
useful to set the project root.
BREAKING CHANGE: We are no longer passing options to the biome LSP
proxy, but we can still set the project root with
`g:ale_biome_lsp_project_root`.
|
|
Since biome supports either `biome.json` or `biome.jsonc` config files,
we need to look for both when searching for the LSP project root. We can
also look for a package.json or .git folder to use. This uses mostly the
same logic as deno.
|
|
* Add Ruby linter with Steep
Fixes #3254
* Run steep instead of using language server
LSP presents a few issues and this works around those.
* Work around Steep path issue
See https://github.com/soutaro/steep/pull/975
* Add simple tests for steep
* Add steep to supported tools
* Pass linter
* Add a comment regarding Steep's column counting
* Make lnum an integer
* Add Steep handler test
* Fix separator for Windows
* Escape Windows path separators for substitute()
* Use ALEInfo (I) group
* Use fnameescape instead of quotes
* Skip linting for files not under steep root
* Add and pass tests covering proper steep root lookup
* Fix separator discrepancy
* Use strict operators (match case)
* Fix ordering
* Use `is#` instead of `==#`
|
|
Since Biome understands `typescriptreact` and `javascriptreact` as
languages, we can send the `filetype` to the LSP, rather than only
sending `typescript` for both `ts` and `tsx` files, or `javascript` for
`js` and `jsx` files.
fixes: #4752
|
|
- based on biome config, will format, lint, and/or sort imports
- adds variable to apply unsafe fixes, disabled by default
fixes: #4754
|
|
Detect paths containing .github as a directory for running actionlint
by default on YAML filetypes.
|
|
Change eslint cwd to follow configuration file paths.
|
|
* Update dart analysis_server command
In 2021 the dart team added a new sub-command `language-server` to
replace the original `./snapshots/analysis_server.dart.snapshot --lsp`
convention for starting the language server.
https://github.com/dart-lang/sdk/commit/c224cc2e0d4cd8fc536c21ee963a0254d18a27bb
* Add ale_dart_analysis_server_enable_language_server option
This allows users to opt-in to the new `dart language-server` command.
* Enable ale_dart_analysis_server_enable_language_server option by default
* Update doc/ale-dart.txt
Include the dart version number where the `dart language-server` command
was added.
|
|
this commit is to fix #4756 which suggests to force disable applying
fixes when linting, particularly when `fix = true` was set in project
`pyproject.toml` file.
The flag `--no-fix` was added without checking the version of `ruff` at
this moment as it seems to be available in a quite early version.
|
|
|
|
* Fix 4740 - add hurlfmt linter
* Fix 4740 - add hurlfmt fixer
* Fix wrong comments
* Add end_col to qflist
* Fix test
|
|
This commit appends `check` to the ruff executable if the version of
specified ruff executable is `>= 0.3.0`, as ruff version `0.3.0`
deprecates `ruff <path>` in favor of `ruff check <path>`:
https://github.com/astral-sh/ruff/releases/tag/v0.3.0
|
|
Checking whole packages instead of individual files is more sensible
default for golang projects. Without this we get many cryptic
`typecheck` errors in ALE that do not show when running in terminal or
CI.
|
|
* Fix 4721 - force latex language id on cspell for tex filetype
* Fix tests
|
|
* Fix '-s' to be '-S' when setting 'TabSize=1' for chktex
Fixes #4712
Closes #4725
* Check if chktex's -S option is available
* Check chktex version instead of trying -S option
|
|
* Fix 4712 - revert #4661
* Fix tests
|
|
* Revert "Add biome support for javascript (#4701)"
This reverts commit 8922478a83cd06bfe5b82eb45279649adc4ec046.
* Add support for biome
|
|
Most of the time it works to assume that the current working
directory is the root of the project. However, this is not the case
for Rebar3 checked out dependencies, for example.
It's also worth noting that because of the way Elvis handles file
patterns, and because directories in configuration are relative to the
project root, the path supplied to command must be also relative.
|
|
|
|
* Refactor erlang_ls linter tests
* Add Rebar3 _checkouts support for erlang_ls linter
* Add Erlang.mk support for erlang_ls linter
|
|
|
|
|
|
|
|
* Fix chktex highlighting wrong column when using tabs instead of spaces
Fixes #723
chktex implemented feature request [1] for allowing setting options from
the command line. Thanks to that we can tell it to treat tab character
as of one space width, i.e. one char. That means, after we translate the
output back to Vim columns, we get correct numbers.
[1]: https://savannah.nongnu.org/bugs/?56486
* Add test_tex_chktex.vader
* Use functions to set g: variables in ale_linters/tex/chktex.vim
* Update ale_linters#tex#chktex#GetCommand() to use '%e'
|
|
|
|
|
|
* Ruff use json-lines output format
* Fix Ruff: add -q to prevent non json output
Using the json-lines output format allows for setting of the end_line,
end_col and code field of the handle output.
Additionally, the first letter of the code is used to determine the type
field.
Co-authored-by: w0rp <w0rp@users.noreply.github.com>
|
|
|
|
* Close #976 - add clang-check to C linters
* Update docs
|
|
* fix --output-format option
* Add conditionally changing flag based on Ruff version
|
|
Fix solhint for versions >= 3.4.0, while still supporting older
versions.
The solhint linter code has been moved out of the `handlers` directory
as it does not need to be shared between different filetypes. Code has
been simplified.
Co-authored-by: Henrique Barcelos <16565602+hbarcelos@users.noreply.github.com>
|
|
We weren't joining and returning paths correctly for detecting project
roots for Haskell projects, and now we are.
Co-authored-by: Rodrigo Mesquita <rodrigo.m.mesquita@gmail.com>
|
|
* Remove some tests we no longer need
* Delete blocks of redundant code
* Compress some tests together to simplify them
* Remove a little code for ancient linter versions
* Escape more executables we didn't escape before
* Rename a deno option that didn't match our conventions
|
|
Default `g:ale_disable_lsp` to a new mode `'auto'` by default. With this
setting applied, ALE will now check for the presence of nvim-lspconfig
and automatically turn off particular LSP linters if already configured
via nvim-lspconfig.
For users that do not use `nvim-lspconfig`, everything should work as
before.
|
|
Packwerk (https://github.com/Shopify/packwerk) is a Ruby gem
used to enforce boundaries and modularize Rails applications.
|
|
|
|
* fix(json): update vscode json lsp name
* fix(vscodejson): fallback to previous name
Co-authored-by: w0rp <devw0rp@gmail.com>
|
|
luacheck will run with `--globals vim` automatically if the file is in
runtimepath and `--globals` hasn't already been configured.
|
|
Combine cases into smaller tests of tests and remove tests we no longer
need. Linter tests have been moved to where they should be.
|
|
* fix(yaml): make actionlint respect config
* docs: update actionlint docs
* chore: update author & add description
* test: move actionlint test to test/linter/
|
|
|
|
* feat(markdown): add marksman lsp
* docs: add marksman docs
* test(markdown): add marksman test
Co-authored-by: Peter Benjamin <peter.benjamin@peter.benjamin-FVFHP2WSQ05Q>
|
|
gometalinter has been deprecated, and was archived in 2019
|
|
* fix: volar v1 support
* fix: volar linter errors
|
|
golint has been deprecated and was archived in 2019
|
|
* Initial buildifier linter files
* Add handler test
* Fix test when options are not set
|
|
* Fix a Ruby deprecation warning in the ERB linter
Before, the ERB linter used positional arguments. Newer versions of Ruby
have deprecated this method signature. We fixed the linter to use
keyword arguments.
* fixup! Fix a Ruby deprecation warning in the ERB linter
|