Skip to content

Protobufs do not follow proto3 conventions w.r.t. presence #61

@SanjayVas

Description

@SanjayVas

proto3 scalar fields have no distinction by default between not being present and being set to the field's default value. The optional keyword is used for cases where that distinction is necessary.

The protobuf definitions in this repo appear to be instead following proto2 conventions of indicating the optional keyword for any singular field.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions