Closed
Bug 1222542
Opened 9 years ago
Closed 9 years ago
Run eslint against all of the ui/ directory not just ui/js/
Categories
(Tree Management :: Treeherder, defect, P2)
Tree Management
Treeherder
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: emorley, Assigned: emorley)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
Since currently the JS files under ui/partials/ and ui/plugins/ are not checked.
Assignee | ||
Comment 1•9 years ago
|
||
Attachment #8684332 -
Flags: review?(wlachance)
Comment 2•9 years ago
|
||
Comment on attachment 8684332 [details] [review]
Run eslint against all of the ui/ directory
I'm a bit concerned that this will run the eslinting rules against files in vendor/, which I don't think is what we want. Is there something I'm missing?
Attachment #8684332 -
Flags: review?(wlachance)
Comment 3•9 years ago
|
||
Comment on attachment 8684332 [details] [review]
Run eslint against all of the ui/ directory
Missed the entry excluding vendors in .eslintrc. Looks good otherwise!
Attachment #8684332 -
Flags: review+
Comment 4•9 years ago
|
||
Commits pushed to master at https://github.com/mozilla/treeherder
https://github.com/mozilla/treeherder/commit/2ff44d7073354fcdca2a459e34c9356e5b05c32a
Bug 1222542 - Fix eslint indentation errors in ui/plugins/*
So we can start running eslint against this directory shortly.
https://github.com/mozilla/treeherder/commit/766838a5c62444776391548d354eb7885a7c4c9c
Bug 1222542 - Run eslint against all of the ui/ directory
Since previously the JS files under ui/partials/ and ui/plugins/ were
omitted. We now need to also explicitly exclude the vendor directory,
which we can do using `.eslintignore`.
This also means that if people prefer to run eslint directly, they
can use `eslint ui/` rather than having to type out the multiple
directories used previously.
Assignee | ||
Updated•9 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Updated•3 years ago
|
Component: Treeherder: Docs & Development → TreeHerder
You need to log in
before you can comment on or make changes to this bug.
Description
•