pint VS phplint

Laravel has Laravel Pint package installed which is just a wrapper around PHP-CS-Fixer. Create pint.json in your project root.

My biggest challenge while coding Sudorealm was dealing with code inconsistencies between features, caused by the long breaks I took between development sessions. I know you can relate to this! This is where laravel/pint 🍺 comes to play.

require("conform").setup({ formatters_by_ft = { -- Laravel's Formatter -- See: https://github.com/laravel/pint php = { "pint" }, } })

I've been using pint for formatting php files with null-ls.nvim. Few days ago null-ls.nvim has announced that the plugin will be archived in few months so I started migrating all my formatters and linter from null-ls to efm-langserver. I got other things such as prettier, black, isort, mypy, etc. working but can't get pint to work with php files: If I run pint via efm-langserver, everything is deleted from the buffer, and the saved file is formatted separately. How do I setup efm-langserver correctly to work with pint? Below is my config.yml for pint currently. yaml tools: pint: &pint format-command: "pint --no-interaction --quiet ${INPUT}" format-stdin: false languages: php: - <<: *pint Thank you.

Well, the rules are defined here: https://github.com/laravel/pint/blob/main/resources/presets/laravel.php

Be sure to check out the Pint documentation at https://github.com/laravel/pint. We hope you enjoy this new package. At Laravel, we're committed to providing you with the most robust and developer-friendly PHP experience in the world. Enjoy!

Laravel Pint is an opinionated PHP code style fixer for minimalists. Pint is built on top of PHP-CS-Fixer and makes it simple to ensure that your code style stays clean and consistent. Pint is a new addition to the Laravel framework.

For details vist https://github.com/laravel/pint

Static Analysis Tools - there are a number of tools that help you to manage code style (PHPCS, PHP-CSFixer, and a new one, Laravel Pint), as well as tools to analyse the "correctness" of your code (Psalm, PHPstan, in particular LaraStan).

build: runs PHPLint on the source code and copies the source code and the dependencies in the tmp\out\bin folder. If I had to do it today I would probably isolate the first action in an analyze target. The second action would do well in the package target. My own consistency evolves over time…