Skip to content

fix: account settings, extension names not translated#2595

Open
AlexAndBear wants to merge 1 commit into
mainfrom
issues/2594
Open

fix: account settings, extension names not translated#2595
AlexAndBear wants to merge 1 commit into
mainfrom
issues/2594

Conversation

@AlexAndBear
Copy link
Copy Markdown
Member

Description

image

Related Issue

How Has This Been Tested?

  • test environment:
  • test case 1:
  • test case 2:
  • ...

Types of changes

  • Bugfix
  • Enhancement (a change that doesn't break existing code or deployments)
  • Breaking change (a modification that affects current functionality)
  • Technical debt (addressing code that needs refactoring or improvements)
  • Tests (adding or improving tests)
  • Documentation (updates or additions to documentation)
  • Maintenance (like dependency updates or tooling adjustments)

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR addresses untranslated extension point labels shown in the Account → Extensions settings page by translating the extension name before rendering it in the table.

Changes:

  • Wrap extensionPoint.userPreference.label with $gettext(...) when rendering the “Extension name” column.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment on lines +27 to 29
<oc-table-td>{{ $gettext(extensionPoint.userPreference.label) }}</oc-table-td>
<oc-table-td v-if="extensionPoint.userPreference.description">
<span v-text="$gettext(extensionPoint.userPreference.description || '')" />
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Untranslated strings

2 participants