-
Notifications
You must be signed in to change notification settings - Fork 36
semver inconsistencies #181
Comments
I think forcing semver via the schema and fixing the non-conforming mod versions is a good approach here. The semver spec provides a regex that could be used in schema.json to enforce valid semver: LocalVideoPlayerVolume 1.0.0.1 and GenericSettings 1.0.0.2 concern me, as I'm not certain truncating the 4th number is the correct way of dealing with this. As far as I can tell there are no code changes in LocalVideoPlayerVolume between 1.0.0.0 and 1.0.0.1, but the fact the that the dlls are named |
yep I saw that too with the 4th number, maybe it would be fine to just put the 4th number into the 3rd instead since in all cases where it matters the 3rd is 0 also im guessing |
wow I am trying to find some documentation on semver ranges (we use them in dependencies and conflicts) and I can't actually find anything official, and finding any regex for it seems basically impossible... |
iirc semver ranges aren't actually part of semver? They're an extra thing a few dependency managers (npm, cargo, etc) do. |
yes I have found that out now, but there is a wip on their github repo on a separate branch |
ok I took the regex from the semver spec, and turned it into a fairly basic version range regex https://regex101.com/r/NDQ4J8/1 though I have no clue how to turn either of those into a regex |
some entries in the manifest don't use semver correctly (semver has exactly 3 parts, while some versions have 4 or even 2)
I think either the manifest schema on the website should be updated to mention that semver isn't really respected
or the incorrect semvers should be fixed up.
I have made a fork with all the semvers fixed up master...art0007i:neos-mod-manifest:patch-4
The text was updated successfully, but these errors were encountered: