Class BadRequest.FieldViolation.Builder (2.29.0)

public static final class BadRequest.FieldViolation.Builder extends GeneratedMessageV3.Builder<BadRequest.FieldViolation.Builder> implements BadRequest.FieldViolationOrBuilder

A message type used to describe a single bad request field.

Protobuf type google.rpc.BadRequest.FieldViolation

Static Methods

getDescriptor()

public static final Descriptors.Descriptor getDescriptor()
Returns
TypeDescription
Descriptor

Methods

addRepeatedField(Descriptors.FieldDescriptor field, Object value)

public BadRequest.FieldViolation.Builder addRepeatedField(Descriptors.FieldDescriptor field, Object value)
Parameters
NameDescription
fieldFieldDescriptor
valueObject
Returns
TypeDescription
BadRequest.FieldViolation.Builder
Overrides

build()

public BadRequest.FieldViolation build()
Returns
TypeDescription
BadRequest.FieldViolation

buildPartial()

public BadRequest.FieldViolation buildPartial()
Returns
TypeDescription
BadRequest.FieldViolation

clear()

public BadRequest.FieldViolation.Builder clear()
Returns
TypeDescription
BadRequest.FieldViolation.Builder
Overrides

clearDescription()

public BadRequest.FieldViolation.Builder clearDescription()

A description of why the request element is bad.

string description = 2;

Returns
TypeDescription
BadRequest.FieldViolation.Builder

This builder for chaining.

clearField()

public BadRequest.FieldViolation.Builder clearField()

A path that leads to a field in the request body. The value will be a sequence of dot-separated identifiers that identify a protocol buffer field.

Consider the following:

 message CreateContactRequest {
   message EmailAddress {
     enum Type {
       TYPE_UNSPECIFIED = 0;
       HOME = 1;
       WORK = 2;
     }

     optional string email = 1;
     repeated EmailType type = 2;
   }

   string full_name = 1;
   repeated EmailAddress email_addresses = 2;
 }

In this example, in proto field could take one of the following values:

  • full_name for a violation in the full_name value
  • email_addresses[1].email for a violation in the email field of the first email_addresses message
  • email_addresses[3].type[2] for a violation in the second type value in the third email_addresses message.

    In JSON, the same values are represented as:

  • fullName for a violation in the fullName value

  • emailAddresses[1].email for a violation in the email field of the first emailAddresses message
  • emailAddresses[3].type[2] for a violation in the second type value in the third emailAddresses message.

string field = 1;

Returns
TypeDescription
BadRequest.FieldViolation.Builder

This builder for chaining.

clearField(Descriptors.FieldDescriptor field)

public BadRequest.FieldViolation.Builder clearField(Descriptors.FieldDescriptor field)
Parameter
NameDescription
fieldFieldDescriptor
Returns
TypeDescription
BadRequest.FieldViolation.Builder
Overrides

clearOneof(Descriptors.OneofDescriptor oneof)

public BadRequest.FieldViolation.Builder clearOneof(Descriptors.OneofDescriptor oneof)
Parameter
NameDescription
oneofOneofDescriptor
Returns
TypeDescription
BadRequest.FieldViolation.Builder
Overrides

clone()

public BadRequest.FieldViolation.Builder clone()
Returns
TypeDescription
BadRequest.FieldViolation.Builder
Overrides

getDefaultInstanceForType()

public BadRequest.FieldViolation getDefaultInstanceForType()
Returns
TypeDescription
BadRequest.FieldViolation

getDescription()

public String getDescription()

A description of why the request element is bad.

string description = 2;

Returns
TypeDescription
String

The description.

getDescriptionBytes()

public ByteString getDescriptionBytes()

A description of why the request element is bad.

string description = 2;

Returns
TypeDescription
ByteString

The bytes for description.

getDescriptorForType()

public Descriptors.Descriptor getDescriptorForType()
Returns
TypeDescription
Descriptor
Overrides

