RestEase.SourceGenerators does not play well with .editorconfig/StyleCop
See original GitHub issueAdded RestEase.SourceGenerators
to my .NET 5 project, and the project no longer builds:
Editor Config: https://github.com/Dotnet-Boxed/Templates/blob/master/Source/ApiTemplate/.editorconfig
Maybe we need // <auto-generated />
on the generated file or something? I am new with the Source Generators.
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Use editorconfig and remove Stylecop.Analyzers ...
The StyleCop analyzers add some features that editorconfig doesn't support, as well as the ability to enforce style rules at build time.
Read more >Visual Studio editorconfig and code analysis is frustrating
In recent years I used ruleset files for code analysis, configured via a project's Properties -> Code Analysis tab.
Read more >Modern StyleCop alternative? Advice appreciated. : r/dotnet
We are needing to enforce some very basic style rules in a set of DotNet 6 projects. This is not something we have...
Read more >EditorConfig versus analyzers - Visual Studio (Windows)
EditorConfig files cannot be used to configure legacy analysis, whereas rule sets can. Code analysis in CI builds. Does .NET Compiler Platform-based code ......
Read more >Use StyleCop styles | JetBrains Rider Documentation
To apply StyleCop rules, JetBrains Rider relies on its own features and settings, which do not always map directly onto StyleCop rules:.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Should be fixed in 1.5.2
In case it’s not clear from the README, you can uninstall the source generator package and just use RestEase to work around this for now: you’ll get any errors at runtime instead of compile time, but the functionality is the same.