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

[legacy-framework] style: fix editor integration with ESLint #373

Merged
merged 2 commits into from
May 1, 2020

Conversation

wKovacs64
Copy link
Collaborator

Type: tooling fix

Closes: blitz-js/legacy-framework#492

What are the changes and their implications? ⚙️

Ran tsdx lint --write-file to "eject" the tsdx ESLint config and merged in our recent adoption of the unicorn plugin and corresponding rules.

Checklist

  • Tests added for changes
  • Any added terminal logging uses packages/server/src/log.ts

Breaking change: no

N/A

Other information

The tsdx CLI supports merging .eslintrc.js (don't think it honors .eslintrc though), but that isn't enough for VSCode, which doesn't know to perform said merge (so it only looks at the config it finds, which in this case is missing things like the TS parser, etc.). The solution from tsdx is to "eject" the ESLint config if you need to extend it while retaining editor integration.

@flybayer flybayer merged commit b0120d7 into canary May 1, 2020
@flybayer flybayer deleted the justin/fix-eslint branch May 1, 2020 05:09
@flybayer
Copy link
Member

flybayer commented May 1, 2020

Awesome, thank you so much!

@dillondotzip dillondotzip changed the title style: fix editor integration with ESLint [legacy-framework] style: fix editor integration with ESLint Jul 7, 2022
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.

VSCode ESLint integration not working
2 participants