Package 

Class FieldDescriptorProtoKt.Dsl

    • Method Detail

      • getLabel

         final DescriptorProtos.FieldDescriptorProto.Label getLabel()

      • setLabel

         final Unit setLabel(DescriptorProtos.FieldDescriptorProto.Label label)

      • getType

         final DescriptorProtos.FieldDescriptorProto.Type getType()

      • setType

         final Unit setType(DescriptorProtos.FieldDescriptorProto.Type type)

      • getOptions

         final DescriptorProtos.FieldOptions getOptions()

      • setOptions

         final Unit setOptions(DescriptorProtos.FieldOptions options)

      • clearName

         final Unit clearName()

        <code>optional string name = 1;</code>

      • hasName

         final Boolean hasName()

        <code>optional string name = 1;</code>

      • clearNumber

         final Unit clearNumber()

        <code>optional int32 number = 3;</code>

      • clearLabel

         final Unit clearLabel()

        <code>optional .google.protobuf.FieldDescriptorProto.Label label = 4;</code>

      • hasLabel

         final Boolean hasLabel()

        <code>optional .google.protobuf.FieldDescriptorProto.Label label = 4;</code>

      • clearType

         final Unit clearType()
        <pre> If type_name is set, this need not be set. If both this and type_name are set, this must be one of TYPE_ENUM, TYPE_MESSAGE or TYPE_GROUP. </pre>

        <code>optional .google.protobuf.FieldDescriptorProto.Type type = 5;</code>

      • hasType

         final Boolean hasType()
        <pre> If type_name is set, this need not be set. If both this and type_name are set, this must be one of TYPE_ENUM, TYPE_MESSAGE or TYPE_GROUP. </pre>

        <code>optional .google.protobuf.FieldDescriptorProto.Type type = 5;</code>

      • clearTypeName

         final Unit clearTypeName()
        <pre> For message and enum types, this is the name of the type. If the name starts with a '.', it is fully-qualified. Otherwise, C++-like scoping rules are used to find the type (i.e. first the nested types within this message are searched, then within the parent, on up to the root namespace). </pre>

        <code>optional string type_name = 6;</code>

      • hasTypeName

         final Boolean hasTypeName()
        <pre> For message and enum types, this is the name of the type. If the name starts with a '.', it is fully-qualified. Otherwise, C++-like scoping rules are used to find the type (i.e. first the nested types within this message are searched, then within the parent, on up to the root namespace). </pre>

        <code>optional string type_name = 6;</code>

      • clearExtendee

         final Unit clearExtendee()
        <pre> For extensions, this is the name of the type being extended. It is resolved in the same manner as type_name. </pre>

        <code>optional string extendee = 2;</code>

      • hasExtendee

         final Boolean hasExtendee()
        <pre> For extensions, this is the name of the type being extended. It is resolved in the same manner as type_name. </pre>

        <code>optional string extendee = 2;</code>

      • clearDefaultValue

         final Unit clearDefaultValue()
        <pre> For numeric types, contains the original text representation of the value. For booleans, "true" or "false". For strings, contains the default text contents (not escaped in any way). For bytes, contains the C escaped value. All bytes &gt;= 128 are escaped. </pre>

        <code>optional string default_value = 7;</code>

      • hasDefaultValue

         final Boolean hasDefaultValue()
        <pre> For numeric types, contains the original text representation of the value. For booleans, "true" or "false". For strings, contains the default text contents (not escaped in any way). For bytes, contains the C escaped value. All bytes &gt;= 128 are escaped. </pre>

        <code>optional string default_value = 7;</code>

      • clearOneofIndex

         final Unit clearOneofIndex()
        <pre> If set, gives the index of a oneof in the containing type's oneof_decl list. This field is a member of that oneof. </pre>

        <code>optional int32 oneof_index = 9;</code>

      • hasOneofIndex

         final Boolean hasOneofIndex()
        <pre> If set, gives the index of a oneof in the containing type's oneof_decl list. This field is a member of that oneof. </pre>

        <code>optional int32 oneof_index = 9;</code>

      • clearJsonName

         final Unit clearJsonName()
        <pre> JSON name of this field. The value is set by protocol compiler. If the user has set a "json_name" option on this field, that option's value will be used. Otherwise, it's deduced from the field's name by converting it to camelCase. </pre>

        <code>optional string json_name = 10;</code>

      • hasJsonName

         final Boolean hasJsonName()
        <pre> JSON name of this field. The value is set by protocol compiler. If the user has set a "json_name" option on this field, that option's value will be used. Otherwise, it's deduced from the field's name by converting it to camelCase. </pre>

        <code>optional string json_name = 10;</code>

      • clearOptions

         final Unit clearOptions()

        <code>optional .google.protobuf.FieldOptions options = 8;</code>

      • hasOptions

         final Boolean hasOptions()

        <code>optional .google.protobuf.FieldOptions options = 8;</code>

      • clearProto3Optional

         final Unit clearProto3Optional()
        <pre> If true, this is a proto3 "optional". When a proto3 field is optional, it tracks presence regardless of field type. When proto3_optional is true, this field must be belong to a oneof to signal to old proto3 clients that presence is tracked for this field. This oneof is known as a "synthetic" oneof, and this field must be its sole member (each proto3 optional field gets its own synthetic oneof). Synthetic oneofs exist in the descriptor only, and do not generate any API. Synthetic oneofs must be ordered after all "real" oneofs. For message fields, proto3_optional doesn't create any semantic change, since non-repeated message fields always track presence. However it still indicates the semantic detail of whether the user wrote "optional" or not. This can be useful for round-tripping the .proto file. For consistency we give message fields a synthetic oneof also, even though it is not required to track presence. This is especially important because the parser can't tell if a field is a message or an enum, so it must always create a synthetic oneof. Proto2 optional fields do not set this flag, because they already indicate optional with `LABEL_OPTIONAL`. </pre>

        <code>optional bool proto3_optional = 17;</code>

      • hasProto3Optional

         final Boolean hasProto3Optional()
        <pre> If true, this is a proto3 "optional". When a proto3 field is optional, it tracks presence regardless of field type. When proto3_optional is true, this field must be belong to a oneof to signal to old proto3 clients that presence is tracked for this field. This oneof is known as a "synthetic" oneof, and this field must be its sole member (each proto3 optional field gets its own synthetic oneof). Synthetic oneofs exist in the descriptor only, and do not generate any API. Synthetic oneofs must be ordered after all "real" oneofs. For message fields, proto3_optional doesn't create any semantic change, since non-repeated message fields always track presence. However it still indicates the semantic detail of whether the user wrote "optional" or not. This can be useful for round-tripping the .proto file. For consistency we give message fields a synthetic oneof also, even though it is not required to track presence. This is especially important because the parser can't tell if a field is a message or an enum, so it must always create a synthetic oneof. Proto2 optional fields do not set this flag, because they already indicate optional with `LABEL_OPTIONAL`. </pre>

        <code>optional bool proto3_optional = 17;</code>