Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(867)

Issue 2046423003: Make OutputDeveloperMessageCode an enum class (Closed)

Created:
4 years, 6 months ago by pkotwicz
Modified:
4 years, 4 months ago
Reviewers:
dominickn, gone
CC:
chromium-reviews, Xi Han
Base URL:
https://chromium.googlesource.com/chromium/src.git@master
Target Ref:
refs/pending/heads/master
Project:
chromium
Visibility:
Public.

Description

Make OutputDeveloperMessageCode an enum class BUG=609122

Patch Set 1 #

Patch Set 2 : Merge branch 'master' into create_webapk_requirements_enum_class #

Patch Set 3 : Merge branch 'master' into create_webapk_requirements_enum_class #

Unified diffs Side-by-side diffs Delta from patch set Stats (+70 lines, -48 lines) Patch
M chrome/android/java/src/org/chromium/chrome/browser/ShortcutHelper.java View 1 1 chunk +3 lines, -3 lines 0 comments Download
M chrome/browser/android/banners/app_banner_manager_android.cc View 1 3 chunks +10 lines, -5 lines 0 comments Download
M chrome/browser/banners/app_banner_data_fetcher.cc View 1 9 chunks +35 lines, -18 lines 0 comments Download
M chrome/browser/banners/app_banner_debug_log.h View 1 chunk +1 line, -1 line 0 comments Download
M chrome/browser/banners/app_banner_debug_log.cc View 1 chunk +17 lines, -17 lines 0 comments Download
M chrome/browser/banners/app_banner_manager.cc View 1 2 chunks +4 lines, -4 lines 0 comments Download

Messages

Total messages: 9 (3 generated)
pkotwicz
dfalcantara@ can you please take a look? A page is WebAPK capable only if AppBannerDataFetcher::IsManifestValidForWebApp() ...
4 years, 6 months ago (2016-06-08 21:30:53 UTC) #2
pkotwicz
dfalcantara@ can you please take a look? A page is WebAPK capable only if AppBannerDataFetcher::IsManifestValidForWebApp() ...
4 years, 6 months ago (2016-06-08 21:31:35 UTC) #3
gone
Dominick: do you have cycles for this review? It's your code, IIRC.
4 years, 6 months ago (2016-06-08 21:32:12 UTC) #5
dominickn
On 2016/06/08 21:30:53, pkotwicz wrote: > dfalcantara@ can you please take a look? > > ...
4 years, 6 months ago (2016-06-08 23:20:44 UTC) #6
pkotwicz
The reason I am making OutputDeveloperMessageCode an enum class is because I want to: - ...
4 years, 6 months ago (2016-06-08 23:59:44 UTC) #7
dominickn
4 years, 6 months ago (2016-06-09 00:15:08 UTC) #8
On 2016/06/08 23:59:44, pkotwicz wrote:
> The reason I am making OutputDeveloperMessageCode an enum class is because I
> want to:
> - add OutputDeveloperMessageCode::kNone (Using
OutputDeveloperMessageCode::kNone
> feels much more correct than kNone without the class scoping)
> - Change AppBannerDataFetcher::IsManifestValidForWebApp(const
content::Manifest&
> manifest, content::WebContents* web_contents, bool is_debug_mode) to
> AppBannerDataFetcher::IsManifestValidForWebApp(const content::Manifest&
> manifest, OutputDeveloperMessageCode* code)
> 
> Currently, my implementation does not log any messages to the JS console from
> add_to_homescreen_data_fetcher.cc We may want to log to the JS console why an
> app is not WebAPK-eligible but it will require more work

So the primary reason is to be able to pass out an error code for WebAPKs to
report
to console? I'd much rather make the underlying app banner system more generic
than keep extending it in ways it wasn't originally intended to handle. Part of
this is
making the error messages less app-banner specific. They'll read something like,
"Site is not installable: <reason>", which should be generic enough for both app
banners and WebAPKs. Like I said, I'm aiming to have this done for the
next milestone.

Powered by Google App Engine
This is Rietveld 408576698