-
Notifications
You must be signed in to change notification settings - Fork 298
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cue: proto support #5
Comments
Original reply by @JohnAZoidberg in cuelang/cue#5 (comment) What's the status of encoding Cue values as Protobuf? |
Original reply by @mpvl in cuelang/cue#5 (comment) It is not implemented so far. Should be straightforward, but stabilizing the new evaluator has priority. But open to contributions. |
Original reply by @mvdan in cuelang/cue#5 (comment) In case you're not aware, the new protobuf module has low-level primitive packages for encoding and decoding, for example for arbitrary data in protowire: https://pkg.go.dev/google.golang.org/protobuf@v1.26.0/encoding/protowire https://pkg.go.dev/google.golang.org/protobuf@v1.26.0/encoding/prototext is message-based instead of token-based, though, so it's unclear if you could use it at all without a schema. |
Hello, is there any update/estimate on the timelines for this request? |
With regards to Protobuf support, the documentation has been improved since 2021, but still does not make it clear that Cue can't generate protobuf files form Cue. Cue can import .proto to .cue, but cannot go the other way. References: Instead of cue, we have settled for the protobuf validation via: |
Originally opened by @mpvl in cuelang/cue#5
Tracking issue for adding protobuf support to CUE:
The text was updated successfully, but these errors were encountered: