Closed
Bug 1429223
Opened 3 years ago
Closed 3 years ago
Remove eslintvalidate.py vcs hooks
Categories
(Firefox Build System :: Lint and Formatting, enhancement)
Tracking
(firefox59 fixed)
RESOLVED
FIXED
mozilla59
| Tracking | Status | |
|---|---|---|
| firefox59 | --- | fixed |
People
(Reporter: ahal, Assigned: ahal)
References
Details
Attachments
(1 file)
I was helping someone out who's lint hooks were failing. Turns out he was using the old eslintvalidate extension, and upgrading to the new hooks.py method fixed the issue for him (I didn't dig into the issue further). We want to encourage people to use hooks.py anyway, as that does more than just eslint. I propose we remove it in two phases: 1) Modify the eslintvalidate.py hooks to print an error message with a link to the documentation on setting up the new hook. 2) After some period of time (a couple weeks?), remove them entirely. This should prevent people from getting confused by "eslintvalidate not found" errors. This should also get posted to the newsgroups before we do anything.
| Comment hidden (mozreview-request) |
Comment 2•3 years ago
|
||
| mozreview-review | ||
Comment on attachment 8941288 [details] Bug 1429223 - [lint] Obsolete the eslintvalidate hooks by printing error message with upgrade path, https://reviewboard.mozilla.org/r/211564/#review217428 Looks good, we should totally do this now, it has been long enough.
Attachment #8941288 -
Flags: review?(standard8) → review+
| Assignee | ||
Updated•3 years ago
|
Assignee: nobody → ahalberstadt
Status: NEW → ASSIGNED
| Assignee | ||
Comment 3•3 years ago
|
||
Posted an intent to remove to firefox-dev, barring objections I'll land EOD today. Also setting leave-open so we can remove the hooks completely after a couple of weeks.
Keywords: leave-open
Pushed by ahalberstadt@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/912ba3bc7211 [lint] Obsolete the eslintvalidate hooks by printing error message with upgrade path, r=standard8
Comment 5•3 years ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/912ba3bc7211
| Assignee | ||
Comment 6•3 years ago
|
||
It's been a month since the hooks have been printing an error message. It's probably safe to remove the files from the tree now. I ended up filing a new bug for the simple reason that mozreview won't let me push a second unrelated patch with the same bug number.
Updated•3 years ago
|
Product: Testing → Firefox Build System
Updated•3 years ago
|
status-firefox59:
--- → fixed
Target Milestone: --- → mozilla59
Updated•3 years ago
|
Version: Version 3 → 3 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•