Skip to content

Conversation

@FGYFFFF
Copy link
Contributor

@FGYFFFF FGYFFFF commented Oct 10, 2024

What type of PR is this?

fix

Check the PR title.

  • This PR title match the format: <type>(optional scope): <description>
  • The description of this PR title is user-oriented and clear enough for others to understand.
  • Attach the PR updating the user documentation if the current PR requires user awareness at the usage level. User docs repo

(Optional) Translate the PR title into Chinese.

修复指定 "-t=compatible_names"时带来的handler无法获取正确请求参数的情况

(Optional) More detailed description for this PR(en: English/zh: Chinese).

en: fix: compatible name conflict
zh(optional): 修复指定 "-t=compatible_names"时带来的handler无法获取正确请求参数的情况
"-t=compatible_names" 会改变结构体的命名
image

image

(Optional) Which issue(s) this PR fixes:

(Optional) The PR that updates user documentation:

@FGYFFFF FGYFFFF requested review from a team as code owners October 10, 2024 07:15
@codecov
Copy link

codecov bot commented Oct 10, 2024

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 82.58%. Comparing base (ea445e3) to head (50a7d17).
⚠️ Report is 125 commits behind head on develop.

Additional details and impacted files
@@           Coverage Diff            @@
##           develop    #1206   +/-   ##
========================================
  Coverage    82.58%   82.58%           
========================================
  Files          124      124           
  Lines        11491    11491           
========================================
  Hits          9490     9490           
  Misses        1428     1428           
  Partials       573      573           

☔ View full report in Codecov by Sentry.
📢 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants