Using message as a value in Map seems to break deserialisation

[Arttii]

Hi,

I am not sure if this is a misunderstanding on my part of some bug, but when using the following message definition:

message Stuff {
  map<string, data.structs.v1.Team> teams = 1;
  
}

nested in another message, leads to errors when decoding, I am getting the following error:

cannot decode map value for field package.structs.v1.Stuff.teams from JSON: object

The Team message itself has another map inside it, maybe that is somehow the culprit? The generation itself works fine.

Is this expected behaviour? Am I doing something wrong?

[timostamm]

Hey @Arttii, we have tests for map fields with messages (see here) and are not aware of any issues with them.

Can you provide a reproducible example?

[Arttii]

So this wont have a problem even if the message has another map in it right? In that case, maybe its something on my side. Thanks for the support.