I've added an enum at the root of the package of a proto file and the grpc options for

Something like... <div class="snippet-clipboard-content notranslate position-relat

Dupe of <a class="issue-link js-issue-link" data-error-text="Failed to load title" dat

Closing as dupe of <a class="issue-link js-issue-link" data-error-text="Failed to load

Unable to find package when enum is present at root of package. about grpcc HOT 6 CLOSED

njpatel commented on June 3, 2024 1

Unable to find package when enum is present at root of package.

from grpcc.

Comments (6)

yukw777 commented on June 3, 2024

Instead of parsing through the proto file, wouldn't it be easier to add an option to pass in the package name?

from grpcc.

Disturbing commented on June 3, 2024

Can you provide example? Also the service name does not show up as an option when you have enum as base so, it may be bugging out.

…

On Wed, Sep 27, 2017 at 6:00 AM Peter Yu ***@***.***> wrote: Instead of parsing through the proto file, wouldn't it be easier to add an option to pass in the package name? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#39 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACQev82GPVeR-cL5fMWHWJ3wcryxsvb4ks5smXQLgaJpZM4PVgy6> .

from grpcc.

yukw777 commented on June 3, 2024

Something like...

$ grpcc --proto ./service/myservice.proto --address 127.0.0.1:3466 --package package.name

And yeah, this function is not behaving correctly: https://github.com/njpatel/grpcc/blob/master/lib/index.js#L41

I feel like that approach is quite hacky and convoluted. I'd say we should forget about trying to figure out all the services automatically (unless grpc library has a way to do this nicely) and just let the user enter the package name.

from grpcc.

Disturbing commented on June 3, 2024

Agreed

…

On Thu, Sep 28, 2017 at 2:39 AM Peter Yu ***@***.***> wrote: Something like... $ grpcc --proto ./service/myservice.proto --address 127.0.0.1:3466 --package package.name And yeah, this function is not behaving correctly: https://github.com/njpatel/grpcc/blob/master/lib/index.js#L41 I feel like that approach is quite hacky and convoluted. I'd say we should forget about trying to figure out all the services automatically (unless grpc library has a way to do this nicely) and just let the user enter the package name. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#39 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACQev8FLA0GL9Dk-joKwsHfJNJFnKQ0hks5smpZDgaJpZM4PVgy6> .

from grpcc.