coding-standard
ale
coding-standard | ale | |
---|---|---|
9 | 133 | |
1,358 | 13,288 | |
0.9% | 0.4% | |
8.2 | 8.7 | |
2 months ago | 7 days ago | |
PHP | Vim Script | |
MIT License | BSD 2-clause "Simplified" License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
coding-standard
-
Laravel code-quality tools
If you go through the imports in the config/insights.php file, you'll see that it mostly uses rules from NunoMaduro\PhpInsights and SlevomatCodingStandard\Sniffs. The former is PHP Insight's in-house insights and the latter is the sniffs from the Slevomat coding standard. In most cases, you'll only ever reach for those two.
-
Does CodeSniffer/ECS have the possibility to detect large methods/functions?
However, you can get cognitive complexity in phpcs with the slevomat ruleset. This ruleset is used as a base for the Doctrine coding standard.
-
Searching expecific rules for php-cs-fixer
I think you can use the Slevomat Coding Standards to solve both issues.
-
Tools you’ve used to increase code quality and/or productivity?
I also make heavy use of Codesniffer with PSR12 as a base and a load of the rules from https://github.com/slevomat/coding-standard - learning how to use Codesniffer and setting up a comprehensive coding standard can be incredibly helpful when working as part of a team.
-
Recommendations for productivity tools/libraries?
You should check out https://github.com/slevomat/coding-standard for some very useful additional rules.
-
Strict operators on known return values
no need for muscle memory, there's a phpcs rule for that 🙂
-
How do you enforce a consistent code style in your projects?
Codesniffer. Though the requirements may differ between projects I typically use PSR12 as a starting point, plus disallowing long array syntax, enforcing a need for DocBlocks, and a few others. I find https://github.com/slevomat/coding-standard is also a good source of useful sniffs.
-
Why "on" == 0 evaluates to true?
Well, as we have this phpcs rule in our coding standard, it is forbidden (for us) 😉 Maybe, forbidden is not a good word, though.
ale
-
A decent VS Code and Ruby on Rails setup
I saw no mention of RBS+Steep, the latter providing a LSP. I use it a lot and very much like it, although it's still young and needs love, but it's making good, steady progress! I've been very pleasantly surprised by some of the crazy things Steep can catch, completely statically!
You appear to be working on projects with Sorbet (which I tried to like but found it fell short in practice, notably outside of the app use case i.e it's mostly useless for gems) so it may be a tall order to try on those. Maybe you can give RBS+Steep a shot on some small project?
RBS: https://github.com/ruby/rbs
RBS collection (for those gems that don't ship RBS signatures in `sig`, integrates with bundler): https://github.com/ruby/gem_rbs_collection
Steep: https://github.com/soutaro/steep
VS Code: https://github.com/soutaro/steep-vscode
Sublime Text: https://github.com/sublimelsp/LSP
Vim (I'm working on it): https://github.com/dense-analysis/ale/pull/4671
-
Laravel code-quality tools
Support for code quality tools are provided by the ALE plugin. These are supported for PHP:
-
Embracing Common Lisp in the Modern World
I mostly agree, though I find Allegro and LispWorks severely lacking in areas too. The companies themselves don't seem to care much about their IDEs. Certainly not in the way JetBrains cares about IntelliJ.
Tucked away in the McCLIM project is Clouseau, which you can quickload and use as a normal user: https://codeberg.org/McCLIM/McCLIM/src/branch/master/Apps/Cl... One small cool thing it does is if you inspect a complex number it will also draw a little x-y vector. (Though trying it out again just now it's overlapping with the text... maybe I should file a bug, but I've only now just learned they moved off github, and I'm not going to make a codeberg account. Friction wins this round.) It does take a while to first compile and load all the dependencies, especially 3bz, another weakness of at least our free Lisps; AFAIK there's still no equivalent of make -j for compiling systems.
I'm a happy vim user (though there is some jank with slimv, admittedly, but it's mostly prevalent around multiple thread situations) and setup the command ,ci to call my own clouseau-inspect function; it just inspects a symbol with clouseau instead of slimv's inspector. Also have a janky watch/unwatch pair of functions that just refreshes the inspector every second. (https://github.com/Jach/dots/blob/master/.sbclrc#L113 if curious, some other junk in .swank.lisp and .vimrc too, and there's https://github.com/dense-analysis/ale/issues/4061 to call sblint on your project...)
But better forms of these sorts of graphical tools are what I hope to one day see more of and are how the free Lisps can close the gap in this area with the commercial Lisps. I believe there's not much Allegro can do that poking around SBCL can't do, but for many things it's just nicer to have a GUI. Want to explore all the symbols and values in a package? Easy enough to script that, but not as nice as just having a table of symbols, and even nicer if you can set watches on some of them. None of the tools need to be tightly integrated with a single IDE either, because all the stuff necessary to debug Lisp is in the running Lisp itself. It's just that the GUI situation continues to suck.
LSP has gotten more popular with other languages and editors, sometimes I wonder if the acronym was made as an inside joke because it's basically how Lisp + Slime/Swank have worked...
-
A Humble Request for Assistance Maintaining ALE
Hello Everyone! w0rp here. I thought I'd ask on Reddit if there's anyone out there would like to help maintain ALE. It would be nice to have another willing volunteer who is up for providing relevant feedback on PRs, answering common questions, merging good PRs, and managing GitHub issues. I'll mention to anyone interested that I have a general policy of never closing issues, no matter how old, unless they are actually either solved or invalid. I bear no compulsions to ensure an that a number of issues, which is arbitrary, remains low. I have a relatively simple vetting process, which mostly just requires building trust over time.
-
Static Analysis Tools for C
A similarly useful list is vim's famous ALE plug-in's list of supported linters:
* https://github.com/dense-analysis/ale/blob/master/supported-...
While less comprehensive¹, this is my go-to list when I start working with a new language. Just brew/yum/apt installing the tool makes it work in the editor²
¹this list mostly has foss,static analyzers, however anyone can contribute (mine was the gawk linting)
²alright,there are some. Tools that might need some setup
-
Tell HN: Vim Has Autocomplete
Ctrl-X Ctrl-L is line based completion, see :help CTRL-X_CTRL-L for details.
:help ins-completion gets the useful docs, Vim's own docs are very good and worth spending some time learning how to use, so you can learn Vim itself better.
Another favorite of mine is 'gf' to open the filename under the cursor, very useful combined with ^X ^F.
Omni completion is also useful: https://vim.fandom.com/wiki/Omni_completion although you're better off with plugin that uses LSP now, for example https://github.com/dense-analysis/ale
-
LazyVim
FWIW, I still use regular vim with ale [0] and it does everything I want. It formats files with Black and isort, shows ruff and pyright errors, supports jumping to definitions, and has variable information available on hover. I have collected my config over the past several years, but I pretty rarely encounter errors with it.
[0]: https://github.com/dense-analysis/ale [1] https://github.com/CGamesPlay/dotfiles/blob/master/files/.co...
-
How to configure vim like an IDE
At some of those syntax things neovim behaves better, and like. But there is https://github.com/dense-analysis/ale.
-
Vim users who work without any plugins, how does your vimrc look like?
I replace ALE with :!, like :! %. If the linter output is compatible with default errorformat , then I do :! % > /tmp/linter.txt then :cgetfile (or in one-go: :cgetexpr systemlist(''))
-
Per project settings for linters used by ALE, how to do it the right way?
I'm not doing much of anything in Python, but according to :help ale-python-pylint:
What are some alternatives?
laravel-code-style - Automatic code formatting for Laravel projects
vim-lsp - async language server protocol plugin for vim and neovim
phpcs-laravel - The PHP_Codesniffer configuration I use across Laravel projects
coc.nvim - Nodejs extension host for vim & neovim, load extensions like VSCode and host language servers.
VIP-Coding-Standards - PHP_CodeSniffer ruleset to enforce WordPress VIP coding standards.
YouCompleteMe - A code-completion engine for Vim
GrumPHP - A PHP code-quality tool
nvim-lspconfig - Quickstart configs for Nvim LSP
easy-coding-standard - The Easiest way to add coding standard to your PHP project
syntastic - Syntax checking hacks for vim
PHP-CS-Fixer - A tool to automatically fix PHP Coding Standards issues [Moved to: https://github.com/PHP-CS-Fixer/PHP-CS-Fixer]
nvim-lint - An asynchronous linter plugin for Neovim complementary to the built-in Language Server Protocol support.