When two message definitions are nested one inside the other, the inner one is translated like a part of the outer's label, creating a syntax error.
message User {
message Attributes {
optional fixed32 created_at = 1;
optional fixed32 updated_at = 2;
}
optional uint32 id = 1;
optional string name = 2;
optional Attributes attributes = 3;
}
Not sure how this should be visualized, though.
When two message definitions are nested one inside the other, the inner one is translated like a part of the outer's label, creating a syntax error.
Not sure how this should be visualized, though.