Check-in a Prettier config file for editor extensions

[wholesomedev]

Can we check-in a Prettier config file which will inform Prettier extensions in editors of how to format code?

If so, can we put it in our common repo and extend it from the other repos?

[forabi]

The unofficial prettier extension for VS Code can read configuration from a field named prettier in package.json. However, this field is not something officially supported by prettier and I don't know of any other code editor extensions that support it. So we need to duplicate the configuration for VS Code extension and the CLI command which is run on every commit.

[forabi]

Relevant issue: prettier/prettier#62

[wholesomedev]

I'm okay with either approach.

[forabi]

I'm okay with either approach.

So should we add the "prettier" field for VS Code extension? I don't see the point. The files will be prettified when committed anyway.

[wholesomedev]

Problem is someone (like me) might have different default configurations in their editor. Now whenever they edit one of our files, the whole file gets reformatted and it's a little jarring. That's what I'm hoping to solve.

[wholesomedev]

@forabi Can't we get the CLI and editor extensions both to read from one of these config files?
https://prettier.io/docs/en/configuration.html

[forabi]

Can't we get the CLI to read from one of these config files?

Sorry, I didn't realize that prettier supports a configuration file. I will look into that.