Skip to content

[MEDIUM] Enable no-console ESLint rule with appropriate overrides #59

Description

@kilodesodiq-arch

Engineering Gap

ESLint configs lack no-console rule enforcement despite 20+ console.* calls in production code. .eslintrc.js and app/backend/eslint.config.mjs both omit this rule.

Codebase Evidence

  • .eslintrc.js: No no-console rule in rules object
  • app/backend/eslint.config.mjs: No no-console rule
  • app/frontend/eslint.config.mjs: Next.js defaults — may include console warnings

Risk Profile

Current Risk

Gradual accumulation of unstructured console output. Potential data leakage.

Business Impact

Degraded observability. Compliance risk from unredacted console output.

Remediation Strategy

Add no-console as warn in all ESLint configs. Suppress for specific dev-only files (seed scripts, debug helpers). Progress to error after cleanup.

Success Conditions

  • no-console rule enabled as warn minimum
  • Dev-only files explicitly excluded
  • CI lint passes

Change Surface

Files: .eslintrc.js, app/backend/eslint.config.mjs

Security Review

Reduces information leakage through console.

Completion Checklist

  • Implementation completed
  • Peer reviewed
  • Lint passing
  • Ready for merge

Activity

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

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions