Kuadrant/kuadrant-console-plugin

Fix hardcoded user-facing strings across policy and resource action hooks

Open

#625 opened on Jul 10, 2026

View on GitHub
 (0 comments) (0 reactions) (1 assignee)TypeScript (63 forks)auto 404
enhancementgood first issuetriage/accepted

Repository metrics

Stars
 (10 stars)
PR merge metrics
 (PR metrics pending)

Description

Summary

Multiple user-facing strings are hardcoded throughout the plugin without being wrapped in the useTranslation t() function, making them untranslatable.

Motivation

The plugin uses i18next for all user-facing strings, but several components bypass this pattern. These need to be consistent before the plugin can be properly localised.

Proposed Solution

Wrap all affected strings with t() and add corresponding keys to locales/en/plugin__kuadrant-console-plugin.json.

Affected Files

Action hooks — label and description strings

  • useDNSPolicyActions.tsx — 'Edit labels', 'Edit annotations', 'Edit', 'Delete'
  • useTLSPolicyActions.tsx — same
  • useOIDCPolicyActions.tsx — same
  • useTokenRateLimitPolicyActions.tsx — same
  • useAPIProductActions.tsx — 'Edit labels', 'Edit annotations', 'Edit APIProduct', 'Delete APIProduct'

Other components

There are also other hardcoded placeholder and aria-label strings across the policy creation form components that should be wrapped with t().

Additional Context

Identified during review of #575. Fix all in one PR for consistency.

Contributor guide

Research direction
Examine the existing i18n setup in the plugin (look at how t() is used in other files). For each file listed, find the hardcoded strings and wrap them with t(). Add the corresponding keys to the English locale JSON file. Also scan the policy creation form components for additional hardcoded placeholder and aria label strings.
Tech stack
typescriptreact
Domain
frontend
Issue type
Refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
JavaScriptTypeScriptGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75