Open GoNextGroup opened 4 months ago
I think this comes down to name collisions; we should add a mode that optionally includes the enum name as a prefix in all enum names (including zero), so we generate TokenType_Zero, TokenType_Temporary, etc
unrelated: you might want to look at https://protobuf-net.github.io/protobuf-net/compatibilitylevel re the data and guid
Thank you for your answer. Currently, I'll try to change ordering of elements starting from 0. Is it possible in future releases to change enum members generation style? Because the same collision can be in cases when 2 enums contain elements with same names.
Is it possible in future releases to change enum members generation style? Because the same collision can be in cases when 2 enums contain elements with same names.
Yes, that is what I was proposing - sorry if that was unclear.
Thank you! I'll wait for new release)))
Why is this closed?
Why is this closed?
Sorry, my bad.
Hello, Marc.
I try to use reflection in my project, but got problem with enums.
I have service with request record:
The proto file was generated:
So, when I try to use command docker run fullstorydev/grpcurl -plaintext -use-reflection 172.23.17.107:50029 describe SharedInterfaces.TokenService.SecurityInterfaces.Token.TokenGeneration
I got a message Failed to resolve symbol "SharedInterfaces.TokenService.SecurityInterfaces.Token.TokenGeneration": proto: descriptor "SharedInterfaces.TokenService.SecurityInterfaces.Token.ZERO" already declared
I've tried to find solution in the internet/SO/tg chats, but without any success. Could you help me to fix this problem? Or is there no way just only change enum elements order starting not from 1, but from 0?