[go: nahoru, domu]
Google Git
Sign in
chromium / devtools / devtools-frontend / 20c2c5b4e7331aa14c9656db6ac42514a607526f
commit20c2c5b4e7331aa14c9656db6ac42514a607526f[log] [tgz]
authorAndrés Olivares <andoli@chromium.org>Mon Jul 31 12:15:59 2023
committerDevtools-frontend LUCI CQ <devtools-frontend-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed Aug 02 08:32:29 2023
treee0afd10da31349a7f2c82bcb21bcd6f3095b6bfa
parent4c24b67a1679d52b45545f0c96c48727dbb475e8 [diff]
[RPP] Mark renderer and samples handlers as optional during migration

With https://crrev.com/c/4729647 in place, we are now executing all
handlers when running from the component example. However, our types do
not reflect that yet.

This CL updates the migration types to mark the renderer and samples
handlers as optional properties, so that we have type support for them
when trying to render thread tracks with the new engine. Otherwise, they
would not exists from TS perspective and we won't be able to use their
data.

Bug: 1428024
Change-Id: I2e105b9f4ab526e6c0d448854cdc39a38fa7cae2
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/4733292
Commit-Queue: Andres Olivares <andoli@chromium.org>
Reviewed-by: Jack Franklin <jacktfranklin@chromium.org>
1 file changed
tree: e0afd10da31349a7f2c82bcb21bcd6f3095b6bfa
  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. .editorconfig
  16. .eslintignore
  17. .eslintrc.js
  18. .git-blame-ignore-revs
  19. .gitattributes
  20. .gitignore
  21. .gn
  22. .mailmap
  23. .npmignore
  24. .npmrc
  25. .style.yapf
  26. .stylelintignore
  27. .stylelintrc.json
  28. AUTHORS
  29. BUILD.gn
  30. codereview.settings
  31. DEPS
  32. LICENSE
  33. OWNERS
  34. package-lock.json
  35. package.json
  36. PRESUBMIT.py
  37. README.md
  38. tsconfig.json
  39. WATCHLISTS
README.md

Chrome DevTools frontend

npm package

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

Source code

The frontend is available on chromium.googlesource.com.

Project documentation

Check out the project documentation for instructions to set up, use, and maintain a DevTools front-end checkout, as well as design guidelines, and architectural documentation.

Additional references

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