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
add license slug #18361
Comments
I tried to test this using the info for license slugs from the docs. I ran quickly into 429 Too Many Requests while making PATCH requests on versions endpoint, sending license slugs. I don't know what's the new rule on throttles and I don't think I can override it as an admin.
|
@ioanarusiczki it was the fix for #18122 (that just got reverted) |
@eviljeff I tried to send {"license": "LGPL-3.0-or-later"} but I get a 400 "Invalid value". I checked the admin and I see "GNU Lesser General Public License, version 3.0" with the URL http://www.gnu.org/licenses/lgpl-3.0.html being available. The other similar license with "LGPL-2.1-or-later" is alright. Maybe the slug for 3.0 is not correct? |
eek, you're right - the slug is wrong. I'll have to fix it. |
for the addon submission api license implementation #18034 we need some way for an api client to be able to specify a pre-defined license. We have a license
id
(the license record pk), and abuiltin
integer (if>0
used to indicate the license is pre-defined, and to enumerate the choices), but neither is particularly user-friendly. Ideally we'd have a slug, for examplempl2
,bsd
,cc
, etc, for the non-custom licenses.The text was updated successfully, but these errors were encountered: