protocol-buffers
protocol-buffers copied to clipboard
k-bx
Haskell protocol-buffers package
When I specify `--lenses` and `--json` simultaneously, I can't compile the generated files. This is because we don't consider that `--lenses` adds `"_"` to the field name. This PR fixes...
Is it possible to have .proto file in my package tarball to be used to generate Haskell modules when package is being built by cabal? So that `hprotoc` version will...
Small fix related to #81 It worked for me for MESOS protobuf definitions, however I've got no idea what I did and is good for something or not.
Adding `--lenses` option will make hprotoc to prepend each record field with underscore, however generated JSON classes will not this prefix.
Exposed API use lazy bytestrings, however internally protobuf works with strict chunks. Some libraries can provide stream of strict bytestrings directly. Having an API which accepts strict bytestrings will allow...
Consider Mesos [maintenance.proto](https://github.com/apache/mesos/blob/master/include/mesos/v1/maintenance/maintenance.proto). It imports package allocator.proto (`import "mesos/v1/allocator/allocator.proto";` at line 21) and uses package-qualified name to access message from it (`repeated allocator.InverseOfferStatus statuses = 2;` at line 82). It...
If you have an empty protobuf message, the generated code compiles with «Defined but not used» warning: ``` $ cat test.proto package test; message Test {} $ hprotoc test.proto …...
Solve problem like that: In the package a.b.c , solve d.D from the package a.b.d
It conflicts with the other function named `makeLenses` from `Control.Lens.TH`. If I'm actually using lenses, surely I'm also importing `Control.Lens.TH` somewhere, and this causes conflicts. This is somewhat petty, but...
`12:import qualified XXXYYY.Proto.DescriptorProtos.FieldOptions as DescriptorProtos (FieldOptions)` instead of `Text.DescriptorProtos` (`XXXYYY.Proto` is my prefix module)