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

Issue 2903063007: WebUI: Linting: Add missing semicolons in local_ntp code. (Closed)

Created:
3 years, 7 months ago by dpapad
Modified:
3 years, 6 months ago
Reviewers:
Marc Treib, Dan Beam
CC:
arv+watch_chromium.org, chromium-reviews, Dan Beam, David Black, donnd+watch_chromium.org, fserb, huangs, jered+watch_chromium.org, jeremycho, jfweitz+watch_chromium.org, kmadhusu+watch_chromium.org, Mathieu, melevin+watch_chromium.org, samarth+watch_chromium.org, samarth, skanuj+watch_chromium.org, Marc Treib
Target Ref:
refs/heads/master
Project:
chromium
Visibility:
Public.

Description

WebUI: Linting: Add missing semicolons in local_ntp code. This is in preparation of enabling http://eslint.org/docs/rules/semi check during PRESUBMIT, which will enforce the following section from the styleguide: https://google.github.io/styleguide/jsguide.html#formatting-semicolons-are-required BUG=720034 TBR=treib@chromium.org CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation Review-Url: https://codereview.chromium.org/2903063007 Cr-Commit-Position: refs/heads/master@{#475625} Committed: https://chromium.googlesource.com/chromium/src/+/248b8502849c81f656d4ae7c7a8329a948108fb1

Patch Set 1 #

Patch Set 2 : Add more files #

Total comments: 2
Unified diffs Side-by-side diffs Delta from patch set Stats (+9 lines, -7 lines) Patch
M chrome/browser/resources/local_ntp/local_ntp.html View 1 1 chunk +1 line, -1 line 0 comments Download
M chrome/browser/resources/local_ntp/local_ntp.js View 3 chunks +6 lines, -4 lines 2 comments Download
M chrome/browser/resources/local_ntp/most_visited_single.js View 1 chunk +1 line, -1 line 0 comments Download
M chrome/browser/search/local_ntp_source.cc View 1 1 chunk +1 line, -1 line 0 comments Download

Messages

Total messages: 20 (13 generated)
dpapad
https://codereview.chromium.org/2903063007/diff/20001/chrome/browser/resources/local_ntp/local_ntp.js File chrome/browser/resources/local_ntp/local_ntp.js (right): https://codereview.chromium.org/2903063007/diff/20001/chrome/browser/resources/local_ntp/local_ntp.js#newcode9 chrome/browser/resources/local_ntp/local_ntp.js:9: // sha256sum local_ntp.js | cut -d " " -f ...
3 years, 7 months ago (2017-05-25 21:28:43 UTC) #5
dpapad
On 2017/05/25 at 21:28:43, dpapad wrote: > https://codereview.chromium.org/2903063007/diff/20001/chrome/browser/resources/local_ntp/local_ntp.js > File chrome/browser/resources/local_ntp/local_ntp.js (right): > > https://codereview.chromium.org/2903063007/diff/20001/chrome/browser/resources/local_ntp/local_ntp.js#newcode9 ...
3 years, 6 months ago (2017-05-30 16:53:34 UTC) #9
dpapad
On 2017/05/30 at 16:53:34, dpapad wrote: > On 2017/05/25 at 21:28:43, dpapad wrote: > > ...
3 years, 6 months ago (2017-05-30 17:01:10 UTC) #12
Dan Beam
lgtm
3 years, 6 months ago (2017-05-30 17:12:23 UTC) #13
commit-bot: I haz the power
CQ is trying da patch. Follow status at: https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.org/2903063007/20001
3 years, 6 months ago (2017-05-30 17:28:53 UTC) #15
commit-bot: I haz the power
Committed patchset #2 (id:20001) as https://chromium.googlesource.com/chromium/src/+/248b8502849c81f656d4ae7c7a8329a948108fb1
3 years, 6 months ago (2017-05-30 19:17:17 UTC) #18
Marc Treib
3 years, 6 months ago (2017-06-07 08:49:34 UTC) #20
Message was sent while issue was closed.
lgtm

Thanks! Sorry for the delay, I was OOO and just got back.

https://codereview.chromium.org/2903063007/diff/20001/chrome/browser/resource...
File chrome/browser/resources/local_ntp/local_ntp.js (right):

https://codereview.chromium.org/2903063007/diff/20001/chrome/browser/resource...
chrome/browser/resources/local_ntp/local_ntp.js:9: // sha256sum local_ntp.js |
cut -d " " -f 1 | xxd -r -p | base64
On 2017/05/25 21:28:43, dpapad wrote:
> It is unfortunate that modifying this file is now much more cumbersome. Could
> this not be done dynamically?
> 
> Regardless of the above, it took quite a bit of effort to figure out how to
> calculate the hash. Let me know if there is an easier way.

If there's a mismatch, you should get an error message in the console that tells
you the expected ID.
Automatically integrating this in the build process would sure be nice, but I
don't know of any good (low-overhead) way to do this. Ideas welcome!

Powered by Google App Engine
This is Rietveld 408576698