Remove use of deprecated base::ListValue::Append(Value*) overload in extensions.

chrome/browser/extensions/api/commands/commands.cc

Index: chrome/browser/extensions/api/commands/commands.cc
diff --git a/chrome/browser/extensions/api/commands/commands.cc b/chrome/browser/extensions/api/commands/commands.cc
index eec31c29424e2eb62585ccbd9deea7beee3006ab..608d5db2dcb1939c7bc61d7c4ea3aa9419d8a12c 100644
--- a/chrome/browser/extensions/api/commands/commands.cc
+++ b/chrome/browser/extensions/api/commands/commands.cc
@@ -12,9 +12,10 @@
 
 namespace {
 
-base::DictionaryValue* CreateCommandValue(
-    const extensions::Command& command, bool active) {
-  base::DictionaryValue* result = new base::DictionaryValue();
+std::unique_ptr<base::DictionaryValue> CreateCommandValue(
+    const extensions::Command& command,
+    bool active) {
+  std::unique_ptr<base::DictionaryValue> result(new base::DictionaryValue());

[Devlin, 2016/09/12 19:12:34]

I'm assuming that future MakeUnique calls are orthogonal to this CL?

[dcheng, 2016/09/12 20:26:45]

This CL has been in progress for awhile: previously, we didn't have the clang
plugin check for using auto* for pointer types (though it's still not enabled by
default, we're getting closer... I hope) and writing std::unique_ptr<T> x =
base::MakeUnique<T>(...) is strictly longer. Now that we're close, I feel
relatively comfortable using the auto x = base::MakeUnique<T> pattern. If you
feel strongly, I can try to be uniform about it in this CL.

   result->SetString("name", command.command_name());
   result->SetString("description", command.description());
   result->SetString("shortcut",