Fix Analyzer Tags - #1216
Merged
Merged
Conversation
…ers for the analyzers being unset which triggered fixing of messages and release tracking
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Fix Analyzer Tags
Description
Some analyzers required the
CompilationEndtag for them to show up in the IDE. Rules that fired in the build would appear in the output, but not the in the Error List. It's a simple, non-functional change to make this addition. In doing so, the analyzers for analyzers were discovered to be misconfigured. Correcting that uncovered a few minor issues; specifically, message format and analyzer tracking. These are also now fixed. These changes result in a patch version bump for several packages.