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

Fix vscode lints #3

Merged
merged 9 commits into from
Jan 31, 2022
Merged

Fix vscode lints #3

merged 9 commits into from
Jan 31, 2022

Conversation

flying-sheep
Copy link
Owner

@flying-sheep flying-sheep commented Nov 10, 2021

Fixes #1

Blocked by yarnpkg/berry#4045

@flying-sheep flying-sheep marked this pull request as draft November 10, 2021 12:25
@flying-sheep flying-sheep marked this pull request as ready for review January 31, 2022 14:46
@flying-sheep flying-sheep merged commit faa251c into main Jan 31, 2022
@flying-sheep flying-sheep deleted the fix-vscode-lints branch January 31, 2022 14:51
PhilippBaschke added a commit to PhilippBaschke/cv that referenced this pull request Mar 4, 2022
The XO VSCode doesn't work with yarn PNP out of the box. Someone found
a solution by createing a patched node runtime that can be used to run
XO.
xojs/vscode-linter-xo#71
flying-sheep/react-color-scheme-switch#3
yarnpkg/berry#4045

I added the XO plugin to the recommended VSCode extensions and added
a workspace config to automatically enable it for the project.
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.

Make linting in VS Code work
1 participant