editorconfig-vim
husky
editorconfig-vim | husky | |
---|---|---|
135 | 127 | |
3,105 | 31,666 | |
0.2% | - | |
5.1 | 8.6 | |
about 1 month ago | 9 days ago | |
Vim Script | JavaScript | |
GNU General Public License v3.0 or later | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
editorconfig-vim
-
How to set up a new project using Yarn
.editorconfig helps maintain consistent coding styles for multiple developers working on the same project across various editors and IDEs. Find more information on the EditorConfig website if youâre curious.
-
Most basic code formatting
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.
-
Taking the Language Server Protocol one step further
Hello,
Maybe you should check this project:
https://editorconfig.org/
Regards,
- How to config indentation per project?
-
How We Started Managing BSA Delivery Processes on GitHub
editorconfigchecker. A linter that checks files for compliance with editorconfig rules. Another linter that helps maintain consistency in the format of all files.
-
Ask HN: What work/office purchase transformed your life?
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 theory each developer can use whatever IDE they want, whatever whitespace settings they want (tabs vs spaces), and the end code committed to the repo is still the same.
-
Rider - Formatting across projects
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.
-
Is there any reason to keep the editorconfig plugin installed?
Does this mean I can completely get rid of this plugin?: https://github.com/editorconfig/editorconfig-vim
-
Is there really no support for editorconfig, yet?
[1] https://editorconfig.org
- How do you handle code formatting in a team?
husky
- Supercharge your workflow with Husky, Lint Staged and Commitlint
-
Streamline Your Workflow: A Guide to Normalising Git Commit and Push Processes
In this post, I will primarily discuss client-side hooks. I'll delve into three specific hooks: pre-commit, commit-msg, and pre-push. The central tool discussed will be Husky, which simplifies the configuration of Git Hooks, making it more straightforward.
-
I switch from Eslint to Biome
Reading Biome doc I also switched from husky to lefthook.
-
Streamline Your Workflow: Setting Up Git Hooks with Husky to Simplify Version Updates
Dive deeper into the world of Husky with the official documentation. Explore the capabilities of Standard Version through its comprehensive documentation. Unravel the mysteries of semantic-release with its detailed documentation. Discover the versatility of bumpp with its comprehensive documentation.
-
Git Project Configuration With Husky and ESLint
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.
- Padronizando seu código através dos Git Hooks
- Angular 14 + Prettier + Husky Setup
-
How Automation Saved Me from Oops Moments: Never Skip Tests in Production Again!
We were already using lint-staged and have a pre-commit hook in place using Husky in our project for linter and prettier. So it made sense to add a check here.
- Pre-commit with husky & lint-staged
-
How to Improve Development Experience of your React Project
Now, let's talk about Husky. It's a wonderful tool that enables you to run scripts on any Git hooks. We'll add a pre-commit hook to run ESLint and Stylelint checks before committing. This ensures that we don't commit code with errors.
What are some alternatives?
nvim-projectconfig - neovim projectconfig
simple-git-hooks - A simple git hooks manager for small projects
pycodestyle - Simple Python style checker in one Python file
lerna - :dragon: Lerna is a fast, modern build system for managing and publishing multiple JavaScript/TypeScript packages from the same repository.
project-config.nvim - Per project config for Neovim
pre-commit - A framework for managing and maintaining multi-language pre-commit hooks.
tabset.nvim - A Neovim plugin to easily set tabstop, shiftwidth and expandtab settings for file types.
standard-version - :trophy: Automate versioning and CHANGELOG generation, with semver.org and conventionalcommits.org
prettier - Prettier is an opinionated code formatter.
emacs-solidity - The official solidity-mode for EMACS
pretty-quick - ⥠Get Pretty Quick