Linting Standards
Linting enforces consistency and prevents common mistakes in the codebase. All developers must use the same linting configuration to ensure a unified style across the team.
Base rules
- The configuration is based on Airbnb ESLint rules.
- Modifications are applied to match team preferences and project requirements.
- Prettier is used alongside ESLint to handle code formatting.
Guidelines
- Linting must run automatically on every commit (via Husky + lint-staged).
- Code that does not pass linting cannot be pushed.
- Developers should not disable linting rules unless explicitly approved.
- If a new rule causes conflicts, it must be discussed with the team and adjusted centrally — never overridden locally.