Use relevant .prettierrc from each project

[snoblenet]

If I had control over the formatting settings on all the projects I work on, I'd give them all the same settings and copy those settings to the prettier section in dprint.json.

(Or even just use dprint's native formatting.)

However, I don't.

How can I ensure that dprint-plugin-prettier always uses the specific .prettierrc file that is relevant to whatever file that it is formatting at the time?

[adambullmer]

100% would love to see support for prettier's internal config loading system. But shy of implementing all the various loaders, being able to specify a config file path would also be a win. We have shared settings for prettier, and copy+paste the config in every repo rather than a reference to the shared config would be a step backwards for the config reuse.

[sschneider-ihre-pvs]

done the same. would be great if there would be a relative path option or so or something like, the neareast prettier config relative to the file that is going to be formatted.

[basaran]

This would be nice feature indeed, and can be used as a stepping stone to migrate away from local project installation of prettier, especially when there is now an NPM package for dprint.

One workflow could be:

• look for prettier config files in the project root (there are a few...)
• read them in precedence order (I can put together a list)
• override with the config from the dprint.json (if any)
• then execute prettier.