这是indexloc提供的服务,不要输入任何密码
Skip to content

fix: set eslint config to "root" inside examples #1151

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

Closed

Conversation

darrylblake
Copy link

Prevents ESlint from referencing parent config and dependencies causing linting to fail if they've not been installed.

@vercel
Copy link

vercel bot commented Apr 29, 2022

@darrylblake is attempting to deploy a commit to the Vercel Team on Vercel.

A member of the Team first needs to authorize it.

Prevents ESlint from referencing parent config and dependencies causing linting to fail if they've not been installed.
@nathanhammond
Copy link
Contributor

Hey @darrylblake! Thanks for drawing my attention to an issue with our examples. The eslint configurations were not actually relying on the eslint-recommended approach to sharing configurations and were instead directly requiring files.

The method you've proposed to resolve the issues you were seeing tipped me off to that issue because it required setting root at a non-root location. Given the degree of difference between this proposed solution and the ESLint-recommended solution, I'm closing this PR in favor of #1172.

Thank you so much for an actionable error report!

kodiakhq bot pushed a commit that referenced this pull request May 3, 2022
Our `eslint` configurations in examples were not actually relying on the `eslint`-recommended approach to sharing configurations and were instead directly requiring files. This switches the approach to what ESLint would recommend.

Originally detected by @darrylblake in #1151, this corrects all of our examples.
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.

2 participants