Post notification after fetching articles

chrome/browser/ntp_snippets/ntp_snippets_features.cc

Index: chrome/browser/ntp_snippets/ntp_snippets_features.cc
diff --git a/chrome/browser/ntp_snippets/ntp_snippets_features.cc b/chrome/browser/ntp_snippets/ntp_snippets_features.cc
new file mode 100644
index 0000000000000000000000000000000000000000..45b1a386f1c1b4e9650fa2039f75b68c86badf7b
--- /dev/null
+++ b/chrome/browser/ntp_snippets/ntp_snippets_features.cc
@@ -0,0 +1,11 @@
+// Copyright 2016 The Chromium Authors. All rights reserved.
+// Use of this source code is governed by a BSD-style license that can be
+// found in the LICENSE file.
+
+#include "chrome/browser/ntp_snippets/ntp_snippets_features.h"
+
+const base::Feature kContentSuggestionsNotificationsFeature = {
+    "ContentSuggestionsNotifications", base::FEATURE_DISABLED_BY_DEFAULT};

[fhorschig, 2017/01/05 13:24:35]

Wouldn't it make sense to put that into the ntp_snippets namespace?

(Helper functions would then feel home here ... analog to 
/components/ntp_snippets/features.cc)

[sfiera, 2017/01/05 13:35:01]

We don't seem to use that namespace in chrome/browser/ntp_snippets. I would be
happy if it was common practice, though.

[Bernhard Bauer, 2017/01/05 13:40:58]

The rough (i.e. not always followed) rule of thumb is that things in chrome/ go
into the top-level namespace and things in components go into a namespace named
after the component.

+
+const char kContentSuggestionsNotificationsAlwaysNotifyParam[] =
+    "always_notify";