Support updating mods with pre-release versions

[madtisa]

Let's say we have mod with current version 1.0.0-pre1 and newest 1.0.0-pre2. Coercing would convert both versions to 1.0.0 and update notification won't occur

[IDCs]

I agree with you completely - but I'm afraid that most of our mod authors (not to mention some game developers) will not abide to semantic versioning. This update will fix the update functionality for some games, yet break it for others.

Until the website is in a position to enforce versioning, I'm afraid that specific line of code will remain as is.

[madtisa]

Thanks for quick reply. I see what you mean. In this case, since parse has more strict regex than coerce, how about we would try to parse it first, and if version is "incomplete" we coerce:
https://github.com/madtisa/Vortex/blob/db44babc7a4faf127bcac6b629350349ccbb328f/src/extensions/mod_management/util/versionClean.ts#L4
This way, it shouldn't affect versions that doesn't comply to semver, and would allow to update pre-release mods with proper versions

[madtisa]

Also submitted PR to semver. Hopefully, it would be possible to coerce pre-releases in future by using options

[madtisa]

@IDCs, I'm not familiar with the process of a discussion in this project. Should I create new PR for latest change or is it going to be reviewed in this one eventually? Or should I mention the change in the opened issue and wait?

[madtisa]

@IDCs, PR to node-semver has been approved, but it will take quite some time until it's released. Hopefully, next discussion in PR won't be ignored