Is there a way to generate .proto files from a file descriptor proto?
If not, is there a way to invoke the compiler using a file descriptor
proto as input?
Thanks,
Jeff
--
You received this message because you are subscribed to the Google Groups
"Protocol Buffers" group.
To post to this group,
uired fields
over 2 releases. This might be too serious of an api change at this point,
but it seems like required has fallen out of favor anyway, so maybe this
wouldn't be too bad.
On Tue, Aug 24, 2010 at 4:47 PM, Kenton Varda wrote:
> On Wed, Aug 18, 2010 at 7:07 AM, Jeff Plaisance
>
you feel like that's a
> worthwhile trade-off.
>
> On Tue, Aug 17, 2010 at 10:51 PM, Jeff Plaisance
> wrote:
>
>> I agree that defaults should be handled in the library. I have been
>> putting off the issue because i found the interaction between the hasX and
>> ge
your message where the field isn't actually required, and you can
> never change "required" to "optional" later without risking breaking
> something. It sounds like your implementation would actually encourage
> people to use "required" to avoid hav
Hello,
I have written a compiler plugin that generates type safe scala
wrappers for the java protoc output. It creates wrappers for each
message type that use the scala Option type for all optional values.
It also forces all required parameters to be included in the
constructor of the builder so
