The road to v2

The road to v2

NOTE: There might be controversial things in this issue. I am 100% certain that you won’t like every thing in this issue. Try to read trough it, give it a minute or two and let it sink in. Once you processed it all, then but only then you are allowed to comment. 😘

We have come very far using this extension. I would like to start with a big thank you to all the contributors. I would also like to thank all our users. And last but not least I would also like to thank the whole prettier team.

That being said, I think it is time that we write our road map to the 2.0.0 release.

Plugins

Plugins are still in beta, but I think that they can be very useful.

What if we make sure that plugins are automatically resolved correctly. According to the docs they should be loaded automatically when they start with @prettier/plugin- or prettier-plugin-. We probably have to resolve these based on the used prettier version.

Here are some crazy thoughts:

• What if we remove the eslint integration and write it as a plugin?
• What if we remove the tslint integration?
• What if we remove all integrations and purely rely on plugins? 🤔

NOTE: This will allow us to focus on core functionality and keep the code fast and clean.

Configuration

Currently we have a bunch of options, and people want even more options. Options are not fun, trust me.

Configuration options also have some problems, e.g.: The goal of prettier is to let teams write code however they want and prevent nitpicking on issues. But what if you have the option "prettier.semi": true, and your colleague has the option "prettier.semi": false,. You just introduced nitpicks on all your PR’s, so here is a suggestion.

What if we remove most of the options in the VSCode extension, and we just read from the configuration from a local (or a parent one if you have multiple projects) prettier config like .prettierrc.

It might be a good idea to keep the core options in place, I don’t know yet.

Advantages:

• Your team is in sync, yay!
• You don’t have to wait for an update on the extension to use your favorite option.
• We don’t have to support those options anymore. 🎉

Disadvantages:

• You have to create a config file in your current folder / project. (Only if you want to use custom configuration options!)

Feature list

• Better error management (notify the user when there are actual errors with the plugin, not your code. This shouldn’t be a linter).
• Make it easier to report issues with action / debug logs and all settings used for prettier.
• …

Thanks

Thank you for reading, feel free to list other features.

[gimenete]

+1 to rely only in .prettierrc. Having the team in sync is key. You have to create a config file but it’s minimal and makes all your tooling aware of your config options.

[rgaino]

I’m all in for a local config file. Multiple team members with different configs goes against the basic concept of prettier.