RPP: disable inactive handlers This CL updates the set of active handlers in the new trace engine to only be the ones that we currently rely on. To do this we define a new constant in the model which lists the active handlers. To then ensure that TypeScript knows which handlers are active (and consequently errors if you try to use data from an inactive handler) we introduce the PartialTraceData type, which is now used throughout the codebase. Once all handlers are active, some of these mechanics can be removed. But by using this type defined in the model, we ensure that we are type safe when accessing data from the new model. Bug: 1420931 Change-Id: I53de24f73ce4d6e0763db7be43ad9c085977d35c Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/4335996 Commit-Queue: Jack Franklin <jacktfranklin@chromium.org> Reviewed-by: Andres Olivares <andoli@chromium.org>
The client-side of the Chrome DevTools, including all JS & CSS to run the DevTools webapp.
The frontend is available on chromium.googlesource.com.
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.
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.
All DevTools commits: View the log or follow @DevToolsCommits on Twitter
All open DevTools tickets on crbug.com
File a new DevTools ticket: new.crbug.com
Code reviews mailing list: devtools-reviews@chromium.org
@ChromeDevTools on Twitter
Chrome DevTools mailing list: groups.google.com/forum/google-chrome-developer-tools