Skip to content

fix(backend): add and configure ESLint for backend workspace#150

Open
Harxhit wants to merge 2 commits into
Dev-Card:mainfrom
Harxhit:lint-fix
Open

fix(backend): add and configure ESLint for backend workspace#150
Harxhit wants to merge 2 commits into
Dev-Card:mainfrom
Harxhit:lint-fix

Conversation

@Harxhit
Copy link
Copy Markdown
Collaborator

@Harxhit Harxhit commented May 18, 2026

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

  • Infrastructure / DevOps
  • Refactor (no functional change)

What Changed

  • Added ESLint setup for the backend workspace.
  • Configured Flat Config based ESLint setup (eslint.config.js).
  • Added TypeScript ESLint plugins and supporting lint packages.
  • Configured backend-only linting workflow.
  • Updated root lint script to target backend workspace only.
  • Temporarily disabled several strict TypeScript ESLint rules to avoid blocking development while the existing codebase is gradually migrated to stricter standards.

How to Test

  1. Install dependencies:
pnpm install
  1. Run backend linting:
cd apps/backend && pnpm lint
  1. Verify backend starts successfully:
pnpm --filter @devcard/backend dev

Checklist

  • My code follows the project's coding style (pnpm lint passes for backend workspace).
  • TypeScript compiles without errors (pnpm -r run typecheck).
  • I have added or updated tests for the changes I made.
  • All tests pass locally (pnpm -r run test).
  • I have updated documentation where necessary.
  • No new console.log or debug statements left in the code.
  • Breaking changes are documented in this PR description.

Proof

lint:fix lintProof

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.

@Harxhit Harxhit added the gssoc:approved Required label for every approved PR. Gives the base +50 points and enables contribution tracking. label May 18, 2026
@Harxhit Harxhit requested a review from ShantKhatri May 18, 2026 08:59
@ShantKhatri
Copy link
Copy Markdown
Contributor

@Harxhit could you please add SS of the test?

@Harxhit
Copy link
Copy Markdown
Collaborator Author

Harxhit commented May 18, 2026

@Harxhit could you please add SS of the test?

I have added the proofs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

gssoc:approved Required label for every approved PR. Gives the base +50 points and enables contribution tracking.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants