fix(backend): add and configure ESLint for backend workspace#150
Open
Harxhit wants to merge 2 commits into
Open
fix(backend): add and configure ESLint for backend workspace#150Harxhit wants to merge 2 commits into
Harxhit wants to merge 2 commits into
Conversation
Contributor
|
@Harxhit could you please add SS of the test? |
Collaborator
Author
I have added the proofs. |
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
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.
Summary
This PR adds and configures ESLint for the backend workspace using Flat Config (
eslint.config.js). It introduces TypeScript ESLint tooling and backend-specific linting configuration without modifying shared workspace packages. Some strict TypeScript ESLint rules were temporarily relaxed to keep development unblocked while the existing codebase is gradually migrated to stricter standards.Type of Change
What Changed
eslint.config.js).How to Test
Checklist
pnpm lintpasses for backend workspace).pnpm -r run typecheck).pnpm -r run test).console.logor debug statements left in the code.Proof
Note -> Please ignore the neon adapter error.
Additional Context
Some strict ESLint rules such as
no-explicit-any, unsafe assignment checks, and strict boolean expression checks were temporarily turned off to avoid blocking development. These rules will be gradually re-enabled as the backend codebase is improved and properly typed.