feat: Add ESLint for code quality improvements #34
+508
−16
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.
PR: Add-ESLint-for-code-quality-improvements
Addressed: #38
Description:
This pull request addresses the need for ESLint configuration within our open-source project to enhance code quality and maintainability. I have taken the following steps to implement ESLint for TypeScript:
.eslintrc.js
configuration file..eslintignore
file to exclude specific files or directories from linting.yarn run lint
.yarn run check-types
(executingtsc -p tsconfig.json --noEmit
).Purpose:
The primary goal of this pull request is to enforce consistent code style and identify potential issues in the codebase, such as unused variables and other common programming mistakes. This will help maintain code quality and improve collaboration among contributors.
Checklist:
.eslintrc.js
file.yarn run lint
andyarn run check-types
scripts, and they are functioning as expected.