Respect NoWarn in project#34
Merged
Merged
Conversation
jnm2
commented
Oct 1, 2019
sharwell
requested changes
Oct 1, 2019
jnm2
commented
Oct 1, 2019
sharwell
reviewed
Oct 2, 2019
sharwell
approved these changes
Oct 3, 2019
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
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.
Closes #31. Confirmed that the warning disappeared after updating to the locally build package using a net35 project with the System.Data warning.
I tested against this weird NoWarn property to verify that I had declared the task property in a valid way.
string[]appears to trigger automatic splitting and trimming.