Roslynator
editorconfig-vim
Roslynator | editorconfig-vim | |
---|---|---|
17 | 134 | |
2,972 | 3,104 | |
0.8% | 0.1% | |
9.3 | 5.1 | |
12 days ago | 22 days ago | |
C# | Vim Script | |
GNU General Public License v3.0 or later | GNU General Public License v3.0 or later |
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.
Roslynator
-
Roslynator VS Metalama - a user suggested alternative
2 projects | 7 Dec 2023
-
does anyone have a working csharp-language-server setup they can share?
There's also this project https://github.com/JosefPihrt/Roslynator that can add even more analyzers.
-
What do you think about formatting contents in parenthesis like contents in braces?
It does. Nearly every style guide I've seen for any language that allows this prefers this style. I personally prefer it when such structures are needed, but would suggest following it just for consistency and the practical benefits.
-
top 5 things every c# developer should know
Roslynator.Analyzers
-
How to write clear and robust unit tests: the dos and don'ts
The reason I say 'similar' above is that though you may treat it as production code, there are some things in the nature of writing tests that may require different coding standard to be enforced. A good example of this is the RCS1046 analyzer, enforcing names of asynchronous methods to be suffixed with 'Async'; in this case it would be acceptable to override this rule (with an .editorconfig for example) so that you're method name continues to describe the behaviour of the application, and we don't have tests named like public async Task My_descriptive_method_name_async().
-
Linting async method declarations
You can write Roslyn analyzer but you can also simply use this set of analyzers: https://github.com/JosefPihrt/Roslynator. It has analyzers for both async method not ending with Async and non-async methods ending with Async.
-
Is my code hard to read?
My suggestion is to look into installing Roslynator or Sonarlint. Both are free and work with either Visual Studio or VS Code. With them you can right click on your solution and Run Analysis and it will give you a list of "code smells" and automatic fixes for many of them. They are great tools for any dev.
-
Visual Studio vs. Jetbrains Rider Performance
Roslynator while not exactly as good as full R# does a pretty good job for the analysis and refactoring hints imo. Paired with Intellicode + NCrunch (paid) so far has been a good enough experience for us.
-
Which code convention would you choose between these two as best practice?
I prefer the second and roslynator would give RCS1124: Inline local variable1 for the first one.
-
What NuGet packages do you automatically add
Roslynator.Analyzers
editorconfig-vim
-
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?
-
Announcing C# Dev Kit for Visual Studio Code
I dunno who downvoted your question, but I believe you can use .editorconfig to set that up for you.
What are some alternatives?
StyleCopAnalyzers - An implementation of StyleCop rules using the .NET Compiler Platform
nvim-projectconfig - neovim projectconfig
sonar-dotnet-vscode - Sonar Dotnet is an Visual Studio Code extensions to C#
pycodestyle - Simple Python style checker in one Python file
omnisharp-roslyn - OmniSharp server (HTTP, STDIO) based on Roslyn workspaces
project-config.nvim - Per project config for Neovim
Refactoring Essentials - Refactoring Essentials for Visual Studio
tabset.nvim - A Neovim plugin to easily set tabstop, shiftwidth and expandtab settings for file types.
AxoCover - Nice and free .Net code coverage support for Visual Studio with OpenCover.
prettier - Prettier is an opinionated code formatter.
VsVIM - Vim Emulator Plugin for Visual Studio 2015+
emacs-solidity - The official solidity-mode for EMACS