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
This would allow structs to have some custom logic for returning "$kind", "$id", etc. This would be useful if the kind or ID had parseable fields, so that the struct could store them separately and only produce the concatenated string when needed by the datastore layer.
The implementation would only call the method in the event that some field doesn't have that key. This would prevent silliness like having a $kind field in the struct, but also special $kind logic in the methods.
I think it would make sense to only allow the override if both methods are defined.
The text was updated successfully, but these errors were encountered:
This is useful when the '$id' is actually multiple fields packed into a string,
but it's generally available for any metadata field.
R=dnj@chromium.org, estaab@chromium.org, maruel@chromium.org, tandrii@chromium.org, vadimsh@chromium.org
BUG=#15
Review URL: https://codereview.chromium.org/1401533007
This would allow structs to have some custom logic for returning "$kind", "$id", etc. This would be useful if the kind or ID had parseable fields, so that the struct could store them separately and only produce the concatenated string when needed by the datastore layer.
The implementation would only call the method in the event that some field doesn't have that key. This would prevent silliness like having a
$kind
field in the struct, but also special$kind
logic in the methods.I think it would make sense to only allow the override if both methods are defined.
The text was updated successfully, but these errors were encountered: