EditorConfig VS Prettier

These are tools that you need to add. But the most elemental code formatting is not here, it is in the widely supported .editorconfig file. - Source: dev.to / 14 days ago

Hello, Maybe you should check this project: https://editorconfig.org/ Regards,. - Source: Hacker News / 4 months ago

Editorconfigchecker. A linter that checks files for compliance with editorconfig rules. Another linter that helps maintain consistency in the format of all files. - Source: dev.to / 5 months ago

Oh, yeah, we had that issue too and solved it pretty successfully with `.editorconfig` (shareable between VScode and IntelliJ, https://editorconfig.org/) combined with `prettier`. Each IDE is configured to: - Not reformat code on its own - Ignore whitespace - Run `prettier` as a pre-commit hook Those settings are saved to `.editorconfig` where possible, or to each IDE's repo-specific folder (e.g. `.idea`). Then in... - Source: Hacker News / 6 months ago

I am aware of .editorconfig, and one day that may be the correct answer but the specification does not support every element of the styles of both oss and css. Source: 7 months ago

Automating code checks with static code analysis allows us to enforce code styling effectively. By integrating tools into our workflow, we can identify errors at an early stage, while coding instead of blocking us at the end. For instance, flake8 checks Python code for style and errors, eslint performs similar checks for JavaScript, and prettier automatically formats code to maintain consistency. - Source: dev.to / 9 days ago

So anyways, I wanted to hook up Emacs with Astro support. For now, I've just been roughing it out there and running Prettier by itself and turning off save on format and auto-complete. It's been scary. - Source: dev.to / 9 days ago

If you're a developer, you're surely familiar with Prettier and ESLint. With over 8 years of existence, they have established themselves as references in the JavaScript ecosystem. - Source: dev.to / 14 days ago

No formatting inconsistencies: The committed code should follow the organization's code formatting standards(prettier or pretty-quick). - Source: dev.to / 21 days ago

Let’s walk through the steps for a one-time setup to configure husky pre-commit and pre-push hooks, ESLint with code styles conventions, prettier code formatter, and lint-staged. Husky automatically runs a script on each commit or push. This is useful for linting files to enforce code styles that keeps the entire code base following conventions. - Source: dev.to / 24 days ago