-
Notifications
You must be signed in to change notification settings - Fork 10
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
Add recommended extensions and editor defaults #2072
base: develop
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not an expert in VScode, but this looks good to me.
"files.autoSave": "off", | ||
"debug.allowBreakpointsEverywhere": true, | ||
"gitdoc.enabled": false | ||
"editor.rulers": [100], |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"editor.rulers": [100], | |
"editor.rulers": [80], |
is there a specific reason we have this at 100? I just noticed this, I thought most common best practice is 80?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I assume it's because so much of the code was done with a 100 character limit that we'll just live with that. (80 and 100 are both fairly commonly adopted and justifiable limits. I don't know which is more common.) I'd personally prefer setting it to 80 and gradually adopting that as we make changes. But if Evan thinks that's too painful, I won't disagree. I am interested in his reasoning, especially if I've guessed wrong.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
I have added the minimum recommended extensions for VS Code so that users will be prompted to install our linting extensions.
This should probably be complemented by updates to CI to error on Linter warnings.