Closed zachmargolis closed 8 years ago
Another option would be to add a compiler env var flag to just use the raw name instead, would simplify a lot of the code
Ex: PB_RAW_RPC_NAMES=true
or something
Looks good to me. I'm looking to get some of these bigger PRs merged first, but I'll grab this after.
@zachmargolis this code is also probably broken if the rpc names collide when underscored, right? Like in this issue: https://github.com/grpc/grpc/issues/5812
@embark I'll redo this with the env var flag outlined above -- maybe we could make the "raw" name the default behavior in the near future
Added one comment about naming, but otherwise this is :+1: to me. Let's get this fixed/ merged and then release a pre. I'm not sure if it should be 3.7.0.pre0
or 4.0.0.pre0
but it's much too late to debate about that for tonight. If you have an opinion one way or the other, let me know :).
Thanks, looks good!
Done! Used PB_USE_RAW_RPC_NAMES
Grrr. Looks like rubo:cop: has a new release out.
How did Rubocop change? Looks like the version was pinned in the gemspec back in 86ef9075a2115904b59612c6152717c475164ea9
Looks like the ruby parser gem had a breaking changed released as a patch verison https://github.com/bbatsov/rubocop/pull/2984#issuecomment-201334316. I'm not able to lock it down and fix it though, so I'm honestly not sure what the issue is. I'll let them sort it out.
:shipit:
Thank you for your PR, btw :)
3.7.0.pre0
has been released.
cc @nerdrew @embark
We found some RPC names that were not the same in a roundtrip of
name.underscore.camelize
so this preserves the raw data