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 was archived by the owner on Jul 22, 2024. It is now read-only.
Repository navigation
This repository was archived by the owner on Jul 22, 2024. It is now read-only.
Hm yes, this is intended and I think would be a breaking change to change the default. By decoding to a map[string]interface{} you are saying that the value interface{} is anything that can be assigned to it. mapstructure realizes that it can decode directly onto there, which I think is arguably correct.
I'd be open to an enhancement that introduces a new option to "prefer maps" basically in this scenario.
Given that this project is being officially forked to https://github.com/go-viper/mapstructure (see #349) I'd suggest that this issue (and associated PR) be opened against that project now.
Activity
mitchellh commentedon Apr 20, 2022
Hm yes, this is intended and I think would be a breaking change to change the default. By decoding to a
map[string]interface{}you are saying that the valueinterface{}is anything that can be assigned to it. mapstructure realizes that it can decode directly onto there, which I think is arguably correct.I'd be open to an enhancement that introduces a new option to "prefer maps" basically in this scenario.
dangra commentedon Feb 12, 2023
#314 looks like a perfect fix for this and much wanted :)
jchunkins commentedon Jun 19, 2024
Given that this project is being officially forked to https://github.com/go-viper/mapstructure (see #349) I'd suggest that this issue (and associated PR) be opened against that project now.