Properly compare multiple package versions #380
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.
What does it do ?
Fix a silly mistake.
Why is it needed ?
I assumed that the max() function was able to figure out the highest semantic version number, but of course it's not that easy. Gitify selected 1.9.0 instead of 1.11.1 in my latest test, so apparently 1.9 was seen as higher than 1.1.
So the whole semantic version string needs to be picked apart and compared. Fortunately there's a version_compare function available in PHP that does just that, so it's now able to sniff out the actual latest version from the packageVersions array. Regardless of position. It even evaluates -alpha and -beta suffixes, so those should be correctly evaluated now too! They did for me with a test array.
Related issue(s)/PR(s)
#327