EditorConfig VS stylelint

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 / 18 days ago

Hello, Maybe you should check this project: https://editorconfig.org/ Regards,. - Source: Hacker News / 5 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

There are more linting tools that I won't go into deeply, but you can integrate them with lint-staged. For example, you can lint your CSS content with Stylelint, or even lint your README files with markdownlint, etc. - Source: dev.to / about 12 hours ago

Another common way to extend configs in linters is using the extends key in the configuration file. Let's take StyleLint as an example:. - Source: dev.to / 3 months ago

Stylelint is similar to ESLint, but its focus is on styling rather than JavaScript. It helps you find errors in style files, such as old syntax or empty classes. We will also incorporate stylelint-config-clean-order to sort your style rules and group them consistently across the entire codebase. - Source: dev.to / 4 months ago

As the property is still experimental, stylelint does not recognize it yet at the time of writing this, so let's explicitly disable the property-no-unknown rule only where we use it by adding a stylelint-disable comment and re-enable it afterwards. - Source: dev.to / 12 months ago

Run static analysis e.g. Lint with lockfile-lint, Stylelint, ESLint, check for unimported files using unimported, and identify potential security vulnerabilities. Source: about 1 year ago