CrOS Settings: Fix consistent-type-import ESLint rule for remaining code This change complies with the top-level ESLint spec, specifically the "consistent-type-import" rule. It helps identify which import lines are only used for type-checking and thus can be excluded from the JS output. Also it helps to remove unintentional side effects. Bug: b:372733928 Test: git cl presubmit --force Change-Id: Ie02bd837351b89bdd78d30301fd0ec1d6a2e125a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5980406 Auto-Submit: Wes Okuhara <wesokuhara@google.com> Reviewed-by: Xiaohui Chen <xiaohuic@chromium.org> Commit-Queue: Xiaohui Chen <xiaohuic@chromium.org> Cr-Commit-Position: refs/heads/main@{#1376679}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure.
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.