Post notification after fetching articles

chrome/browser/ntp_snippets/ntp_snippets_features.h

Index: chrome/browser/ntp_snippets/ntp_snippets_features.h
diff --git a/chrome/browser/ntp_snippets/ntp_snippets_features.h b/chrome/browser/ntp_snippets/ntp_snippets_features.h
new file mode 100644
index 0000000000000000000000000000000000000000..02a33f6a938194f8767b6ee8a3b361b8f877c2af
--- /dev/null
+++ b/chrome/browser/ntp_snippets/ntp_snippets_features.h
@@ -0,0 +1,17 @@
+// Copyright 2016 The Chromium Authors. All rights reserved.

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

Do we need that new file because browser features don't belong in
src/components/ntp_snippets/features.{h,cc}?
Couldn't we drop the ntp_snippets_ prefix then for consistency?

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

I don't think that notifications features belong there, since they wouldn't
(can't) be used within the component itself.
There's already a features.cc in the //chrome/browser target, and targets can't
have multiple files with the same basename.

+// Use of this source code is governed by a BSD-style license that can be
+// found in the LICENSE file.
+
+#ifndef CHROME_BROWSER_NTP_SNIPPETS_NTP_SNIPPETS_FEATURES_H_
+#define CHROME_BROWSER_NTP_SNIPPETS_NTP_SNIPPETS_FEATURES_H_
+
+#include "base/feature_list.h"
+
+// Enables and configures notifications for content suggestions.
+extern const base::Feature kContentSuggestionsNotificationsFeature;
+
+// "false": use server signals to decide whether to send a notification
+// "true": always send a notification when we receive ARTICLES suggestions
+extern const char kContentSuggestionsNotificationsAlwaysNotifyParam[];
+
+#endif  // CHROME_BROWSER_NTP_SNIPPETS_NTP_SNIPPETS_FEATURES_H_