Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Switch to Prettier #2

Merged
merged 1 commit into from
Jun 30, 2021
Merged

Switch to Prettier #2

merged 1 commit into from
Jun 30, 2021

Conversation

jsumners
Copy link
Contributor

As commented earlier, #1 (comment), I was testing how viable it would be to migrate to using https://standardjs.com over Prettier through this project. The goal was to determine a set of baseline settings recommendations for VSCode such that switching between projects would be seamless.

My plan was to suggest:

  1. Remove the VSCode "Prettier" extension
  2. Install the standard ESLint extension (https://marketplace.visualstudio.com/items?itemName=dbaeumer.vscode-eslint)
  3. Provide settings that would allow the ESLint extension to work in both project styles

That wouldn't work due to this issue:

So I investigated an alternate plan:

  1. Add the Standard VSCode extension (https://marketplace.visualstudio.com/items?itemName=standard.vscode-standard)
  2. Provide docs on how to work with both Prettier (or ESLint) and Standard extensions installed side-by-side

This plan fails due to:

Ultimately, I found it too frustrating at this time to get VSCode playing nicely with both project styles at the same time. I believe that if the ESLint extension issue is resolved then plan 1 would be a viable plan.

For now, however, I am calling the test a failure and swapping this project to Prettier.

@huong-dang
Copy link

Prettier ftw!

@jsumners jsumners merged commit c6baa4a into master Jun 30, 2021
@jsumners jsumners deleted the switch-to-prettier branch June 30, 2021 16:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants