Currently, dependencies are stored in such a way that requires the version you wish to depend on (or mark as your minimum version) has to be uploaded in order for it to be a dependency.
The suggestion is to change this to a SemVer string as opposed to an version ID. suggested structure is as follows:
[
{
"parentId": 1
"sv": "^1.0.0"
}
]This would allow for uploaders to specify what exactly their dependencies are and allows for full support of the SemVer spec.
Migration plan would be that the selected version is used as the basis (e.g. modId -> parentId & modVersion -> sv: "^${modVersion}")
Currently, dependencies are stored in such a way that requires the version you wish to depend on (or mark as your minimum version) has to be uploaded in order for it to be a dependency.
The suggestion is to change this to a SemVer string as opposed to an version ID. suggested structure is as follows:
[ { "parentId": 1 "sv": "^1.0.0" } ]This would allow for uploaders to specify what exactly their dependencies are and allows for full support of the SemVer spec.
Migration plan would be that the selected version is used as the basis (e.g.
modId->parentId&modVersion->sv: "^${modVersion}")