ryan-dia / eslint-config-hijacking

Hi 👋

🎾 강철원

Contribute

• eslint/eslint#17435

• typescript-eslint/typescript-eslint#7404

• vercel/next.js#52599
• vercel/next.js#52787

• toss/slash#333
• toss/slash#334

• jest-community/vscode-jest#1032

🧸 Me 🧸

 

eslint-config-hijacking's Issues

feat : typescript eslint 설정 변경

ESLint version

eslint : 8.45.0
@typescript-eslint/parser : 6.2.0

Introduction

typescript-eslint v6가 발표되면서 몇가지 변경 및 추가사항이 생겨서 일부 설정을 변경하였습니다.

typescript-eslint v5

• recommended
• recommended-requiring-type-checking
• strict

Those configurations worked well for most projects. However, some users correctly noted two flaws in that approach

• Strict rules that didn't require type checking were lumped in with those that did
• Stylistic best practices were lumped in with rules that actually find bugs

이를 보완하기위해 v6에서는 다음 두 그룹으로 재작업했습니다.

1. Functional rule configurations, for best best practices and code correctness

• recommended
• recommended-type-checked
• strict
• strict-type-checked

2. Stylistic rule configurations, for consistent and predictable syntax usage

• stylistic
• stylistic-type-checked

What problem do you want to solve?

What do you think is the correct solution?

Additional comments

Refernce

recommended-type-checked : link

feat(eslint-plugin): rework configs: recommended, strict, stylistic; -type-checked