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
In some cases, especially when creating entity states, an ID field has a value which equals the value of a field of a nested message.
For example, in ProtoData, ProtobufSourceFile message has the ID field file_path, which has the same value as the path value of the nested File message contained in the file field:
messageProtobufSourceFile {
option(entity).kind=VIEW;
// The relative path to the file.//// Must be the same as `file.path`.//FilePathfile_path=1;
Filefile=2;
...
}
A programmer has to remember this fact, and currently there's no way to guard him against an error. It would be more convenient to have a validation option, which ensures that field values are equal:
messageProtobufSourceFile {
option(entity).kind=VIEW;
// The relative path to the file.//// Must be the same as `file.path`.//FilePathfile_path=1 [(same_as) = "file.path");
Filefile = 2;
...
The text was updated successfully, but these errors were encountered:
In some cases, especially when creating entity states, an ID field has a value which equals the value of a field of a nested message.
For example, in ProtoData,
ProtobufSourceFile
message has the ID fieldfile_path
, which has the same value as thepath
value of the nestedFile
message contained in thefile
field:A programmer has to remember this fact, and currently there's no way to guard him against an error. It would be more convenient to have a validation option, which ensures that field values are equal:
The text was updated successfully, but these errors were encountered: