| ▲ | imtringued 7 days ago | |
>The solution is as follows: > * Make all fields in a message required. This makes messages product types. Meanwhile in the capnproto FAQ: >How do I make a field “required”, like in Protocol Buffers? >You don’t. You may find this surprising, but the “required” keyword in Protocol Buffers turned out to be a horrible mistake. I recommend reading the rest of the FAQ [0], but if you are in a hurry: Fixed schema based protocols like protobuffers do not let you remove fields like self describing formats such as JSON. Removing fields or switching them from required to optional is an ABI breaking change. Nobody wants to update all servers and all clients simultaneously. At that point, you would be better off defining a new API endpoint and deprecating the old one. The capnproto faq article also brings up the fact that validation should be handled on the application level rather than the ABI level. | ||