-
Notifications
You must be signed in to change notification settings - Fork 698
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support floating prerelease and stable packages at the same time with the same version range (enable absolute latest scenario) (*-*) #3247
Conversation
…into dev-nkolev92-w
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🍕
Thanks for the review @awesley. :) |
b9882c7
to
dad63c9
Compare
var valid = FloatRange.TryParse(floatVersionString, out range); | ||
|
||
// Assert | ||
Assert.True(valid); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can range verification added in the test as well?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you clarify what specifically you are referring to?
test/NuGet.Core.Tests/NuGet.Versioning.Test/FloatingRangeTests.cs
Outdated
Show resolved
Hide resolved
test/NuGet.Core.Tests/NuGet.Versioning.Test/FloatingRangeTests.cs
Outdated
Show resolved
Hide resolved
test/NuGet.Core.Tests/NuGet.Versioning.Test/FloatingRangeTests.cs
Outdated
Show resolved
Hide resolved
test/NuGet.Core.Tests/NuGet.Versioning.Test/VersionRangeFloatParsingTests.cs
Show resolved
Hide resolved
@donnie-msft Addressed feedback in the latest commit. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@donnie-msft Addressed feedback in the latest commit.
Resolved the accepted comments, replied to the other 2.
Thanks. Looks good, but I'll let someone else approve to overrule on the coding guideline.
I have change the test names and moved them around in better classes as per what I suggested in the TODO that @donnie-msft commented on #3247 (comment). PTAL. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. Just style and variable assigments comments.
test/NuGet.Core.Tests/NuGet.Versioning.Test/FloatingRangeTests.cs
Outdated
Show resolved
Hide resolved
I broke my tests somehow :( |
I had an off by 2 error. Will merge once tests are green. |
Bug
Fixes: NuGet/Home#912
Regression: No
Fix
Details: Spec at https://github.com/NuGet/Home/blob/dev/designs/FloatingStableAndPrerelease.md
You can test out the implementation at the following link
Testing/Validation
Tests Added: Yes
Reason for not adding tests:
Validation: Lots of unit tests, covering all scenarios.