tim2CF

I actually know which types are causing these errors, here is example https://github.com/lightningnetwork/lnd/blob/1bd211a7228d2f13ecaf514f611738837c057d94/lnrpc/rpc.proto#L840

Not sure it is right solution or not, but I worked it around with this orphan instance https://github.com/coingaming/lnd-client/blob/d6971ae41da8c8112a65b805ba49106bcad3edf6/src/LndGrpc/Orphans.hs#L11-L12

This is ok way to do so, and conceptually correct from Google Protobuf standard point of view. In general case Google is promoting custom options for language-specific details. It's unrelated,...

Btw I don't see any Haskell related codes [here](https://github.com/protocolbuffers/protobuf/blob/e9360dfa53f151e64c996823785e0eb6c8118620/docs/options.md). If we do any sort of custom options - it's nice to register in this registry

But option for `compile-proto-file` executable might be very handy as well (and I think relatively easy to do). In our particular use case we have ~200 protobuf files, and adding...

thanks!

I have the same issue. Maybe @Gabriel439 can say what exactly needs to be fixed - parsing or rendering? Or maybe AST and then parsing and rendering.

might be fixed in this PR https://github.com/awakesecurity/proto3-suite/pull/143