Fixed newer packages mistakenly considered as older #30
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.
I had this prompt while using the program today.
After investigating the code, I realized that the number after the
.r
is being ignored.With this exact setup (where
oldVersion
andnewVersion
are in the form of456.r4x-1
), theoldVer
andnewVer
arrays becomes the same, and returns false.I made a simple fix for now, but it probably needs a deeper look. I couldn't find any reliant package version conventions online, and I am not sure how the program should behave if the
.rXX
is being added or removed. For now, I just checked if it existed on both versions.