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.
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
Better API version parsing. #1020
Better API version parsing. #1020
Changes from all commits
753d29f
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Here's an easier mapping to blang/semver
v1alpha3 -> 1.0.0-alpha.3
v1 -> 1.0.0
v2beta3 -> 2.0.0-beta.3
v2beta4 -> 2.0.0-beta.4
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.
Once we map it to blang/semver, we can remove the comparison logic and just reuse that library's
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.
I think it's prefer to keep it this way rather than turn this into a semver and reparse with blang - I tried it and it's about the same amount of code. Let's see what others think though, I'm not sure one is clearly better than the other.
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.
i wrote it up quick at #1026, take a look
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.
My 2 cents:
The two solution seem pretty comparable, but I like the blang/semver version more because it seems like that the K8s versioning is a subset of semver, hence the abstraction is correct.
The lib will take care of version ordering after the mapping - and for the other blang/semver functionality - like range parsing - will be available, only we'd have to do similar mapping but could be useful and then we don't have to write tests for our own ordering.
One issue for example with Dan's approach already is that "v1" is not supported. "ga" is not following the K8S versioning either. By mapping
<alpha/beta>X
to Semver's pre-release numbers, this goes away automatically.One problem I see with our approach is that there is no minor version numbers - but we made that call when we went with the K8S versioning.