Closed Bug 910339 Opened 11 years ago Closed 11 years ago

[e.me] Un-ignore jslint

Categories

(Firefox OS Graveyard :: Gaia::Everything.me, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: sonmarce, Assigned: amirn)

Details

Attachments

(1 file)

No description provided.
Blocks: 1.3-e.me
There's much whitespace to be removed, tabs to be replaced with spaces and lines to be broken. Better have it in one PR.
No longer blocks: 1.3-e.me
Assignee: nobody → ran
Status: NEW → ASSIGNED
Summary: [e.me][feature] JsLint all code → [e.me] Un-ignore jslint
Assignee: ran → amirn
Attached file redirect to PR 12854.html (deleted) —
add ?w=1 to the url to hide whitespace diff
Attachment #817118 - Flags: review?(ran)
Attachment #817118 - Flags: review?(evyatar)
Attachment #817118 - Flags: review?(crdlc)
This is a big task. The PR contains only cosmetic changes that I was sure (read hope) will not break the code. There is, however, more "dangerous" linting needed (e.g. breaking lines that are too long) that might break the code. Since this ticket turned out huge already, I suggest it will include only "safe" linting changes. Further linting can be carried out *cautiously* one file at a time, to make sure nothing breaks. What do you think?
Hmm... I think it's good to separate, but if we do - we need to put e.me back on the linting ignore list. otherwise we won't be able to commit because of the long lines. allowing linting should be added back once we're done all linting tasks IMO.
The linting scheme was changed recently and *will not* force you to break long lines when committing your changes. (see https://github.com/mozilla-b2g/gaia/commit/ccfcf9fca37accaab029e78747ebf5ccb3fb19d1) What I did in this PR is to fix all issues that *would* prevent you from committing (double quotes, EOF line breaks etc.)
Please ignore my previous comment - Evyatar is correct. I was running `APP=homescreen make hint` which runs jshint and does not warn about long lines (but warns about other stuff) but the pre-commit hook runs `make lint` which *does* raise 'line too long' errors. I will update the PR once I fix remaining jslint issues. Thanks.
OK guys, updated the PR. Please review. 10x.
Comment on attachment 817118 [details] redirect to PR 12854.html Pretty hard reviewing all the code, obviously, but I flicked through it and it looks good. Built to the device and didn't find any issues.
Attachment #817118 - Flags: review?(evyatar) → review+
Comment on attachment 817118 [details] redirect to PR 12854.html I went over everything. EVERYTHING! There were some comma mistakes that wowed me. Anywho, it's all good and no functional breakage.
Attachment #817118 - Flags: review?(ran) → review+
Comment on attachment 817118 [details] redirect to PR 12854.html I cannot add more :)
Attachment #817118 - Flags: review?(crdlc) → review+
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Btw, Cristian we found what's causing our spacing problem. It had to do with a git setting that messed spacing on every cherry-pick...
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: