You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 22, 2024. It is now read-only.
Notice that the second slice is intended to be named grand_children but is really being named children as it is actually named in the struct.
If I step through the mapstructure.Decode function, I can see the tag get read and build an appropriate fieldName as sub_config.first_children[0].grand_children, but that at some point gets shuffled back to children.
We can see in this screenshot the result of the Decode prior to rendering the yaml:
If I'm not mistaken, the
main.go
below should output:Instead, it is outputting:
Notice that the second slice is intended to be named
grand_children
but is really being namedchildren
as it is actually named in the struct.If I step through the
mapstructure.Decode
function, I can see the tag get read and build an appropriatefieldName
assub_config.first_children[0].grand_children
, but that at some point gets shuffled back tochildren
.We can see in this screenshot the result of the
Decode
prior to rendering the yaml:main.go
go.mod
The text was updated successfully, but these errors were encountered: