Skip to content

fix(web): align marketplace i18n terminology#37837

Queued
Jingyi-Dify wants to merge 1 commit into
mainfrom
fix/marketplace-copy-i18n
Queued

fix(web): align marketplace i18n terminology#37837
Jingyi-Dify wants to merge 1 commit into
mainfrom
fix/marketplace-copy-i18n

Conversation

@Jingyi-Dify

Copy link
Copy Markdown
Contributor

Important

  1. Make sure you have read our contribution guidelines
  2. Ensure there is an associated issue and you have been assigned to it
  3. Use the correct syntax to link this PR: Fixes #<issue number>.

Summary

Fixes SNP-487

Linear issue: https://linear.app/dify/issue/SNP-487/onboarding-体验重构-marketplace-翻译检查

  • Keep Marketplace untranslated and properly spaced in Simplified and Traditional Chinese copy.
  • Align Marketplace page wording from plugins to integrations for the visible hero, tabs, and empty state.
  • Keep Japanese Marketplace copy consistent with the 1.14 localization style while syncing the dataset-pipeline integration wording.

Screenshots

N/A. This PR only updates i18n copy.

Checklist

  • This change requires a documentation update, included: Dify Document
  • I understand that this PR may be closed in case there was no previous discussion or issues. (This doesn't apply to typos!)
  • I've added a test for each change that was introduced, and I tried as much as possible to make a single atomic change.
  • I've updated the documentation accordingly.
  • I ran make lint && make type-check (backend) and cd web && pnpm exec vp staged (frontend) to appease the lint gods

Verification:

  • Parsed all 19 changed i18n JSON files successfully.
  • Verified 30 English visible Marketplace strings map to Chinese copy containing capitalized Marketplace with no CJK adjacency.
  • Verified Japanese Marketplace copy has no remaining English Marketplace in the corresponding visible strings.
  • Ran git diff --check.
  • Pre-commit hook ran eslint --fix --pass-on-unpruned-suppressions on staged files.

From Codex

@Jingyi-Dify Jingyi-Dify requested a review from iamjoel as a code owner June 23, 2026 19:37
@dosubot dosubot Bot added the size:XS This PR changes 0-9 lines, ignoring generated files. label Jun 23, 2026
@github-actions github-actions Bot added the web This relates to changes on the web. label Jun 23, 2026
@codecov

codecov Bot commented Jun 23, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 85.61%. Comparing base (50b3228) to head (352c2b6).
⚠️ Report is 5 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main   #37837   +/-   ##
=======================================
  Coverage   85.61%   85.61%           
=======================================
  Files        5032     5032           
  Lines      257481   257481           
  Branches    48888    48888           
=======================================
  Hits       220444   220444           
  Misses      32803    32803           
  Partials     4234     4234           
Flag Coverage Δ
dify-ui 94.94% <ø> (ø)
web 85.63% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@dosubot dosubot Bot added the lgtm This PR has been approved by a maintainer label Jun 24, 2026
@lyzno1 lyzno1 added this pull request to the merge queue Jun 24, 2026
Any commits made after this event will not be merged.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

in-linear lgtm This PR has been approved by a maintainer size:XS This PR changes 0-9 lines, ignoring generated files. web This relates to changes on the web.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants