I looked it up, and Red Hat says that YAML is a superset of JSON, and all the data can be parsed in JSON format.

In issue , a user told me that parsing is normal behavior

I set out to fix the test case.

Hello, please take a look at the PR I submitted and give me some feedback. This PR provides 4 types of shortcuts to ShouldBindBodyWith, which are JSON, YAML, XML, and TOML.

Take a look at this PR, please. @appleboy @thinkerou @manucorporat

I will take a look.

@RedCrazyGhost Please help to fix lint error.

@RedCrazyGhost Please help to fix lint error.

@appleboy Thanks for your help, I am trying to fix the error in lint, I have committed fix commit.

Hello, can you help me start the approval flow? @flc1125

Hello, can you help me start the approval flow? @flc1125

I'm not a project member and can't help you. Thanks~

Hello, can you help me start the approval flow? @flc1125

I'm not a project member and can't help you. Thanks~

Okay, I see. Sorry to bother you.

@appleboy Hello, please approve the workflow if you have time

Codecov Report

Attention: Patch coverage is 80.00000% with 2 lines in your changes are missing coverage. Please review.

Project coverage is 99.18%. Comparing base (3dc1cd6) to head (d7acf06).
Report is 30 commits behind head on master.

@@            Coverage Diff             @@
##           master    #3871      +/-   ##
==========================================
- Coverage   99.21%   99.18%   -0.03%     
==========================================
  Files          42       43       +1     
  Lines        3182     2709     -473     
==========================================
- Hits         3157     2687     -470     
+ Misses         17       12       -5     
- Partials        8       10       +2     

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

Do I need to pay attention to the CodeCov bot detection report?

Adding new method shortcuts results in a substantial drop in coverage.
@appleboy

This codecov detection result is not the same as the result of go test coverage.

This makes me very confused!

I don't know how to solve this patch coverage? @appleboy

termial use code:

$ go test -coverprofile=coverage.out ./...

$ go tool cover -html=coverage.out

@RedCrazyGhost I've checked the tests myself, so I won't refer to the data from codecov. :) Thanks.

@RedCrazyGhost I've checked the tests myself, so I won't refer to the data from codecov. :) Thanks.

Thank you for your support throughout.