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

Feat es lint #123

Merged
merged 11 commits into from
Apr 15, 2024
Merged

Feat es lint #123

merged 11 commits into from
Apr 15, 2024

Conversation

chris-nowicki
Copy link
Contributor

@chris-nowicki chris-nowicki commented Apr 10, 2024

Fixes #66 - adds the ability to lint our project using eslint

Setup & Run

  • There are two new lint dev dependency packages: eslint-config-next & eslint-plugin-jsx-a11y so be sure to install them by running pnpm i
  • Type npm run lint to lint the project

Copy link

vercel bot commented Apr 10, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
gridiron-survivor ✅ Ready (Inspect) Visit Preview 💬 Add feedback Apr 15, 2024 5:19pm
gridiron-survivor-storybook ✅ Ready (Inspect) Visit Preview 💬 Add feedback Apr 15, 2024 5:19pm

vmaineng
vmaineng previously approved these changes Apr 11, 2024
Copy link
Contributor

@vmaineng vmaineng left a comment

Choose a reason for hiding this comment

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

Looks good to me adding in esLint configs

.eslintrc.json Outdated
@@ -0,0 +1,3 @@
{
"extends": ["plugin:jsx-a11y/recommended", "next/core-web-vitals"]
Copy link
Collaborator

Choose a reason for hiding this comment

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

What ESLINT rules are included in both of these?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@shashilo
Copy link
Collaborator

I want to ensure we have NO WARNINGS. Any rule we set up is an ERROR. This will stop devs from ignoring warnings.

@chris-nowicki
Copy link
Contributor Author

chris-nowicki commented Apr 11, 2024

I want to ensure we have NO WARNINGS. Any rule we set up is an ERROR. This will stop devs from ignoring warnings.

Agreed. I think there are some default ones we may be able to suppress but right now you have to do it rule by rule in the config file. I am not finding anything that turns off global warnings.

There is a quiet option that I added into the package.json script that is supposed to show only errors when run:

"scripts": {
		...
		"lint": "next lint --quiet"
	}

@Clue355 Clue355 self-requested a review April 11, 2024 18:39
shashilo
shashilo previously approved these changes Apr 12, 2024
vmaineng
vmaineng previously approved these changes Apr 12, 2024
Copy link
Contributor

@vmaineng vmaineng left a comment

Choose a reason for hiding this comment

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

After reviewing new changes, it makes sense by the links Chris provided.

@shashilo shashilo dismissed stale reviews from vmaineng and themself via 9c95dd7 April 13, 2024 01:11
@shashilo shashilo requested review from vmaineng and shashilo April 13, 2024 01:15
@shashilo shashilo merged commit 6d084f2 into develop Apr 15, 2024
6 checks passed
@shashilo shashilo deleted the feat_esLint branch April 15, 2024 17:21
Clue355 pushed a commit that referenced this pull request May 1, 2024
Fixes #66  - adds the ability to lint our project using eslint

## Setup & Run

- There are two new lint dev dependency packages: `eslint-config-next` &
`eslint-plugin-jsx-a11y` so be sure to install them by running `pnpm i`
- Type `npm run lint` to lint the project

---------

Co-authored-by: Shashi Lo <[email protected]>
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.

Add ESLint
3 participants