chore: setup formatter and linter for VSCode #63
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This is config you can keep locally. If you want to add .vscode to gitignore feel free to do so in the other PR |
|
i disagree that
|
fregante
reviewed
Aug 26, 2024
| "editor.defaultFormatter": "samverschueren.linter-xo" | ||
| }, | ||
| "editor.codeActionsOnSave": { | ||
| "source.fixAll": "always" |
There was a problem hiding this comment.
This is a user preference. I also use VS Code but don’t run linters auto fix on save.
I’m generally not a fan of storing this config on repos and it’s more likely I’ll switch back to a plain eslint at some point anyway.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
makes it easier to apply xo linter and formatter output on VSCode.