Internal: Setup prettier and fix all lint/format issues [TMZ-1051]#671
Internal: Setup prettier and fix all lint/format issues [TMZ-1051]#671rami-elementor wants to merge 3 commits into
describe-changes@v1
describe-changes@v1: with concatenate mode: append
✨ PR Description
1. Problem & Context
Integrate Prettier code formatter across the codebase to enforce consistent code style and reduce lint/format friction. Replaces manual eslint-based formatting with Prettier's opinionated, deterministic approach.
2. What Changed (Where)
- Config & tooling: Added
.prettierrc, updatedpackage.json(Prettier + eslint-config-prettier + eslint-plugin-prettier), updated.eslintrc.jsto remove conflicting rules and extend Prettier config - TypeScript/React files (60+ files in
modules/admin-home,dev/js,tests/playwright): Reformatted spacing, arrow functions, brackets, template literals, JSX attributes - Build config (
webpack.config.js): Improved readability with expanded multi-line declarations
3. How It Works
Prettier enforces formatting via .prettierrc config (tabs, 80-char width, always arrow parens, bracket spacing). ESLint integration delegates formatting concerns to Prettier via eslint-plugin-prettier and eslint-config-prettier (disables conflicting ESLint rules). npm run format now triggers Prettier instead of manual lint-fix cycles.
4. Risks
Low risk—purely formatting, no logic changes. Only concern: Prettier's 80-char line width may force awkward breaks in long strings/URLs (e.g., test selectors), but this improves consistency at minor verbosity cost. Existing tests/functionality unaffected.
Generated by LinearB AI and added by gitStream.
AI-generated content may contain inaccuracies. Please verify before using.
💡 Tip: You can customize your AI Description using Guidelines Learn how