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()
Methods
addRepeatedField(Descriptors.FieldDescriptor field, Object value)
public BadRequest.FieldViolation.Builder addRepeatedField(Descriptors.FieldDescriptor field, Object value)
Overrides
build()
public BadRequest.FieldViolation build()
buildPartial()
public BadRequest.FieldViolation buildPartial()
clear()
public BadRequest.FieldViolation.Builder clear()
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
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;
clearField(Descriptors.FieldDescriptor field)
public BadRequest.FieldViolation.Builder clearField(Descriptors.FieldDescriptor field)
Overrides
clearOneof(Descriptors.OneofDescriptor oneof)
public BadRequest.FieldViolation.Builder clearOneof(Descriptors.OneofDescriptor oneof)
Overrides
clone()
public BadRequest.FieldViolation.Builder clone()
Overrides
getDefaultInstanceForType()
public BadRequest.FieldViolation getDefaultInstanceForType()
getDescription()
public String getDescription()
A description of why the request element is bad.
string description = 2;
Returns |
---|
Type | Description |
String | The description.
|
getDescriptionBytes()
public ByteString getDescriptionBytes()
A description of why the request element is bad.
string description = 2;
Returns |
---|
Type | Description |
ByteString | The bytes for description.
|
getDescriptorForType()
public Descriptors.Descriptor getDescriptorForType()
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
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 |
---|
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
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 |
---|
Type | Description |
ByteString | The bytes for field.
|
internalGetFieldAccessorTable()
protected GeneratedMessageV3.FieldAccessorTable internalGetFieldAccessorTable()
Overrides
isInitialized()
public final boolean isInitialized()
Overrides
public BadRequest.FieldViolation.Builder mergeFrom(CodedInputStream input, ExtensionRegistryLite extensionRegistry)
Overrides
mergeFrom(Message other)
public BadRequest.FieldViolation.Builder mergeFrom(Message other)
Parameter |
---|
Name | Description |
other | Message
|
Overrides
mergeFrom(BadRequest.FieldViolation other)
public BadRequest.FieldViolation.Builder mergeFrom(BadRequest.FieldViolation other)
mergeUnknownFields(UnknownFieldSet unknownFields)
public final BadRequest.FieldViolation.Builder mergeUnknownFields(UnknownFieldSet unknownFields)
Overrides
setDescription(String value)
public BadRequest.FieldViolation.Builder setDescription(String value)
A description of why the request element is bad.
string description = 2;
Parameter |
---|
Name | Description |
value | String
The description to set.
|
setDescriptionBytes(ByteString value)
public BadRequest.FieldViolation.Builder setDescriptionBytes(ByteString value)
A description of why the request element is bad.
string description = 2;
Parameter |
---|
Name | Description |
value | ByteString
The bytes for description to set.
|
setField(Descriptors.FieldDescriptor field, Object value)
public BadRequest.FieldViolation.Builder setField(Descriptors.FieldDescriptor field, Object value)
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 |
---|
Name | Description |
value | String
The field to set.
|
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 |
---|
Name | Description |
value | ByteString
The bytes for field to set.
|
setRepeatedField(Descriptors.FieldDescriptor field, int index, Object value)
public BadRequest.FieldViolation.Builder setRepeatedField(Descriptors.FieldDescriptor field, int index, Object value)
Overrides
setUnknownFields(UnknownFieldSet unknownFields)
public final BadRequest.FieldViolation.Builder setUnknownFields(UnknownFieldSet unknownFields)
Overrides