Closed Bug 1783422 Opened 4 years ago Closed 4 years ago

Enable additional ESLint rules relevant for selfhosted code

Categories

(Core :: JavaScript Engine, task, P1)

task

Tracking

()

RESOLVED FIXED
105 Branch
Tracking Status
firefox105 --- fixed

People

(Reporter: anba, Assigned: anba)

Details

Attachments

(5 files)

No description provided.

These rules should only be applied to self-hosted code, but not for example to
the .eslintrc.js file itself.

Enable this rule to avoid regressing bug 1780517 over time.

Depends on D153848

We have to be extra careful not to use x == null, otherwise we might introduce
spec compliance bugs. For example the two changes in "Tuple.js" are actually bugs
uncovered by this rule.

Depends on D153849

Self-hosted code is implicitly strict mode. Any extra strict mode directive
is probably an error.

Depends on D153850

Report an error for disallowed syntax. Either the parser or the byte code
emitter will assert when restricted syntax is encountered, but this rule
allows to reject invalid syntax directly when linting.

Depends on D153851

Severity: -- → N/A
Priority: -- → P1
Pushed by andre.bargull@gmail.com: https://hg.mozilla.org/integration/autoland/rev/8784c2316a4d Part 1: Move self-hosted code specific ESLint rules into the "overrides" section. r=Standard8 https://hg.mozilla.org/integration/autoland/rev/f1222ec4d3e2 Part 2: Enable "no-void" ESLint rule. r=tcampbell https://hg.mozilla.org/integration/autoland/rev/1dfe7568c39e Part 3: Enable "eqeqeq" ESLint rule. r=tcampbell https://hg.mozilla.org/integration/autoland/rev/e3863be25196 Part 4: Enable "strict" ESLint rule. r=tcampbell https://hg.mozilla.org/integration/autoland/rev/7d338be64b49 Part 5: Enable "no-restricted-syntax" ESLint rule. r=tcampbell
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: