Use recommended ESLint rules and fix errors #192
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Deploy preview for zothacks-site-2023-sanity ready!
|
- Add ESLint rules from `eslint:recommended` and `next/typescript` - Resolve subsequent lint errors; still have warnings about next/image - Remove old components for Stickers
taesungh
force-pushed
the
update/eslint-rules
branch
from
4e5e69e to
24e1b5f
Compare
|
Deploy preview for zothacks-site-2023 ready!
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As part of #188, use recommended ESLint rules. Will make a separate PR later for checking import order to reduce the scope of this one.
Changes
eslint:recommendedandnext/typescript