feat(Extensions): Add translation support for Extensions

[lokanandaprabhu]

Translation support to Extensions

Fixes

https://issues.redhat.com/browse/RHIDP-8742

Added internationalization (i18n) support to Extensions. The plugin now supports multiple languages with proper fallbacks and maintains all existing functionality.

• Multi-language support: English (default), German, French, and Spanish

Languages added:

1. 🇫🇷 French (fr)
2. 🇩🇪 German (de)
3. 🇪🇸 Spanish (es)
4. 🇺🇸 English (en) - default

Screenshots

---

---

---

---

✔️ Checklist

• A changeset describing the change and affected packages. (more info)
• Added or Updated documentation
• Tests for new functionality and regression tests for bug fixes
• Screenshots attached (for UI changes)

[rhdh-gh-app]

Important

This PR includes changes that affect public-facing API. Please ensure you are adding/updating documentation for new features or behavior.

Unexpected Changesets

The following changeset(s) reference packages that have not been changed in this PR:

• /home/runner/work/rhdh-plugins/rhdh-plugins/workspaces/marketplace/.changeset/add-marketplace-i18n-support.md: @red-hat-developer-hub/backstage-plugin-marketplace-backend, @red-hat-developer-hub/backstage-plugin-marketplace-common, @red-hat-developer-hub/backstage-plugin-catalog-backend-module-marketplace

Note that only changes that affect the published package require changesets, for example changes to tests and storybook stories do not require changesets.

Changed Packages

Package Name	Package Path	Changeset Bump	Current Version
app	workspaces/marketplace/packages/app	none	v0.0.0
@red-hat-developer-hub/backstage-plugin-marketplace	workspaces/marketplace/plugins/marketplace	minor	v0.9.3

[HusneShabbir]

Tested Locally,
/lgtm

[christoph-jerolimov]

Hey, really nice work, I have just two suggestions:

• You translated a lot of Skeletons usages which is imo not needed. Wdyt?

• I added an idea about removing the Trans component and using MarkdownContent instead.

• And finally, you also translate the Catalog entites. It's nice, but I don't know if we really want that for now.... Really unsure... 🤔

  Can you maybe test if you can alternatively, add a 2nd property to examples/collections/featured.yaml and if we can use that as translation? Maybe its worth to put this into a 2nd PR.

  # yaml-language-server: $schema=../../json-schema/collections.json
  apiVersion: extensions.backstage.io/v1alpha1
  kind: PluginCollection
  metadata:
   namespace: marketplace-plugin-demo
   name: featured
   title: Featured Plugins
   titleKey: collection.featured.title
   description: A set of great plugins! :)
   descriptionKey: collection.featured.description
  spec:
   type: curated
   plugins:
     - quay
     - 3scale
     - tekton
     - topology

  fyi: These collections aren't used yet in our product.

[openshift-ci]

New changes are detected. LGTM label has been removed.

[christoph-jerolimov]

Hi @lokanandaprabhu, this got conflicts after we (I) merged

• #1394

Another bigger PR from @ciiay is WIP that changes again a lot of strings

• #1395

Maybe its best to wait until this is also merged and rebase your changes after that.

Sorry that we worked on 3 important changes at the same time on the same code base... 🤷‍♂️

[christoph-jerolimov]

Awesome work @lokanandaprabhu 👍

Thanks for keeping this updated after the other PRs breaks this.

This lgtm, I would just extract the utils function that was there 3 times. Or remove it. (Final decision in slack... ;))

[sonarqubecloud]

Quality Gate failed

Failed conditions
44.3% Duplication on New Code (required ≤ 3%)

See analysis details on SonarQube Cloud