format VS husky

C# has https://github.com/dotnet/format but because C# is, well, not JS, the importance of linting is far less significant. Instead, there are hundreds of out-of-box analyzers that highlight problematic patterns or likely mistakes in the code and there are even more that you can enable through extensions (like Roslynator) or through packages that are 'dotnet add package' away.

On the package management - it couldn't be more different between Java and C# and it's incorrect to compare the two. .NET has few if any issues of the former.

In my project, I incorporated a source code formatter provided by the dotnet framework. I also added .editorconfig file to the root directory of my project. This file defines formatting rules, such as indent style and indent size, ensuring consistency throughout the codebase.

However: It would appear that dotnet has a lot of extension values for editorconfig - does Rider support all of those? Some of those? Is there documentation of any extension?

Like this post explains: https://github.com/dotnet/format/issues/879

Dotnet Format

Oh, I'm using .net format. https://github.com/dotnet/format . I will take a look at csharpier to compare both :)

- dotnet format but this is not a linter I think?

Para formatar seu código instale o dotnet format e execute o seguinte comando:

dotnet format does not break lines when they get too long, or collapse lines if they are too short and could be fit on the same line. See https://github.com/dotnet/format/issues/246. Another way to say it - no matter where you put linebreaks in a given code file, csharpier will produce the same output. dotnet format would produce a different output based on where current line breaks exist.

Reading Biome doc I also switched from husky to lefthook.

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.

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.

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.

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.

In all my projects I use husky, lint-staged and commitlint.