| Age | Commit message (Collapse) | Author |
|---|
|
cmake-format added support for reading from/outputting to stdin/out as
of v0.3.6, released 2018-04-10 (commit 2e2aff2) [0].
Reading from stdin is preferable over reading from a temporary file
because when given a concrete file cmake-format will look for its config
file (.cmake-format.py or similar) in the parent directories of the
provided file. If the temporary file is off in a tmpdir somewhere (e.g.,
/tmp on *nix), cmake-format will almost certainly not come across the
user's intended format configuration file, making it appear that
cmake-format is ignoring the config file.
If cmake-format reads from stdin, though, it'll look for its config file
in its current working directory and its parent directories, in a
similar manner to clang-format. This has a much higher chance of running
across the intended config file.
[0]: https://github.com/cheshirekow/cmake_format/releases/tag/v0.3.6
Co-authored-by: Alex Wang <ts826848@gmail.com>
|
|
* Fix stylelint not obeying project-specific rules
* Fix tests
* Fix test
* Fix test
|
|
|
|
|
|
* v: add "v fmt" fixer.
* v: add "v" (build) linter.
* v: fix vlint complaints and add documentation.
* v: add tests.
* v: use ale#Pad().
|
|
* Add nixfmt fixer.
* Replace manual options pad with ale#Pad()
|
|
Buildifier offers a -path command line option:
> Buildifier's reformatting depends in part on the path to the file
> relative to the workspace directory. Normally buildifier deduces
> that path from the file names given, but the path can be given
> explicitly with the -path argument. This is especially useful when
> reformatting standard input, or in scripts that reformat a temporary
> copy of a file.
This lets us drop our `-type`-guessing logic.
For the moment, we rely on the buffer filename being "relative to the
workspace directory", which it generally is, but in a future change, we
should introduce logic that will locate the WORKSPACE file and adjusts
the filename relative to that directory. This could be complicated based
on the working directory in which `buildifier` is executed, so a little
more research is necessary to implement that logic correctly.
|
|
* Add support for `ptop` fixer
* add test file for ptop tests
* called wrong fixer in assertion test
* use ' %s %t' instead of ' %t %t'
|
|
|
|
|
|
Working directories are now set seperately from the commands so they
can later be swapped out when running linters over projects is
supported, and also better support filename mapping for running linters
on other machines in future.
|
|
* Add support for `erlfmt`
* Add missing entry to table of contents
* Fix warnings
* Add missing tools to supported tools
|
|
This fixer enables buildifier's formatting and "lint fix" modes.
Additional options can be provided via `bazel_buildifier_options`.
It also implements some basic logic for guessing the file's type.
buildifier itself usually does this based on the filenames provided on
the command line, but because we're piping our buffer via stdin, we need
to do this manually.
|
|
it _does_ need an additional plugin, but when it has the plugin, it
works as expected.
|
|
* Allow clangformat to use a local style file.
* Add tests.
* Fix Vint issue.
* Improve explanation of feature in documentation.
* Fix failing test.
The test was checking the wrong directory.
|
|
Fish indent
|
|
3498 change standardrb fixer to use stdin
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Enhanced Dhall fixer support
|
|
Make isort fixer recognize auto_pipenv flag
|
|
|
|
Use stdin/stdout to communicate with gofmt
|
|
|
|
|
|
|
|
feat: add autoimport fixer
|
|
Add ormolu fixer.
|
|
* Taken from phpcs. add add_php_phpcbf_options #3382
* Updated docs for php_phpcbf_options #3382
* Added tests #3382
|
|
|
|
|
|
|
|
|
|
This commit adds a fixer for the Haskell language, ormolu
(https://github.com/tweag/ormolu).
Signed-off-by: David Wood <david@davidtw.co>
|
|
|
|
|
|
|
|
|
|
|
|
Prettier does not use `.prettierignore` unless the current directory is the root where the `.prettierignore` file resides.
* Update Prettier tests
* Look for prettierignore to determine project root
|
|
https://github.com/dhall-lang/dhall-lang
|
|
|
|
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.
|
|
Fix 2816 - Standard fix does not work.
|
|
|
