You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, this type has the following nuances to resolve:
string format and repeated string param fields should be removed in favor of TemplateString message.
base.FieldPath field_path is mostly used as field_name. Let's introduce an explicit field_name, and remove the remaining path prefix to field_path_prefix field.
repeated violation field is unnecessary. Currently, we create two violations where a single one actually occurs. If a nested message has an invalid field, a root message always creates an unnecessary violation as a wrapper. We should try to avoid this.
The text was updated successfully, but these errors were encountered:
Currently, this type has the following nuances to resolve:
string format
andrepeated string param
fields should be removed in favor ofTemplateString message
.base.FieldPath field_path
is mostly used asfield_name
. Let's introduce an explicitfield_name
, and remove the remaining path prefix tofield_path_prefix
field.repeated violation
field is unnecessary. Currently, we create two violations where a single one actually occurs. If a nested message has an invalid field, a root message always creates an unnecessary violation as a wrapper. We should try to avoid this.The text was updated successfully, but these errors were encountered: