-
Notifications
You must be signed in to change notification settings - Fork 280
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When using the @GetMapping("/path/{para}") annotation to pass parameters, the generated HTML reports an error during interface debugging. #103
Comments
@NeverKnowsTomorrow Does the |
@shalousun, I didn't quite understand your point. Could you please describe it in more detail? |
@NeverKnowsTomorrow, the question is whether simple types like String and Integer on the controller need to be converted to underscore format. |
@shalousun, does the test support path parameters? For example:
In the generated documentation test, there are no path parameters, that is, the parameters declared by PathVariable are ignored.
I am using version 2.3.6.
The configuration file is as follows:
Because the test parameters are not listed in the editable request parameters, the path parameters in the test request are not replaced, so the request address directly becomes xxx/xxx/{paramter}, which will reproduce the problem encountered by the person who posted the question originally |
@NeverKnowsTomorrow @hetylei Path parameters are not converted; essentially, they are just placeholders. |
Your Environment(您的使用环境)
Expected Behavior(您期望的结果)
Current Behavior(当前结果)
The generated HTML API documentation throws an error during interface debugging.
API response result:
Possible Solution(bug解决建议)
Sure, here is the translation to English:
Steps to Reproduce (Bug Generation Steps, please try to provide test case code)
"requestFieldToUnderline"
totrue
.@GetMapping("/path/{para}" )
to pass parameters.Send Request
in the generated HTML interface documentation to request the interface.Context (Description of how the bug affects you)
It has been verified that there is no problem when the parameter
"requestFieldToUnderline"
is set tofalse
.The text was updated successfully, but these errors were encountered: