Skip to content

fix(form): fix container image field typo (en)#725

Open
thornsberrysara wants to merge 1 commit intokubero-dev:mainfrom
thornsberrysara:fix/container-field-typo
Open

fix(form): fix container image field typo (en)#725
thornsberrysara wants to merge 1 commit intokubero-dev:mainfrom
thornsberrysara:fix/container-field-typo

Conversation

@thornsberrysara
Copy link
Copy Markdown

Description

Fixed a typo in the English locale file where "Conmtainer Image" was misspelled as "Conmtainer" instead of "Container". This typo appeared in the app form labels, specifically in the containerImage field label.

Summary: Corrected the spelling of "Container Image" in the English translation file (client/src/locale/en.ts).

Motivation: This typo was visible in the UI when users were configuring container images for their apps, which could be confusing and unprofessional.

Dependencies: None required. This is a simple text correction.

Fixes # (issue)

Type of change

Please delete options that are not relevant.

  • Template (non-breaking change which adds a template)
  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

  • I've built the image and tested it on a kubernetes cluster

Test Configuration:

  • Operator Version: N/A (UI-only change)
  • Kubernetes Version: N/A (UI-only change)
  • Kubero CLI Version (if applicable): N/A

Testing Steps:

  1. Navigate to the app creation/edit form in the Kubero UI
  2. Verify that the "Container Image" field label is now spelled correctly (previously showed "Conmtainer Image")

Checklist:

  • I removed unnecessary debug logs
  • My code follows the style guidelines of this project
  • I have performed a self-review of my code
  • I documented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings

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