Fix HasValueX incorrectly returning true #676
Merged
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.
Overview
As per issue #675, when a whitespace string is passed to the
Values(params object[] items)
orValues(IEnumerable<object?> items)
constructors of any of theValues<>
classes, theHasValueX
property will returntrue
, where the correspondingValueX
will be empty.Primary changes
this.HasValueX
evaluation and assignment to afterthis.ValueX
assignment.Ancillary changes
.editorconfig
to redefine new Roslyn analysers, ensuring that newer warnings don't fail the build.Schema.NET.Test
,AssertEx.Empty<T>(OneOrMany<T> collection)
, which addresses the instances where the compiler was implicitly usingstring
forAssert.Empty(OneOrMany<string>)
, instead of treating the input as an enumerable.