Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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:
That wouldn't work due to this issue:
So I investigated an alternate plan:
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.