Skip to content

chore: add ESLint + Prettier config for consistent code style (#304) - #314

Open
laurentketterle-hub wants to merge 6 commits into
Heliobond:mainfrom
laurentketterle-hub:feat/eslint-config-standardization-304
Open

chore: add ESLint + Prettier config for consistent code style (#304)#314
laurentketterle-hub wants to merge 6 commits into
Heliobond:mainfrom
laurentketterle-hub:feat/eslint-config-standardization-304

Conversation

@laurentketterle-hub

Copy link
Copy Markdown

Closes #304

Changes

  • .eslintrc.json — ESLint config with TypeScript, React, import ordering
  • .eslintignore — Excludes build outputs, generated files, fixtures
  • .prettierrc — Consistent formatting (single quotes, trailing commas)
  • .vscode/settings.json — Auto-fix on save, format on save
  • .vscode/extensions.json — Recommended editor extensions
  • .github/workflows/ci.yml — Lint check in CI pipeline

Rules Configured

  • @typescript-eslint — no-unused-vars, no-explicit-any
  • react-hooks — rules-of-hooks (error), exhaustive-deps (warn)
  • jsx-a11y — accessibility best practices
  • import/order — alphabetical with grouping
  • eqeqeq, curly, prefer-const, no-var

Apply for Stellar Wave bounty.

@vercel

vercel Bot commented Jul 30, 2026

Copy link
Copy Markdown

@laurentketterle-hub is attempting to deploy a commit to the David Dada's projects Team on Vercel.

A member of the Team first needs to authorize it.

… lint:fix script

- Add .eslintrc.json with TypeScript, React hooks, jsx-a11y, import ordering rules
- Add .eslintignore for build outputs and generated files
- Enhance eslint.config.mjs (flat config) with strict TypeScript, accessibility,
  import ordering, and best-practice rules (eqeqeq, curly, prefer-const, no-var)
- Add lint:fix script to package.json (eslint . --fix)
- Add eslint-plugin-import, eslint-plugin-jsx-a11y, eslint-import-resolver-typescript
  as explicit devDependencies
- Update lint-staged to run eslint --fix on staged TS/TSX files

Closes Heliobond#304
@laurentketterle-hub
laurentketterle-hub force-pushed the feat/eslint-config-standardization-304 branch from 91b18cb to 77d9146 Compare August 6, 2026 17:29
@laurentketterle-hub

Copy link
Copy Markdown
Author

Note: CI failing due to Vercel deployment authorization. This needs the repo maintainer to re-authorize the Vercel integration for fork PRs. The code changes should be fine. Could a maintainer trigger the Vercel authorization?

@laurentketterle-hub
laurentketterle-hub force-pushed the feat/eslint-config-standardization-304 branch 2 times, most recently from 6835711 to 77d9146 Compare August 6, 2026 21:24
@laurentketterle-hub
laurentketterle-hub force-pushed the feat/eslint-config-standardization-304 branch from 6df4c06 to 373a9d2 Compare August 6, 2026 23:05
@laurentketterle-hub

Copy link
Copy Markdown
Author

🔄 Rebased on main + force-pushed to retrigger CI. The build failure should be resolved now.

@laurentketterle-hub

Copy link
Copy Markdown
Author

Note: Vercel deployment is failing across all PRs with 'Authorization required to deploy.' This appears to be a Vercel configuration issue requiring repo owner intervention to re-authorize the Vercel integration. Build CI is passing now after the latest ESLint config fix.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

tooling: ESLint config missing — inconsistent code style in PRs

2 participants