Skip to content

Translate hardcoded labels on status page and dashboard - #504

Open
jnk0 wants to merge 3 commits into
cachethq:mainfrom
jnk0:fix-affected-components-label
Open

jnk0 wants to merge 3 commits into
cachethq:mainfrom
jnk0:fix-affected-components-label

Conversation

@jnk0

@jnk0 jnk0 commented Nov 9, 2026 •

Copy link
Copy Markdown
Contributor

The incident and schedule components used __('Affected Components') and a hardcoded ' and ' when listing components. The package ships no JSON translations, so both stayed English in every locale.

Use the existing incident.affected_components_header key and add a cachet.and key for the conjunction.

Also translate the remaining hardcoded labels: the "Reported" entry on the status page, the updates and components relation managers in the dashboard, the incident user field and the metric suffix placeholder.

@jnk0 jnk0 changed the title Translate affected components label on status page Translate hardcoded labels on status page and dashboard Nov 11, 2026
jnk0 added 2 commits November 11, 2026 14:17
The incident and schedule components used __('Affected Components')
and a hardcoded ' and ' when listing components. The package ships no
JSON translations, so both stayed English in every locale.

Use the existing incident.affected_components_header key and add a
cachet.and key for the conjunction.
The reported label on the status page and several dashboard labels
used plain strings such as __('Reported') or fixed English text. The
package ships no JSON translations, so they stayed English in every
locale.

Use existing package keys where available and add an update language
file for the updates relation manager shared by incidents and
schedules, plus a metric suffix placeholder key.
@jnk0
jnk0 force-pushed the fix-affected-components-label branch from d2f5e36 to 7da1f70 Compare November 11, 2026 13:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant