Files
Nikolay Vitkov 99a9104ae9 [test] Add scripts folder to runner
Prototype for run.ts to include all scripts files as well.
This will make it easier to just run a single command.

Bug: none
Change-Id: I0e7e623a777330d320a003a0099518aeeed88821
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/6187112
Reviewed-by: Philip Pfaffe <pfaffe@chromium.org>
Reviewed-by: Benedikt Meurer <bmeurer@chromium.org>
Commit-Queue: Nikolay Vitkov <nvitkov@chromium.org>
2025-01-23 07:10:53 -08:00

845 B

Custom ESLint rules for Chromium DevTools

The lib/ folder contains a set of ESLint rules specific to Chromium DevTools. These rules are executed as part of the

npm run lint

command and implicitly via the Presubmit checks.

We follow the ESLint Rule Naming Conventions and consistently use dashes to separate words (instead of underscores), and prefix all rules that disallow something with no-.

Testing the rules

When writing a custom ESLint rule, place the logic into a file lib/foo.js and add a corresponding test for the logic to tests/foo.test.js.

You can use

npm run test -- ./scripts/eslint_rules/tests

to run the tests for the custom ESLint rules.