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 textDocument/typeDefinition for LSP
Doc to spec https://microsoft.github.io/language-server-protocol/specification#textDocument_typeDefinition
This works like textDocument/definition but resolves a location of a
type of an expression under the cursor.
I'm not sure what to do with tsserver though.
* Fix passing column to LSP
* test_go_to_definition: wording
* Add tests for textDocument/typeDefinition
* Add docs for textDocument/typeDefinition
|
|
Adjust column to be 0-based for LSP messages
|
|
|
|
End position in LSP range is exclusive
|
|
|
|
|
|
This is what LSP specifies.
|
|
Add support for pyls configuration options
|
|
Resolves #1443.
Heavily inspired by the analogous support added for elixir-ls.
|
|
From LSP spec:
> A range in a text document expressed as (zero-based) start and end
> positions. A range is comparable to a selection in an editor. Therefore
> the end position is exclusive.
|
|
Fixed typo
|
|
|
|
|
|
|
|
|
|
* Support textlint for reStructuredText
* Add linter test for textlint rst
|
|
|
|
|
|
command
|
|
bugfix: c.vim: Pull build directory from compilation database
|
|
* Add textlint for asciidoc
* Add textlint --fix
|
|
Fix cflags parsing
|
|
|
|
|
|
The LLVM compiler database JSON already includes a directory where the
build was performed:
https://clang.llvm.org/docs/JSONCompilationDatabase.html
Prefer this directory for fixing relative paths in compiler include
arguments in ale#c#ParseCFlags.
Without this change, users cannot create a symlink to their compilation
database as suggested in the LLVM tooling setup instructions:
https://clang.llvm.org/docs/HowToSetupToolingForLLVM.html
|
|
|
|
Manually trigger autocomplete even when prefix is ""
|
|
|
|
|
|
Improve perf for compile dbs in large projects
|
|
* Add ability to manually trigger completion menu
* Mention :ALEComplete in completion docs
* Add test for ALEComplete
|
|
When using a compilation database (compile_commands.json) in very large
projects, significant delays would occur when changing files --
particularly those that happened to be far down the db. Rather than
iterating over the whole list every time, we now build up a lookup table
based on the tail of the filename (and tail of the directory for
widening searches) and iterate over the much smaller list of compile
commands for files with the given name.
Test metrics (from compile_database_perf/test.sh) show a 90% performance
improvement -- from 25 seconds to 2.5 seconds per run.
|
|
* Add support for https://github.com/saibing/bingo
* Add docs for ale-go-bingo
* Use go.mod when found
* Add test for bingo FindProjectRoot
* Simplify ale_linters#go#bingo#GetCommand
|
|
|
|
support tests/ with elm 0.19.0
|
|
|
|
windows paths have backslashes, which are special in regex patterns
|
|
With earlier elm versions, a separate package file is maintained for
tests, which when properly configured enabled the compiler to find what
it needed to compile the tests. Under elm 0.19, test dependencies are
managed in the top-level package file, so `elm make` will fail on the
tests. `elm-test make` is required in this case.
See https://github.com/elm-explorations/test/issues/64
|
|
most projects will have an elm.json file (>= 0.19) or elm-package.json (< 0.19)
|
|
|
|
Add support for ale option to override default shell used by ale
|
|
Fix CFLAGS & Makefile issues
|
|
|
|
Add support for black usage with pipenv
|
|
|
|
Add associated line text on ALEFindReferences results for TypeScript
|
|
|
|
|