| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2019-05-14 | Close #908 - Report phpcs problems as style problems | w0rp | |
| 2019-05-10 | Add phpstan autoload option | Mikko Pesari | |
| 2019-05-07 | Escape phpstan arguments, and update documentation | w0rp | |
| 2019-05-01 | Better phpstan default configuration (#2444) | Julien Deniau | |
| * Use phpstan config file as default whenever possible + report as error | |||
| 2019-04-07 | #2132 - Replace command_chain and chain_with with ale#command#Run | w0rp | |
| 2019-03-25 | Use location of `composer.json` for PHP project path too (#2391) | Shahin Sorkh | |
| * move php-langserver "test for .git dir" test-project to its own directory * search for composer.json file in php-langserver first then .git dir * add test for php-langserver composer.json | |||
| 2019-02-22 | #2132 - Replace all uses of foo_callback with foo | w0rp | |
| 2018-11-23 | php: change phpstan's --errorFormat to --error-format (#2005) | lfree | |
| * php: change phpstan's --errorFormat to --error-format * add version check to phpstan | |||
| 2018-11-01 | PHP linter: make the path to the executable configurable | Cyril Roelandt | |
| Fixes #1388 | |||
| 2018-10-19 | Update Psalm plugin to use LSP mode | Matthew Brown | |
| 2018-09-27 | Add psalm linter for PHP (#1893) | Richard Marmorstein | |
| 2018-08-18 | Added and fixed tests | matthias | |
| 2018-08-16 | Added phpcs options support as described in #257 | matthias | |
| 2018-08-02 | Simplify the code for most linters and tests with closures | w0rp | |
| 2018-08-02 | Split Hack out from PHP, modernize | Fred Emmott | |
| 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` | |||
| 2018-07-04 | Make the language option for LSP linters optional | w0rp | |
| 2018-05-27 | Fix an incorrect argument of ale#Var in ale_linters#php#phan#Handle | haginaga | |
| 2018-05-27 | Fix code style issues and refactor to use ale#Var | haginaga | |
| 2018-05-08 | Fix to follow the Google VimScript Style Guide | haginaga | |
| 2018-05-08 | Fix to follow the Google VimScript Style Guide | haginaga | |
| 2018-05-08 | Modify to be able to use phan_client without g:ale_php_phan_executable | haginaga | |
| 2018-05-08 | (close w0rp/ale#1561) Add support phan_client for php | haginaga | |
| 2018-04-27 | Close #1521 - Allow the language to be set with simple strings for LSP linters | w0rp | |
| 2018-04-09 | Close #542 - Add an option for disabling running locally installed ↵ | w0rp | |
| executables by default | |||
| 2017-12-13 | Fix PHP linter to support PHP 7.2 lint output | Stephen Rathbone | |
| 2017-11-05 | Add executable option for phpmd linter (resolves #1076) (#1078) | David Sierra DiazGranados | |
| * Add executable option for phpmd linter (resolves #1076) * Add test for phpmd executable option | |||
| 2017-10-31 | Prevent logging of errors in the php linter. | Derrick Nelson | |
| 2017-10-26 | Merge pull request #1009 from sirbrillig/add/phpcs-include-code-option | w0rp | |
| phpcs: include sniff code in message | |||
| 2017-10-26 | Include sniff code in message | Payton Swick | |
| 2017-10-24 | Add phan as a linter for php files (#1026) | Diego Oliveira | |
| Add phan for checking PHP code | |||
| 2017-10-22 | Fix the regex of phpmd | Diego Oliveira | |
| 2017-09-30 | Added g:ale_php_phpstan_configuration option | Ruslan Osmanov | |
| 2017-08-21 | Fix #864 - Use the user's configured executable for phpstan for executable() ↵ | w0rp | |
| checks | |||
| 2017-08-08 | Ban use of ==# or ==? in the codebase, and prefer is# or is? instead | w0rp | |
| 2017-08-07 | Document the PHP langserver integration | w0rp | |
| 2017-08-02 | Cover the PHP language server functions with Vader tests | w0rp | |
| 2017-08-02 | #517 Enable the PHP language server | w0rp | |
| 2017-07-30 | Fix some bugs so the PHP language server will show errors at least once | w0rp | |
| 2017-07-26 | #517 Add more code LSP support which makes the tssserver linter behave more ↵ | w0rp | |
| like the LSP linters | |||
| 2017-07-16 | Added phpstan linter for php. (#772) | Ardis | |
| * Added phpstan linter for php. | |||
| 2017-06-21 | Support project's local phpcs installation (#666) | Eric Stern | |
| * Use locally-installed PHPCS if available * Add author * Add configuration options * Escape executable * Add tests | |||
| 2017-05-17 | Add end columns on php linter #538 | Adriaan Zonnenberg | |
| 2017-05-08 | Read errors from stdout only (and make sure they are displayed) | Pawel Bogut | |
| 2017-04-18 | Add a function for getting matches, and use it to simplify a lot of code | w0rp | |
| 2017-04-16 | #427 Implement buffer variable overrides for all linter options | w0rp | |
| 2017-04-15 | Fix #257 in preparation for #427, standardise options with fallbacks, and ↵ | w0rp | |
| make it so every value can be computed dynamically | |||
| 2017-04-12 | PHP: Fix double errors and support fatal errors | Adriaan Zonnenberg | |
| 2017-03-30 | Remove 'col' from linters where it is hardcoded to 1 (#434) | Adriaan Zonnenberg | |
| * Remove 'col' from linters where it is hardcoded to 1 When 'col' is 1, the first column will get highlighted for no reason. It should be 0 (which is the default). In the scalac linter there was also a check about the outcome of `stridx`. It would set l:col to 0 if it was -1, and then it uses `'col': l:col + 1` to convert the outcome of `stridx` to the actual column number. This will make 'col' equals 1 when there is no match. We can remove the check because `-1 + 1 = 0`. * Remove outdated comments about vcol vcol was added as a default, and the loclists that follow these comments do not contain 'vcol' anymore | |||
| 2017-03-01 | Fix PHP column matching for unexpected single quotes (#370) | Adriaan Zonnenberg | |
| * PHP: Fix column matching for unexpected single quotes Unexpected single quotes resulted in an empty match, because PHP surrounds the errors with quotes, and we check for the next quote to be the ending delimiter. For example: an unexpected string 'foo' would be presented as `unexpected ''foo''`, and then the match would be `''`. The inner part of that match is an empty string. This adds a check for the keyword "expecting". Any quote after "expecting" won't be matched, so we can use greedy matching instead of non-greedy. * PHP: Use "very magic" The pattern started to get unreadable Also replaced non-greedy matching (`\{-}`) by greedy matching, because we don't need to match non-greedily anymore and it reads a little nicer. * PHP: Add tests for column matches And with that, also a test for unexpected single quotes. | |||
| 2017-02-26 | Copy all loclist items returned from handlers, and set up defaults for ↵ | w0rp | |
| convenience | |||
 |
index : ale | |
| Check syntax in Vim asynchronously and fix files, with Language Server Protocol (LSP) support | cos |
| summaryrefslogtreecommitdiff |