getField()

public String getField()

A path that leads to a field in the request body. The value will be a sequence of dot-separated identifiers that identify a protocol buffer field.

Consider the following:

 message CreateContactRequest {
   message EmailAddress {
     enum Type {
       TYPE_UNSPECIFIED = 0;
       HOME = 1;
       WORK = 2;
     }

     optional string email = 1;
     repeated EmailType type = 2;
   }

   string full_name = 1;
   repeated EmailAddress email_addresses = 2;
 }

In this example, in proto field could take one of the following values:

  • full_name for a violation in the full_name value
  • email_addresses[1].email for a violation in the email field of the first email_addresses message
  • email_addresses[3].type[2] for a violation in the second type value in the third email_addresses message.

    In JSON, the same values are represented as:

  • fullName for a violation in the fullName value

  • emailAddresses[1].email for a violation in the email field of the first emailAddresses message
  • emailAddresses[3].type[2] for a violation in the second type value in the third emailAddresses message.

string field = 1;

Returns
TypeDescription
String

The field.

getFieldBytes()

public ByteString getFieldBytes()

A path that leads to a field in the request body. The value will be a sequence of dot-separated identifiers that identify a protocol buffer field.

Consider the following:

 message CreateContactRequest {
   message EmailAddress {
     enum Type {
       TYPE_UNSPECIFIED = 0;
       HOME = 1;
       WORK = 2;
     }

     optional string email = 1;
     repeated EmailType type = 2;
   }

   string full_name = 1;
   repeated EmailAddress email_addresses = 2;
 }

In this example, in proto field could take one of the following values:

  • full_name for a violation in the full_name value
  • email_addresses[1].email for a violation in the email field of the first email_addresses message
  • email_addresses[3].type[2] for a violation in the second type value in the third email_addresses message.

    In JSON, the same values are represented as:

  • fullName for a violation in the fullName value

  • emailAddresses[1].email for a violation in the email field of the first emailAddresses message
  • emailAddresses[3].type[2] for a violation in the second type value in the third emailAddresses message.

string field = 1;

Returns
TypeDescription
ByteString

The bytes for field.

internalGetFieldAccessorTable()

protected GeneratedMessageV3.FieldAccessorTable internalGetFieldAccessorTable()
Returns
TypeDescription
FieldAccessorTable
Overrides

isInitialized()

public final boolean isInitialized()
Returns
TypeDescription
boolean
Overrides

mergeFrom(CodedInputStream input, ExtensionRegistryLite extensionRegistry)

public BadRequest.FieldViolation.Builder mergeFrom(CodedInputStream input, ExtensionRegistryLite extensionRegistry)
Parameters
NameDescription
inputCodedInputStream
extensionRegistryExtensionRegistryLite
Returns
TypeDescription
BadRequest.FieldViolation.Builder
Overrides
Exceptions
TypeDescription
IOException

mergeFrom(Message other)

public BadRequest.FieldViolation.Builder mergeFrom(Message other)
Parameter
NameDescription
otherMessage
Returns
TypeDescription
BadRequest.FieldViolation.Builder
Overrides

mergeFrom(BadRequest.FieldViolation other)

public BadRequest.FieldViolation.Builder mergeFrom(BadRequest.FieldViolation other)
Parameter
NameDescription
otherBadRequest.FieldViolation
Returns
TypeDescription
BadRequest.FieldViolation.Builder

mergeUnknownFields(UnknownFieldSet unknownFields)

public final BadRequest.FieldViolation.Builder mergeUnknownFields(UnknownFieldSet unknownFields)
Parameter
NameDescription
unknownFieldsUnknownFieldSet
Returns
TypeDescription
BadRequest.FieldViolation.Builder
Overrides

setDescription(String value)

public BadRequest.FieldViolation.Builder setDescription(String value)

A description of why the request element is bad.

string description = 2;

Parameter
NameDescription
valueString

