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

Add Visual Studio Code workspace configuration #117

Merged
5 commits merged into from
Nov 3, 2021
Merged

Conversation

georgefst
Copy link
Contributor

I've argued against editor-specific configuration before, but this would be a useful way for me to be able to share settings with @annedino4...

"arrterian.nix-env-selector",
"b4dm4n.nixpkgs-fmt",
"bbenoist.nix",
"dbaeumer.vscode-eslint",
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Somehow I get a lot of eslint warnings which don't appear on CI. I'm still investigating that.

"files.insertFinalNewline": true,
"files.trimFinalNewlines": true,
"files.trimTrailingWhitespace": true,
"nixEnvSelector.nixFile": "${workspaceRoot}/shell.nix",
Copy link
Contributor Author

@georgefst georgefst Nov 2, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This isn't ideal, but there's no flake support yet: arrterian/nix-env-selector#53.

And we're rarely needing to reload the editor in practice, so the fact that it takes a few seconds longer isn't a huge issue.

@dhess
Copy link
Member

dhess commented Nov 2, 2021

I'm fine with this, so just go ahead and commit it when you're finished with the config.

primer-app.code-workspace Outdated Show resolved Hide resolved
We were sticking to VScode's built-in formatter, since I thought `primer-app.code-workspace` was the only "jsonc" file in the project. But it turns out that the `tsconfig.json` files also allow comments, and we use Prettier on those.
As was configured in the previous commit.
Prettier handles this for us on all source files anyway, and for other files we needn't care (there is currently trailing whitespace in the README, at least).
@georgefst
Copy link
Contributor Author

bors merge

@ghost
Copy link

ghost commented Nov 3, 2021

@ghost ghost merged commit 11b0b00 into main Nov 3, 2021
@ghost ghost deleted the georgefst/vscode-config branch November 3, 2021 14:24
ghost pushed a commit that referenced this pull request Nov 8, 2021
127: Remove Visual Studio Code workspace configuration r=dhess a=georgefst

Reverts #117.

Co-authored-by: George Thomas <georgefsthomas@gmail.com>
ghost pushed a commit that referenced this pull request Nov 8, 2021
127: Remove Visual Studio Code workspace configuration r=georgefst a=georgefst

Reverts #117.

Co-authored-by: George Thomas <georgefsthomas@gmail.com>
This pull request was closed.
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.

None yet

2 participants