v1.2.0: Support packages.config and exclude the attributes from code coverage by default #7
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.
v1.2.0
This release provides solutions for issue #1 and
issue #6. In addition, potential compiler
warnings in the
NullableAttributes.cs
file are now hidden.Upgrading:
Remove any previously defined
NULLABLE_ATTRIBUTES_EXCLUDE_FROM_CODE_COVERAGE
compiler constant,as it does not have any effect anymore.
Details:
packages.config
via acontent/
folder in the NuGet package.When referenced from projects targeting .NET Standard >= 2.0 or .NET Framework >= 4.0, the
ExcludeFromCodeCoverageAttribute
is used. For other project types, theDebuggerNonUserCodeAttribute
is used.
NULLABLE_ATTRIBUTES_INCLUDE_IN_CODE_COVERAGE
compiler constant whichremoves the code coverage attributes.
NULLABLE_ATTRIBUTES_EXCLUDE_FROM_CODE_COVERAGE
compiler constant no longer hasany effects. Code coverage is now disabled by default.
NullableAttributes.cs
file now wraps the attributes with a#pragma warning disable
and#pragma warning restore
block to disable both compiler- and code-analysis warnings.