Is your feature request related to a problem? Please describe.
There was a bug where a reflect.Value was wrapped into another reflect.Value, which led to invalid url queries: #14798 .
Though the commit 117e511 solves this problem in a straightforward manner, by unwrapping the reflect.Value to interface{}, it does not seem very "future proof", in the meaning that any other future used reflect.Value, also needs unwrapping.
Describe the solution you'd like
Modify the parameterAddToHeaderOrQuery function in the client golang template to always check if the value to wrap is of reflect.Value and skipping if its true:
// previously: var v = reflect.ValueOf(obj)
var v reflect.Value
if refValue, ok := obj.(reflect.Value); ok {
v = refValue
} else {
v = reflect.ValueOf(obj)
}
Describe alternatives you've considered
Not doing anything, as the bug itself is fixed and does not warrant any further action.
Additional context
None
Is your feature request related to a problem? Please describe.
There was a bug where a reflect.Value was wrapped into another reflect.Value, which led to invalid url queries: #14798 .
Though the commit 117e511 solves this problem in a straightforward manner, by unwrapping the reflect.Value to interface{}, it does not seem very "future proof", in the meaning that any other future used reflect.Value, also needs unwrapping.
Describe the solution you'd like
Modify the parameterAddToHeaderOrQuery function in the client golang template to always check if the value to wrap is of reflect.Value and skipping if its true:
Describe alternatives you've considered
Not doing anything, as the bug itself is fixed and does not warrant any further action.
Additional context
None