Reference documentation and code samples for the Migrate for Compute Engine V1 API class Google::Rpc::BadRequest::FieldViolation.
A message type used to describe a single bad request field.
Inherits
- Object
Extended By
- Google::Protobuf::MessageExts::ClassMethods
Includes
- Google::Protobuf::MessageExts
Methods
#description
def description() -> ::String
- (::String) — A description of why the request element is bad.
#description=
def description=(value) -> ::String
- value (::String) — A description of why the request element is bad.
- (::String) — A description of why the request element is bad.
#field
def field() -> ::String
-
(::String) —
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 thefull_name
valueemail_addresses[1].email
for a violation in theemail
field of the firstemail_addresses
messageemail_addresses[3].type[2]
for a violation in the secondtype
value in the thirdemail_addresses
message.
In JSON, the same values are represented as:
fullName
for a violation in thefullName
valueemailAddresses[1].email
for a violation in theemail
field of the firstemailAddresses
messageemailAddresses[3].type[2]
for a violation in the secondtype
value in the thirdemailAddresses
message.
#field=
def field=(value) -> ::String
-
value (::String) —
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 thefull_name
valueemail_addresses[1].email
for a violation in theemail
field of the firstemail_addresses
messageemail_addresses[3].type[2]
for a violation in the secondtype
value in the thirdemail_addresses
message.
In JSON, the same values are represented as:
fullName
for a violation in thefullName
valueemailAddresses[1].email
for a violation in theemail
field of the firstemailAddresses
messageemailAddresses[3].type[2]
for a violation in the secondtype
value in the thirdemailAddresses
message.
-
(::String) —
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 thefull_name
valueemail_addresses[1].email
for a violation in theemail
field of the firstemail_addresses
messageemail_addresses[3].type[2]
for a violation in the secondtype
value in the thirdemail_addresses
message.
In JSON, the same values are represented as:
fullName
for a violation in thefullName
valueemailAddresses[1].email
for a violation in theemail
field of the firstemailAddresses
messageemailAddresses[3].type[2]
for a violation in the secondtype
value in the thirdemailAddresses
message.