Make CompatibilityCollector able to parse a single version String - #1446
Merged
Christoph Bergmeister (bergmeister) merged 1 commit intoApr 17, 2020
Conversation
Copy link
Copy Markdown
Collaborator
Sorry, something went wrong.
Rob Holt (rjmholt)
approved these changes
Apr 17, 2020
Copy link
Copy Markdown
Contributor
|
Thanks for this Christoph Bergmeister (@bergmeister)! |
Sorry, something went wrong.
Copy link
Copy Markdown
Collaborator
Author
|
You're welcome, it was a relatively easy fix |
Sorry, something went wrong.
6 tasks
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
Reviewers
1 more reviewer2 participants
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.
PR Summary
Make CompatibilityCollector able to parse a single version String.
I found it odd that the version number is -1 when not being specified (System.Management.Automation.SemanticVersion uses a 0 in that case) but I tried to be at least consistent with the current implementation...
PR Checklist