Currently, pint will merge any project config with the --preset option. This was slightly unexpected and makes it difficult to quickly use one of the presents from within a project that has a custom pint.json config.
You can get around this by passing an invalid path to --config. But that's a bit hacky. I felt a --no-config option was nice and provides an explicit way to prevent pint from merging any project config.
For example, to apply the laravel preset to a set of stub files:
pint --no-config --preset laravel -- stubs
This is indeed a real world use case where a project has it's own rules configured within pint.json, but contains stub files which are formatted to the laravel preset.
Currently,
pintwill merge any project config with the--presetoption. This was slightly unexpected and makes it difficult to quickly use one of the presents from within a project that has a custompint.jsonconfig.You can get around this by passing an invalid path to
--config. But that's a bit hacky. I felt a--no-configoption was nice and provides an explicit way to preventpintfrom merging any project config.For example, to apply the
laravelpreset to a set of stub files:This is indeed a real world use case where a project has it's own rules configured within
pint.json, but contains stub files which are formatted to thelaravelpreset.