[ui] Migrate EditFileSystemView to new style and add tests

This CL updates the EditFileSystemView widget from the "Settings"
panel.

The CL replaces the use of `ListWidget` with a one-column DataGrid.
Adding and editing happens in-place while deleting entries is done
via context menu.

The internal implementation of the widget also changes: No longer do
we listen for removed/added events from the model. This is not
strictly necessary since the user is the only one who can update the
excluded sub-directory list so it's enough to get the latest list of
entries when we show the widget.

Another reason is that we also have to show "invalid" entries in the
table, which are not actually synced with the model, only valid ones
are.

R=dsv@chromium.org

Fixed: 407735766
Change-Id: I4ffb7e9baf963b6e5e55ba94fc4e70e7483dc719
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/6540466
Reviewed-by: Danil Somsikov <dsv@chromium.org>
Commit-Queue: Simon Zünd <szuend@chromium.org>
10 files changed
tree: e31b2a2f453c2d953c6e7ade7a23ba7547d4664b
  1. .vscode/
  2. build_overrides/
  3. config/
  4. docs/
  5. extension-api/
  6. extensions/
  7. front_end/
  8. inspector_overlay/
  9. node_modules/
  10. scripts/
  11. test/
  12. third_party/
  13. v8/
  14. .clang-format
  15. .clang-format-ignore
  16. .editorconfig
  17. .git-blame-ignore-revs
  18. .gitallowed
  19. .gitattributes
  20. .gitignore
  21. .gitmodules
  22. .gn
  23. .mailmap
  24. .npmignore
  25. .npmrc
  26. .style.yapf
  27. .stylelintignore
  28. .stylelintrc.json
  29. AUTHORS
  30. BUILD.gn
  31. codereview.settings
  32. CONTRIBUTING.md
  33. DEPS
  34. DIR_METADATA
  35. eslint.config.mjs
  36. favicon.ico
  37. LICENSE
  38. OWNERS
  39. package-lock.json
  40. package.json
  41. PRESUBMIT.py
  42. README.md
  43. tsconfig.json
  44. WATCHLISTS
README.md

Chrome DevTools frontend

npm package

The client-side of the Chrome DevTools, including all TypeScript & CSS to run the DevTools webapp.

Source code and documentation

The frontend is available on chromium.googlesource.com. Check out the Chromium DevTools documentation for instructions to set up, use, and maintain a DevTools front-end checkout, as well as design guidelines, and architectural documentation.

Source mirrors

DevTools frontend repository is mirrored on GitHub.

DevTools frontend is also available on NPM as the chrome-devtools-frontend package. It's not currently available via CJS or ES modules, so consuming this package in other tools may require some effort.

The version number of the npm package (e.g. 1.0.373466) refers to the Chromium commit position of latest frontend git commit. It's incremented with every Chromium commit, however the package is updated roughly daily.

Getting in touch

There are a few options to keep an eye on the latest and greatest of DevTools development: