Const specifies that this field must be exactly the specified value
Len specifies that this field must be the specified number of characters (Unicode code points). Note that the number of characters may differ from the number of bytes in the string.
MinLen specifies that this field must be the specified number of characters (Unicode code points) at a minimum. Note that the number of characters may differ from the number of bytes in the string.
MaxLen specifies that this field must be the specified number of characters (Unicode code points) at a maximum. Note that the number of characters may differ from the number of bytes in the string.
LenBytes specifies that this field must be the specified number of bytes
MinBytes specifies that this field must be the specified number of bytes at a minimum
MaxBytes specifies that this field must be the specified number of bytes at a maximum
Pattern specifes that this field must match against the specified regular expression (RE2 syntax). The included expression should elide any delimiters.
Prefix specifies that this field must have the specified substring at the beginning of the string.
Suffix specifies that this field must have the specified substring at the end of the string.
Contains specifies that this field must have the specified substring anywhere in the string.
NotContains specifies that this field cannot have the specified substring anywhere in the string.
In specifies that this field must be equal to one of the specified values
NotIn specifies that this field cannot be equal to one of the specified values
This applies to regexes HTTP_HEADER_NAME and HTTP_HEADER_VALUE to enable strict header validation. By default, this is true, and HTTP header validations are RFC-compliant. Setting to false will enable a looser validations that only disallows &92;r&92;n&92;0 characters, which can be used to bypass header matching rules.
IgnoreEmpty specifies that the validation rules of this field should be evaluated only if the field is not empty
Const specifies that this field must be exactly the specified value
Contains specifies that this field must have the specified substring anywhere in the string.
IgnoreEmpty specifies that the validation rules of this field should be evaluated only if the field is not empty
In specifies that this field must be equal to one of the specified values
Len specifies that this field must be the specified number of characters (Unicode code points).
Len specifies that this field must be the specified number of characters (Unicode code points). Note that the number of characters may differ from the number of bytes in the string.
LenBytes specifies that this field must be the specified number of bytes
MaxBytes specifies that this field must be the specified number of bytes at a maximum
MaxLen specifies that this field must be the specified number of characters (Unicode code points) at a maximum.
MaxLen specifies that this field must be the specified number of characters (Unicode code points) at a maximum. Note that the number of characters may differ from the number of bytes in the string.
MinBytes specifies that this field must be the specified number of bytes at a minimum
MinLen specifies that this field must be the specified number of characters (Unicode code points) at a minimum.
MinLen specifies that this field must be the specified number of characters (Unicode code points) at a minimum. Note that the number of characters may differ from the number of bytes in the string.
NotContains specifies that this field cannot have the specified substring anywhere in the string.
NotIn specifies that this field cannot be equal to one of the specified values
Pattern specifes that this field must match against the specified regular expression (RE2 syntax).
Pattern specifes that this field must match against the specified regular expression (RE2 syntax). The included expression should elide any delimiters.
Prefix specifies that this field must have the specified substring at the beginning of the string.
This applies to regexes HTTP_HEADER_NAME and HTTP_HEADER_VALUE to enable strict header validation.
This applies to regexes HTTP_HEADER_NAME and HTTP_HEADER_VALUE to enable strict header validation. By default, this is true, and HTTP header validations are RFC-compliant. Setting to false will enable a looser validations that only disallows &92;r&92;n&92;0 characters, which can be used to bypass header matching rules.
Suffix specifies that this field must have the specified substring at the end of the string.
(Since version 0.6.0) Use toPMessage
(Since version 0.6.0) Use getField that accepts a ScalaPB descriptor and returns PValue
StringRules describe the constraints applied to
string
valuesConst specifies that this field must be exactly the specified value
Len specifies that this field must be the specified number of characters (Unicode code points). Note that the number of characters may differ from the number of bytes in the string.
MinLen specifies that this field must be the specified number of characters (Unicode code points) at a minimum. Note that the number of characters may differ from the number of bytes in the string.
MaxLen specifies that this field must be the specified number of characters (Unicode code points) at a maximum. Note that the number of characters may differ from the number of bytes in the string.
LenBytes specifies that this field must be the specified number of bytes
MinBytes specifies that this field must be the specified number of bytes at a minimum
MaxBytes specifies that this field must be the specified number of bytes at a maximum
Pattern specifes that this field must match against the specified regular expression (RE2 syntax). The included expression should elide any delimiters.
Prefix specifies that this field must have the specified substring at the beginning of the string.
Suffix specifies that this field must have the specified substring at the end of the string.
Contains specifies that this field must have the specified substring anywhere in the string.
NotContains specifies that this field cannot have the specified substring anywhere in the string.
In specifies that this field must be equal to one of the specified values
NotIn specifies that this field cannot be equal to one of the specified values
This applies to regexes HTTP_HEADER_NAME and HTTP_HEADER_VALUE to enable strict header validation. By default, this is true, and HTTP header validations are RFC-compliant. Setting to false will enable a looser validations that only disallows &92;r&92;n&92;0 characters, which can be used to bypass header matching rules.
IgnoreEmpty specifies that the validation rules of this field should be evaluated only if the field is not empty