Is there an existing issue for this?
Current Behavior
If there are unexported fields in a struct, it throws a panic.
Context: I'm upgrading the version from 1.2.1 to 1.4.1
reflect: reflect.Value.Set using value obtained using unexported field\n\ngoroutine 447 [running]:\nruntime/debug.Stack()\n
Expected Behavior
No panic.
Steps To Reproduce
In the destination struct, have some unexported fields, maybe pointers.
Anything else?
No response
Is there an existing issue for this?
Current Behavior
If there are unexported fields in a struct, it throws a panic.
Context: I'm upgrading the version from 1.2.1 to 1.4.1
reflect: reflect.Value.Set using value obtained using unexported field\n\ngoroutine 447 [running]:\nruntime/debug.Stack()\n
Expected Behavior
No panic.
Steps To Reproduce
In the destination struct, have some unexported fields, maybe pointers.
Anything else?
No response