Support the "Multiple versions without translations (/<version>/<filename>)" versioning scheme

[edgarrmondragon]

Currently only two schemes are supported by this action:

actions/preview/scripts/edit-description.js

Lines 20 to 24 in 43ac444

	if (RTD_SINGLE_VERSION === "true") {
	RTD_URL = RTD_PROJECT_DOMAIN;
	} else {
	RTD_URL = RTD_PROJECT_DOMAIN + `${RTD_PROJECT_LANGUAGE}/${PR_NUMBER}/`;
	}

Which correspond to "Single version without translations (/<filename>)" and "Multiple versions with translations (/<language>/<version>/<filename>)" respectively.

Fix might be adding a new option (e.g. no-translations) or a special value none for project-language, and use that in a condition to build the right URL.

[edgarrmondragon]

I can probably take some time to submit a PR in the coming days, would that be of interest to you @humitos?

[humitos]

I think we should add a new attribute called "versioning-scheme" (which is what the APIv3 uses https://docs.readthedocs.io/en/stable/api/v3.html#project-details) and base the URL on that.

[humitos]

Also, now that APIv3 is open and un-authed, we could propbably only ask the user for the slug and get all the required information from the API endpoint instead. So, we may need to re-think this action a little more in depth.

[edgarrmondragon]

Also, now that APIv3 is open and un-authed, we could propbably only ask the user for the slug and get all the required information from the API endpoint instead. So, we may need to re-think this action a little more in depth.

I see, that makes sense. Seems like with the response from https://readthedocs.org/api/v3/projects/<slug>/ we could get rid of 2 settings

• single-version -> versioning_scheme
• project-language -> language.code

[stsewd]

Also, now that readthedocs/readthedocs.org#11485, we could propbably only ask the user for the slug and get all the required information from the API endpoint instead. So, we may need to re-think this action a little more in depth.

We shouldn't rely on this API for all projects, on .com projects are private, and we can't hit the API directly for those without auth.

[edgarrmondragon]

Also, now that readthedocs/readthedocs.org#11485, we could propbably only ask the user for the slug and get all the required information from the API endpoint instead. So, we may need to re-think this action a little more in depth.

We shouldn't rely on this API for all projects, on .com projects are private, and we can't hit the API directly for those without auth.

Gotcha. It's probably better then to deprecate single-version in favor of versioning-scheme, for example.