Open
Conversation
Samaro1
force-pushed
the
chore/backend-eslint-config
branch
from
30dccd6 to
905c464
Compare
Contributor
|
@Samaro1 Can you resolve the conflicts? |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Adds an ESLint setup for the backend TypeScript codebase to standardize linting and improve code consistency without changing application logic.
Changes
Added ESLint and related dev dependencies (eslint, @typescript-eslint, airbnb-typescript, etc.)
Created .eslintrc.cjs with recommended and project-specific rules
Added .eslintignore to exclude build artifacts
Updated the lint script in package.json to run:
eslint --ext .ts src
Adjusted some rules to reduce unnecessary churn and match the current code style
Fixed or suppressed a few lint issues in test files (duplicate imports, unused variables, naming, quotes)
Added linting instructions to the README
Notes for Maintainer
Some tests were already failing before this PR (6 failed | 3 passed).
Those failures are unrelated to the ESLint setup.
Closes #43