-
Notifications
You must be signed in to change notification settings - Fork 155
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Automatically detect license links #739
Comments
Another solution could be to introduce a new key for the "custom": {
"modmenu": {
"links": {
"modmenu.license": "https://some-url"
}
}
} The license is generally meant to be a SPDX identifier, which this format would allow. In addition, the license name and link could differ. |
That is impossible for custom licenses. |
I don't believe a link is a valid identifier of a license, the spec is vague and doesn't fully specify but it does recommend using SPDX identifiers. You can denote a custom license in SPDX format using I've brought it up with the Fabric team and I think in v2 they will add support for links and custom names for licenses. I'd be open to adding my own license link field in Mod Menu metadata until that happens though. |
That leads to a worse user experience, imo, as now you would somehow magically need to know where to find "MyCustomLicense". |
Currently, the only way to specify a custom license is to use
"license": "https://some-url"
.While this works fine, modmenu will display it verbatim without the link being clickable.
It would be nice to change this, maybe a simple check like "does the license start with
http://
orhttps://
"The text was updated successfully, but these errors were encountered: