When different messages have nested enums sharing the same name, those enums are visualized as one linked to all the parent messages.
For example, the following code
message Post {
enum Type {
ARTICLE = 1;
BLOG = 2;
}
required Type type = 1;
}
message User {
enum Type {
GUEST = 1;
MEMBER = 2;
}
required Type type = 1;
}
produces one Type node linked to both User and Post, when in reality those are two different entities.
On an unrelated note, the enum values are not visualized at all — is there any way I can get them to be listed the same way as message fields?
When different messages have nested enums sharing the same name, those enums are visualized as one linked to all the parent messages.
For example, the following code
produces one Type node linked to both User and Post, when in reality those are two different entities.
On an unrelated note, the enum values are not visualized at all — is there any way I can get them to be listed the same way as message fields?