[Bug] 实付金额在 USD 展示模式下仍显示"元"(CNY)

Open Beginner friendly
#3,196 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Quiet
Tech stack
javascript
Domain
frontend

Research direction

Start in web/src/components/topup/index.jsx, inspect the renderAmount function and how PaymentConfirmModal uses it. Check how quota_display_type is available in the recharge view, then verify that USD mode displays the amount with “USD” instead of “元” in both locations.

Written by the indexing model from the issue text.

Description

bug

Routine Checks

  • I have confirmed there are no similar issues currently
  • I have confirmed I have upgraded to the latest version
  • I have thoroughly read the project README, especially the FAQ section
  • I understand and am willing to follow up on this issue, assist with testing and provide feedback
  • I understand and acknowledge the above, and understand that project maintainers have limited time and energy, issues that do not follow the rules may be ignored or closed directly

Issue Description

运营设置 → 额度展示类型设为 USD → 充值页面顶部"实付金额"仍显示 x 元

Steps to Reproduce

web/src/components/topup/index.jsx 的 renderAmount 函数硬编码了 元,未读取 quota_display_type,PaymentConfirmModal 也用了同一函数,同样受影响

Expected Result

运营设置 → 额度展示类型设为 USD → 充值页面顶部"实付金额"显示为 “x USD”

Dominant language
Go
Stars
48.5k
Forks
11.6k
Avg merge
1d 9h
Merged PRs (30d)
61

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from QuantumNous/new-api

All issues in QuantumNous/new-api

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.