google.rpc.BadRequest.FieldViolation */ class FieldViolation extends \DeliciousBrains\WP_Offload_Media\Gcp\Google\Protobuf\Internal\Message { /** * 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. * * Generated from protobuf field string field = 1; */ protected $field = ''; /** * A description of why the request element is bad. * * Generated from protobuf field string description = 2; */ protected $description = ''; /** * Constructor. * * @param array $data { * Optional. Data for populating the Message object. * * @type string $field * 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. * @type string $description * A description of why the request element is bad. * } */ public function __construct($data = NULL) { \DeliciousBrains\WP_Offload_Media\Gcp\GPBMetadata\Google\Rpc\ErrorDetails::initOnce(); parent::__construct($data); } /** * 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. * * Generated from protobuf field string field = 1; * @return string */ public function getField() { return $this->field; } /** * 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. * * Generated from protobuf field string field = 1; * @param string $var * @return $this */ public function setField($var) { GPBUtil::checkString($var, True); $this->field = $var; return $this; } /** * A description of why the request element is bad. * * Generated from protobuf field string description = 2; * @return string */ public function getDescription() { return $this->description; } /** * A description of why the request element is bad. * * Generated from protobuf field string description = 2; * @param string $var * @return $this */ public function setDescription($var) { GPBUtil::checkString($var, True); $this->description = $var; return $this; } }