chore: updated .prettierrc.json to use "auto" for endOfLine

bwcr commented 7 months ago

Description

This pull request resolves a compatibility issue related to line endings (endOfLine) when transitioning from "lf" to "auto" for better compatibility with Windows environments.

Linked Issues

No linked issues

Preview / Screenshot

Checklist

[x] I have followed commit guideline to create PR title (https://conventionalcommits.org/en/v1.0.0/)

vercel[bot] commented 7 months ago

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
nextarter-chakra	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Apr 16, 2024 9:58am

netlify[bot] commented 7 months ago

Deploy Preview for nextarter-chakra ready!

Name	Link
Latest commit	293e989efad7ce885404b3f5872a8880aeb62473
Latest deploy log	https://app.netlify.com/sites/nextarter-chakra/deploys/661e4ba5ede2f80008d17394
Deploy Preview	https://deploy-preview-140--nextarter-chakra.netlify.app
Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 71 Accessibility: 100 Best Practices: 75 SEO: 100 PWA: 60 View the detailed breakdown and full score reports

To edit notification comments on pull requests, go to your Netlify site configuration.

sonarcloud[bot] commented 7 months ago

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud

sozonome commented 7 months ago

Hi @bwcr

Using auto for endOfLine in Prettier is not recommended because it can lead to inconsistent line endings within the same project. This inconsistency can cause several issues:

Version control issues: Version control systems like Git treat files with different line endings as modified, leading to unnecessary merge conflicts and noise in the commit history.
Cross-platform compatibility problems: Files with mixed line endings may not work correctly when shared between different operating systems (Windows, macOS, Linux).
Maintainability challenges: Having a mix of line endings in the codebase makes it harder to maintain and work with the code consistently.
Instead, it's better to explicitly set endOfLine to lf (line feed, \n), which is the standard line ending used on Unix-based systems and is widely considered the preferred line ending for cross-platform compatibility. Using lf ensures consistent line endings across the entire codebase, regardless of the operating system used for editing.

Most modern text editors and IDEs can handle lf line endings without any issues, even on Windows, which traditionally uses crlf (carriage return + line feed, \r\n). By configuring Git and your text editor/IDE properly, you can work with your preferred line endings locally while maintaining consistency in the shared codebase.

git config --global core.autocrlf true

sozonome / nextarter-chakra