The description to set.

Returns
TypeDescription
BadRequest.FieldViolation.Builder

This builder for chaining.

setDescriptionBytes(ByteString value)

public BadRequest.FieldViolation.Builder setDescriptionBytes(ByteString value)

A description of why the request element is bad.

string description = 2;

Parameter
NameDescription
valueByteString

The bytes for description to set.

Returns
TypeDescription
BadRequest.FieldViolation.Builder

This builder for chaining.

setField(Descriptors.FieldDescriptor field, Object value)

public BadRequest.FieldViolation.Builder setField(Descriptors.FieldDescriptor field, Object value)
Parameters
NameDescription
fieldFieldDescriptor
valueObject
Returns
TypeDescription
BadRequest.FieldViolation.Builder
Overrides

setField(String value)

public BadRequest.FieldViolation.Builder setField(String value)

A path that leads to a field in the request body. The value will be a sequence of dot-separated identifiers that identify a protocol buffer field.

Consider the following:

 message CreateContactRequest {
   message EmailAddress {
     enum Type {
       TYPE_UNSPECIFIED = 0;
       HOME = 1;
       WORK = 2;
     }

     optional string email = 1;
     repeated EmailType type = 2;
   }

   string full_name = 1;
   repeated EmailAddress email_addresses = 2;
 }

In this example, in proto field could take one of the following values:

  • full_name for a violation in the full_name value
  • email_addresses[1].email for a violation in the email field of the first email_addresses message
  • email_addresses[3].type[2] for a violation in the second type value in the third email_addresses message.

    In JSON, the same values are represented as:

  • fullName for a violation in the fullName value

  • emailAddresses[1].email for a violation in the email field of the first emailAddresses message
  • emailAddresses[3].type[2] for a violation in the second type value in the third emailAddresses message.

string field = 1;

Parameter
NameDescription
valueString

The field to set.

Returns
TypeDescription
BadRequest.FieldViolation.Builder

This builder for chaining.

setFieldBytes(ByteString value)

public BadRequest.FieldViolation.Builder setFieldBytes(ByteString value)

A path that leads to a field in the request body. The value will be a sequence of dot-separated identifiers that identify a protocol buffer field.

Consider the following:

 message CreateContactRequest {
   message EmailAddress {
     enum Type {
       TYPE_UNSPECIFIED = 0;
       HOME = 1;
       WORK = 2;
     }

     optional string email = 1;
     repeated EmailType type = 2;
   }

   string full_name = 1;
   repeated EmailAddress email_addresses = 2;
 }

In this example, in proto field could take one of the following values:

  • full_name for a violation in the full_name value
  • email_addresses[1].email for a violation in the email field of the first email_addresses message
  • email_addresses[3].type[2] for a violation in the second type value in the third email_addresses message.

    In JSON, the same values are represented as:

  • fullName for a violation in the fullName value

  • emailAddresses[1].email for a violation in the email field of the first emailAddresses message
  • emailAddresses[3].type[2] for a violation in the second type value in the third emailAddresses message.

string field = 1;

Parameter
NameDescription
valueByteString

The bytes for field to set.

Returns
TypeDescription
BadRequest.FieldViolation.Builder

This builder for chaining.

setRepeatedField(Descriptors.FieldDescriptor field, int index, Object value)

public BadRequest.FieldViolation.Builder setRepeatedField(Descriptors.FieldDescriptor field, int index, Object value)
Parameters
NameDescription
fieldFieldDescriptor
indexint
valueObject
Returns
TypeDescription
BadRequest.FieldViolation.Builder
Overrides

setUnknownFields(UnknownFieldSet unknownFields)

public final BadRequest.FieldViolation.Builder setUnknownFields(UnknownFieldSet unknownFields)
Parameter
NameDescription
unknownFieldsUnknownFieldSet
Returns
TypeDescription
BadRequest.FieldViolation.Builder
Overrides