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
I'm not sure if this might be considered as an issue, since sumo hasn't notion about what a map is, this type not even exist. Currently, Riak's store is assuming nested entities as sumo models, that's the reason why those fields are being transformed to atoms (following the sumo API). Otherwise, how can we know when a nested entity has to be treated as a map and when as a sumo entity? We would need, for instance, create another data type in sumo, e.g.: map. There is an issue related with "custom" types (#186), probably this is the way, once this issue is done, we can do something here.
Riak store changes map's keys to atoms in sumo:find_all(module).
The text was updated successfully, but these errors were encountered: