Comment on nullability of fields #11
Description
In the README you mention that you'll have to look into the Mumble protocol to see if some of the proto fields are actually not nullable.
As you have already pointed out, we do specify all fields as optional in our proto definition.
This should really be taken literally.
The reason for even marking fields as optional that right now are absolutely mandatory is backwards compatibility. It is jot possible to change a field from required to optional in a backwards compatible way, which is why the official guideline is to mark all fields as optional.
For your case this means that you probably also want to keep all these fields as nullable in your code as otherwise your lib may break/crash if in the future one of the currently required fields become optional/obsolete.