Skip to content

fix(domain): read a release's contact the same way in the Studio - #832

Merged
ixuz merged 1 commit into
mainfrom
fix/one-release-contact
Nov 16, 2026
Merged

ixuz merged 1 commit into
mainfrom
fix/one-release-contact

Conversation

@ixuz

@ixuz ixuz commented Nov 15, 2026

Copy link
Copy Markdown
Member

What and why

The Studio's Contact field showed the web page of the first contact point of a release, blank nodes included, while the learner app's "Report a mistake" followed the first contact point that is named. A release that names more than one contact point could so show its creator one contact in the Studio and send learners to another once published.

Both now read a release's contact the same way: the one contact point, named or blank, with one web page. A release that names more than one contact point, or a point with more than one web page, names no contact, so "Report a mistake" has no page to lead to and the Contact field is empty. The release check warns of such a release in a pod and for the library (contactAmbiguous), in every language the Studio speaks. Setting the contact again still writes exactly one point, and a release made a draft keeps its points as they are, for the check to show. The Studio and library docs say so.

Refs: GHSA-g8xv-c484-62vx

The Studio's Contact field showed the web page of the first contact
point of a release that names one, blank nodes included, while the
learner app's "Report a mistake" followed the first contact point that
is named. A release that names more than one contact point could so
show its creator one contact in the Studio and send learners to
another once published.

Both now read a release's contact the same way: the one contact point,
named or blank, with one web page. A release that names more than one
contact point, or a point with more than one web page, names no
contact, so "Report a mistake" has no page to lead to, and the Contact
field is empty. The release check warns of such a release in a pod and
for the library (contactAmbiguous), in every language the Studio
speaks. Setting the contact again still writes exactly one point, and
a release made a draft keeps its points as they are, for the check to
show. The Studio and library docs say so.

Refs: GHSA-g8xv-c484-62vx
@ixuz ixuz added bug Something isn't working i18n labels Nov 15, 2026
@ixuz
ixuz enabled auto-merge November 15, 2026 23:48
@ixuz
ixuz added this pull request to the merge queue Nov 16, 2026
Merged via the queue into main with commit 601f4f3 Nov 16, 2026
53 checks passed
@ixuz
ixuz deleted the fix/one-release-contact branch November 16, 2026 00:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working i18n

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant