incorrect assumption in mapstructure library causing panic

[jxsl13]

incorrect assumption in mapstructure library causing panic

[knadh]

Sorry, haven't had a chance to study this. Were you able to figure this out?

[jxsl13]

currently no time due to private reasons, will come back to this maybe next week.

[jxsl13]

the solution is to make the second test pass by updating the CustomTextUnmarshalHookFunc().
This is an extended form of the issue at hand where a
type Foo string not only is a string under the hood (for which the type assertion .(string) does not work) but that custom string type additionally implements both, the TextMarshaler and TextUnmarshaler interfaces which allow the internal string representation (deserialized) to differ from the external string representation (serialized).
The third test is a test to somehow deduce that the value type as well as the pointer type do not implement the TextMarshaler interface.
The third test is a little bit of a playground for the implementation that I need in CustomTextUnmarshalHookFunc() at TODO
A potential direction is to copy the values and have both pointer type and value type (pointer/value receiver) inside of an empty interface (.Interface()) for which you may then try to type assert TextMarshaler.