Supplimentary identifier for passwords specific

components/sync/core/write_node.cc

Index: components/sync/core/write_node.cc
diff --git a/components/sync/core/write_node.cc b/components/sync/core/write_node.cc
index 0977234702cbce013978ddd190d8df1375a17d00..10f89f0c23c07bd47580909a26920333dda2b42f 100644
--- a/components/sync/core/write_node.cc
+++ b/components/sync/core/write_node.cc
@@ -146,6 +146,9 @@ void WriteNode::SetPasswordSpecifics(
   SetEntitySpecifics(entity_specifics);
 }
 
+void WriteNode::SetPasswordSpecificsMetadata(
+    const sync_pb::PasswordSpecificsMetadata& specifics) {}

[Nicolas Zea, 2016/08/20 00:23:43]

I wonder if we really need this. Couldn't you set the metadata field as part of
SetPasswordSpecifics (you may need to do it within nigori_util.cc's
UpdateEntryWithEncryption in fact, which is eventually called from
SetPasswordSpecifics).  You should have access to the encryption state, and can
just clear/set the field as necessary there.

+
 void WriteNode::SetEntitySpecifics(const sync_pb::EntitySpecifics& new_value) {
   ModelType new_specifics_type = GetModelTypeFromSpecifics(new_value);
   CHECK(!new_value.password().has_client_only_encrypted_data());