mirror of https://github.com/react/react-native-devtools-frontend.git synced 2026-10-02 18:11:04 +08:00

Files

T

Nikolay Vitkov d1ebd9e14d [EsLint] Don't use empty blocks

Bug: 397260638
Change-Id: Ibf4389ce952333a7af1877450ded87a480d2041f
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/6298125
Reviewed-by: Benedikt Meurer <bmeurer@chromium.org>
Commit-Queue: Nikolay Vitkov <nvitkov@chromium.org>

2025-02-26 08:30:00 -08:00

lib

[EsLint] Don't use empty blocks

2025-02-26 08:30:00 -08:00

tests

[Eslint] Add a custom rule for enforcing as const in UIStrings

2025-02-21 04:46:52 -08:00

README.md

[test] Add scripts folder to runner

2025-01-23 07:10:53 -08:00

README.md

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.