refactor: ignore CS[1591,0618,0105,0672] on reactiveui-events because that code is codegened #1187
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… that code is codegened reduces spam in the CI build log
glennawatson
pushed a commit
that referenced
this pull request
Mar 23, 2019
… that code is codegened (#1187) reduces spam in the CI build log
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
refactor/chore on
reactiveui-eventsWhat is the current behavior? (You can also link to an open issue here)
CS[1591,0618,0105,0672] are enabled and spam the build logs with useless information which makes reviewing the logs harder. We don't need these warnings because
reactiveui-eventsis all automatically code generated.What is the new behavior (if this is a feature change)?
CS[1591,0618,0105,0672] are disabled
Does this PR introduce a breaking change?
No
Please check if the PR fulfills these requirements
Other information: