You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should add an automated ESLint workflow for our Template Playground. Right now, linting depends on developers running it manually, which leads to inconsistent formatting and missed errors. An automated check on every PR will ensure cleaner, more consistent code and save mentors time during code reviews.
Possible Solution
Runs on pull requests to main branch.
Sets up Node.js 18.x .
Installs dependencies (npm ci).
Runs eslint src --ext ts,tsx --report-unused-disable-directives --max-warnings 0 to ensure no errors or warnings sneak through.
Fails the workflow if any issues are found, blocking the PR until it's fixed.
Expected Outcome
Every PR gets automatically checked for linting errors. This keeps our codebase clean, saves time on reviews, and prevents formatting issues from ever hitting production.
The text was updated successfully, but these errors were encountered:
Feature Request 🛍️
Use Case
We should add an automated ESLint workflow for our Template Playground. Right now, linting depends on developers running it manually, which leads to inconsistent formatting and missed errors. An automated check on every PR will ensure cleaner, more consistent code and save mentors time during code reviews.
Possible Solution
Runs on pull requests to main branch.
Sets up Node.js 18.x .
Installs dependencies (npm ci).
Runs eslint src --ext ts,tsx --report-unused-disable-directives --max-warnings 0 to ensure no errors or warnings sneak through.
Fails the workflow if any issues are found, blocking the PR until it's fixed.
Expected Outcome
Every PR gets automatically checked for linting errors. This keeps our codebase clean, saves time on reviews, and prevents formatting issues from ever hitting production.
The text was updated successfully, but these errors were encountered: