protoc import "cue/cue.proto"; ? #983
Replies: 3 comments 2 replies
-
@randomizedcoder I'm very sorry, your original message entirely slipped through the gaps. Are you still having problems here? If so, please respond back and I'll be happy to help. |
Beta Was this translation helpful? Give feedback.
0 replies
-
I could not get cue working because of the issue I posed.
…On Mon, Jul 26, 2021 at 2:25 AM Paul Jolly ***@***.***> wrote:
@randomizedcoder <https://github.com/randomizedcoder> I'm very sorry,
your original message entirely slipped through the gaps.
Are you still having problems here? If so, please respond back and I'll be
happy to help.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#983 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/APMCHTSNU5KNHD7G2G544XLTZUS2PANCNFSM47YASLRQ>
.
--
Regards,
Dave Seddon
+1 415 857 5102
|
Beta Was this translation helpful? Give feedback.
1 reply
Answer selected by
myitcv
-
Thanks Paul. I feel less silly now. :) I guess this item can be closed as
a duplicate.
…On Tue, Aug 3, 2021 at 8:16 AM Paul Jolly ***@***.***> wrote:
@randomizedcoder <https://github.com/randomizedcoder> the issue here is
that protoc does not know where to find cue/cue.proto. Hence you need to
pass -I to protoc to indicate where imports can be resolved. As far as
I'm aware, the best way to do that is to establish a dependency on the
cuelang.org/go Go module which contains that file. For a complete example
please see #581 (comment)
<#581 (comment)>, a
comment which unfortunately also confirms there is a problem with the Go
code that is generated today 😢 ! But #581
<#581> tracks fixing that.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#983 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/APMCHTSZEIWQCFUARRBBOYLT3AB5ZANCNFSM47YASLRQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email>
.
--
Regards,
Dave Seddon
+1 415 857 5102
|
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Originally opened by @randomizedcoder in cuelang/cue#983
G'day,
I'm a newbie attempting to use Cue for the first time, so sorry for the really basic questions. I figure I should ask to help the next newbie, and possibly add a little to the docs to make it more clear. - Documentation does seems great BTW
Essentially, I'm hoping to this CUE mostly to code gen input validation for gRPC, per the tail end of:
https://cuelang.org/docs/usecases/generate/
I've added the cue tags to the .protos, per:
https://cuelang.org/docs/integrations/protobuf/#extract-cue-from-a-standalone-proto-file
I've done the install via: https://cuelang.org/docs/install/
Added the import for cue, just after the standard timestamp, for example:
Then I tried protoc, but I suspect I'm missing a plugin.
But I don't know what to do. Searching finds the envoyproxy stuff, and actually that might be an alternative to cue. I don't know what the community is doing, with CUE verse this envoy proxy code gen thinger.
https://github.com/envoyproxy/protoc-gen-validate
Thanks in advance
Beta Was this translation helpful? Give feedback.
All reactions