pre-commit by Yelp VS EditorConfig

# See https://pre-commit.com for more information # See https://pre-commit.com/hooks.html for more hooks Repos: - repo: https://github.com/pre-commit/pre-commit-hooks rev: v3.2.0 hooks: - id: trailing-whitespace - id: end-of-file-fixer - id: check-yaml - id: check-toml - id: check-added-large-files - repo: local hooks: - id: tox lint name: tox-validation ... - Source: dev.to / 5 months ago

Pre-commit hooks act as the first line of defense in maintaining code quality, seamlessly integrating with linters and code formatters. They automatically execute these tools each time a developer tries to commit code to the repository, ensuring the code adheres to the project's standards. If the hooks detect issues, the commit is paused until the issues are resolved, guaranteeing that only code meeting quality... - Source: dev.to / 5 months ago

Https://pre-commit.com/ can (and probably should) be used with any editor for such things. - Source: Hacker News / 5 months ago

Pre-commit Hooks: Pre-commit is a tool that can be set up to enforce coding rules and standards before you commit your changes to your code repository. This ensures that you can't even check in (commit) code that doesn't meet your standards. This allows a code reviewer to focus on the architecture of a change while not wasting time with trivial style nitpicks. - Source: dev.to / 6 months ago

Ah, fair enough! On my team we use pre-commit[0] a lot. I guess I would define the history to be something like "has this commit ever been run through our pre-commit hooks?". If you rewrite history, you'll (usually) produce commits that have not been through pre-commit (and they've therefore dodged a lot of static checks that might catch code that wasn't working, at that point in time). That gives some manner of... - Source: Hacker News / 7 months ago

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 / 11 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 / 5 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