Name Conflicts When Importing Protobuf Definitions about ssl-game-controller HOT 2 CLOSED

Thanks for the explanation. I added package to the ssl_gc protobufs and that works in our repo. For C++, package gets compiled into namespaces, so enums aren't a problem at all. For example, assuming package SSL;, the C++ type for the Team protobuf message would be SSL::Team. That fixes my problem, so closing this issue

from ssl-game-controller.

I removed the SSL_ prefix intentionally, because it is not a valid name according to the protobuf naming convention: https://developers.google.com/protocol-buffers/docs/style#message_and_field_names

If you do not want to refactor your code, you can just rename the field in your codebase. The message and field names are not part of the API.

Name conflicts can easily be solved using packages, as the GC does with go_package and for example the TIGERs AutoRef does with package: https://github.com/TIGERs-Mannheim/AutoReferee/blob/master/modules/moduli-referee/src/main/proto/ssl_gc_referee_message.proto#L3

One difficulty are enums indeed. They must be unique outside packages as well. I think that's why the Team is in a common package. Is this an issue in your code base as well? And if so, can't you reuse the Team and/or RobotId?

from ssl-game-controller.