feat: add support for user-defined presets via composer #389
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello!
This allows users to create and distribute custom presets through composer packages, enabling better code style sharing across projects. I also updated pint to use the new preset manifest system so there's a unified method of registering presets.
Presets are added in the composer
extra
section like so:Note
I'm aware that it's possible to pass a custom config file like
./vendor/bin/pint --config vendor/my-company/coding-style/pint.json
, however, it's much nicer to be able to simple define a custom company preset which then is referenced in all pint configsThis also adds a new
preset:list
command to show all available presets:Thanks!