feat: default flat param object #1805
Merged
+120
−51
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I finished a version of the flattened parameter object, but there are still a few questions
MVC:
The default flattening causes test cases to fail. $ref has been changed to properties type, json cannot match. The fail use cases covered are 4, 13, 26, 71, 82, 93, 117, 140, 142
Other use cases have been successed with defaultFlatParamObject=true
WebFlux:
WebFlux uses a lot of Mono, and the flattening operations are in the core package, I'm not sure whether to separate the flattening operations into mvc and webflux.
In short, the behavior is unchanged from before when defaultFlatParamObject set false (default). the parameter object can be automatically flattened under mvc when defaultFlatParamObject set true, so that the description of the field and whether it is required can be viewed on swagger-ui. But defaultFlatParamObject can not set true in webflux.