incorrectly reading top-level enums as packages about grpcc HOT 12 CLOSED

Ah, I see it now, I moved a few things around and the tests need updating. Shall do so tomorrow!

from grpcc.

I ran into this as well. Another example (names changed and simplified)

message XRequest {
MyEnum val = 1;
string somethingElse = 2;
}
message YRequest {
MyEnum val = 1;
}

enum MyEnum{
EntryOne = 0;
EntryTwo = 1;
}

EDIT:
I think I found a workaround. It's ugly and requires a bit of finagling with the types in classes using the generated c# (not sure about other languages) but so far so good. At least, I seem to be able to call it the same way.
message XRequest {
MyEnumWrapper .MyEnum val = 1;
string somethingElse = 2;
}
message YRequest {
MyEnumWrapper .MyEnum val = 1;
}

message MyEnumWrapper {
enum MyEnum{
EntryOne = 0;
EntryTwo = 1;
}
}

from grpcc.

Sorry for the delay on this, I've just published a big release of grpcc, so please upgrade and check it out. I can no-longer recreate the issue.

Also you may want to take at the new features https://github.com/njpatel/grpcc :)

from grpcc.

@njpatel I see this was just closed with an associated commit but the commit seems to be failing on circle.

I'd add these for test cases in test.proto, haven't gotten around to testing myself yet.

enum EventType {
  TEST = 0;
  TEST_AGAIN = 1;
}

message SayThing {
  enum NumberThing {
    THING_ONE = 0;
    THING_TWO = 1;
  }
}

from grpcc.

Yeah, it worked locally but CircleCI is not loading for me - I get to the main build page but the output won't load. I'm still working on grpcc, so will keep a look out until it's working again.

from grpcc.

+1 I also just ran into this bug. It's a shame, since it prevents me from using the program at all.

from grpcc.

+1

from grpcc.

+1

from grpcc.

+1

from grpcc.

+1 very annoying bug

from grpcc.

Thanks for the update!

from grpcc.

from grpcc.