Re-enable warnings which are currently disabled in the build
See original GitHub issueCurrently there are some warnings disabled in the build (mostly related to ///
comments). #2258 removes some of them, but even after that is merged there will be these remaining: <NoWarn>1591;1573</NoWarn>
. Note that these warnings are disabled in this file.
1591 is about missing comments
1573 is about missing <param>
tags in comments.
It seems that AutoRest should generate code which is C# compliant (with no warnings), and that we should have these flags turned on in this repo to ensure that we ship the best possible documentation to our clients.
Cost: 3
Issue Analytics
- State:
- Created 7 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
How can I disable a C/C++ `-Werror` build error in Bazel? ...
The answer is to use the -Wno-error=<name> build flag, as described ... Learn to enable/disable GCC and Clang compiler warnings and options ...
Read more >Buildifier warnings - bazelbuild/buildtools
The native module shouldn't be used in BUILD files. Category name: native-build; Automatic fix: yes; Suppress the warning: # buildifier: disable=native-build.
Read more >Disable warnings during build - support
I have tried list.json in layouts/_default but it is not working. Here is the warning. found no layout file for "JSON" for ...
Read more >C# Compiler Options to report errors and warnings
C# Compiler Options for errors and warnings. These options suppress or enable warnings, and control warnings as errors.
Read more >Why should one want to disable compiler warnings?
There are quite a few reasons to selectively disable compiler warnings, ... the "treat warnings as errors" directive on the build server.
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
Shouldn’t we have 1591 enabled on our actual SDKs? (I don’t really care about tests, just SDKs).
And if the code-generator isn’t generating code with comments, fix the generator so it does?
It seems a pretty reasonable requirement that all public methods have comments in the public SDKs, right?
@kurtzeborn, if the warnings come from generated code, there’s little thing we team could do since current process need service team to generate code. Please feel free to reopen the issue.