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
Inherited Members
com.google.protobuf.GeneratedMessageV3.Builder.getUnknownFieldSetBuilder()
com.google.protobuf.GeneratedMessageV3.Builder.mergeUnknownLengthDelimitedField(int,com.google.protobuf.ByteString)
com.google.protobuf.GeneratedMessageV3.Builder.mergeUnknownVarintField(int,int)
com.google.protobuf.GeneratedMessageV3.Builder.parseUnknownField(com.google.protobuf.CodedInputStream,com.google.protobuf.ExtensionRegistryLite,int)
com.google.protobuf.GeneratedMessageV3.Builder.setUnknownFieldSetBuilder(com.google.protobuf.UnknownFieldSet.Builder)
Static Methods
getDescriptor()
public static final Descriptors.Descriptor getDescriptor()
Returns
Methods
addRepeatedField(Descriptors.FieldDescriptor field, Object value)
public BadRequest.FieldViolation.Builder addRepeatedField(Descriptors.FieldDescriptor field, Object value)
Parameters
Returns
Overrides
build()
public BadRequest.FieldViolation build()
Returns
buildPartial()
public BadRequest.FieldViolation buildPartial()
Returns
clear()
public BadRequest.FieldViolation.Builder clear()
Returns
Overrides
clearDescription()
public BadRequest.FieldViolation.Builder clearDescription()
A description of why the request element is bad.
string description = 2;
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 valueemail_addresses[1].email for a violation in the email field of the
first email_addresses messageemail_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 valueemailAddresses[1].email for a violation in the email field of the
first emailAddresses messageemailAddresses[3].type[2] for a violation in the second type
value in the third emailAddresses message.
string field = 1;
clearField(Descriptors.FieldDescriptor field)
public BadRequest.FieldViolation.Builder clearField(Descriptors.FieldDescriptor field)
Parameter
Returns
Overrides
clearOneof(Descriptors.OneofDescriptor oneof)
public BadRequest.FieldViolation.Builder clearOneof(Descriptors.OneofDescriptor oneof)
Parameter
Returns
Overrides
clone()
public BadRequest.FieldViolation.Builder clone()
Returns
Overrides
getDefaultInstanceForType()
public BadRequest.FieldViolation getDefaultInstanceForType()
Returns
getDescription()
public String getDescription()
A description of why the request element is bad.
string description = 2;
| Type | Description |
String | The description.
|
getDescriptionBytes()
public ByteString getDescriptionBytes()
A description of why the request element is bad.
string description = 2;
| Type | Description |
ByteString | The bytes for description.
|
getDescriptorForType()
public Descriptors.Descriptor getDescriptorForType()
Returns
Overrides
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 valueemail_addresses[1].email for a violation in the email field of the
first email_addresses messageemail_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 valueemailAddresses[1].email for a violation in the email field of the
first emailAddresses messageemailAddresses[3].type[2] for a violation in the second type
value in the third emailAddresses message.
string field = 1;
| Type | Description |
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 valueemail_addresses[1].email for a violation in the email field of the
first email_addresses messageemail_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 valueemailAddresses[1].email for a violation in the email field of the
first emailAddresses messageemailAddresses[3].type[2] for a violation in the second type
value in the third emailAddresses message.
string field = 1;
internalGetFieldAccessorTable()
protected GeneratedMessageV3.FieldAccessorTable internalGetFieldAccessorTable()
Returns
Overrides
isInitialized()
public final boolean isInitialized()
Returns
Overrides
public BadRequest.FieldViolation.Builder mergeFrom(CodedInputStream input, ExtensionRegistryLite extensionRegistry)
Parameters
Returns
Overrides
Exceptions
mergeFrom(Message other)
public BadRequest.FieldViolation.Builder mergeFrom(Message other)
Parameter
Returns
Overrides
mergeFrom(BadRequest.FieldViolation other)
public BadRequest.FieldViolation.Builder mergeFrom(BadRequest.FieldViolation other)
Parameter
Returns
mergeUnknownFields(UnknownFieldSet unknownFields)
public final BadRequest.FieldViolation.Builder mergeUnknownFields(UnknownFieldSet unknownFields)
Parameter
Returns
Overrides
setDescription(String value)
public BadRequest.FieldViolation.Builder setDescription(String value)
A description of why the request element is bad.
string description = 2;
| Name | Description |
value | String
The description to set.
|
Returns
setDescriptionBytes(ByteString value)
public BadRequest.FieldViolation.Builder setDescriptionBytes(ByteString value)
A description of why the request element is bad.
string description = 2;
| Name | Description |
value | ByteString
The bytes for description to set.
|
Returns
setField(Descriptors.FieldDescriptor field, Object value)
public BadRequest.FieldViolation.Builder setField(Descriptors.FieldDescriptor field, Object value)
Parameters
Returns
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 valueemail_addresses[1].email for a violation in the email field of the
first email_addresses messageemail_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 valueemailAddresses[1].email for a violation in the email field of the
first emailAddresses messageemailAddresses[3].type[2] for a violation in the second type
value in the third emailAddresses message.
string field = 1;
| Name | Description |
value | String
The field to set.
|
Returns
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 valueemail_addresses[1].email for a violation in the email field of the
first email_addresses messageemail_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 valueemailAddresses[1].email for a violation in the email field of the
first emailAddresses messageemailAddresses[3].type[2] for a violation in the second type
value in the third emailAddresses message.
string field = 1;
| Name | Description |
value | ByteString
The bytes for field to set.
|
Returns
setRepeatedField(Descriptors.FieldDescriptor field, int index, Object value)
public BadRequest.FieldViolation.Builder setRepeatedField(Descriptors.FieldDescriptor field, int index, Object value)
Parameters
Returns
Overrides
setUnknownFields(UnknownFieldSet unknownFields)
public final BadRequest.FieldViolation.Builder setUnknownFields(UnknownFieldSet unknownFields)
Parameter
Returns
Overrides
