optional int32 result_per_page = 3 [default = 10];
If the default value is not specified for an optional element, a type-specific default value is used instead: for strings, the default value is the empty string. For bytes, the default value is the empty byte string. For bools, the default value is false. For numeric types, the default value is zero. For enums, the default value is the first value listed in the enum's type definition. This means care must be taken when adding a value to the beginning of an enum value list. See the Updating A Message Type section for guidelines on how to safely change definitions."
Well according to the docs on protocol buffers at least my understanding is as I have read elsewhere.
I don't know what your problem is guy.
I was under the impression that you can't specify fields as null. Instead they just get assigned whatever the default value is for that type.
That seems like a significant drawback for me if it is indeed the case. Especially in the case of a public facing API.
I like the idea of a lot of client libraries able to generate easily, I'm just not sure on this one point how to deal with it nicely...