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
Problem
The code base, despite existing linting rules, lacks consistent formatting, leading to:
Reduced Readability: Inconsistent indentation, spacing, and wrapping make code harder to understand for all developers.
Manual Formatting Waste: Developers spend time manually formatting instead of focusing on logic and functionality.
Solution
Introduce Prettier as a code formatter base on the coding conventions to enforce consistent formatting, improving readability and freeing developer time for higher-level tasks
The text was updated successfully, but these errors were encountered:
Prettier conflicts with ESLint rules (operator-linebreak for instance). Looks like this cannot be done unless we are disabling some of the eslint rules. What should be the right approach for fixing this issue ?
I'd try to initially encourage Prettier to make as few changes as possible, due to existing large PRs out there. Merge conflicts could be a nightmare to sort out!
However, if we enforce prettier styling then I'm content for that to override eslint rules. I also work on https://github.com/gchq/Bailo, and that uses both Prettier & ESLint:
Problem
The code base, despite existing linting rules, lacks consistent formatting, leading to:
Solution
Introduce Prettier as a code formatter base on the coding conventions to enforce consistent formatting, improving readability and freeing developer time for higher-level tasks
The text was updated successfully, but these errors were encountered: