[RPP] Add FlowsHandler to parse flows in traces A flow is a logic connection between trace events. We display this connection as arrows between trace events belonging to the same flow. In the trace event format, flows are represented with pairing "flow phase" events. Each flow phase event corresponds to one trace event and indicates the role a trace event plays in a flow (start, step or end). To parse flows, we first handle flow phase events, by creating unique flows with the timestamps of each phase. Then, we place trace events in the flow where their corresponding phase event was placed (if a corresponding flow phase event does exist). In a follow up CL, I'll add flows exported by the flows handler to the InitiatorsHandler. Bug: 381033695 Change-Id: Idf00526dc96614e3c83cc4bdced076e59b10d6fd Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/6049061 Commit-Queue: Andres Olivares <andoli@chromium.org> Reviewed-by: Jack Franklin <jacktfranklin@chromium.org>
The client-side of the Chrome DevTools, including all TypeScript & CSS to run the DevTools webapp.
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.
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.
There are a few options to keep an eye on the latest and greatest of DevTools development:
Follow What's new in DevTools.
Follow Umar's Dev Tips.
Follow these individual Twitter accounts: @umaar, @malyw, @kdzwinel, @addyosmani, @paul_irish, @samccone, @mathias, @mattzeunert, @PrashantPalikhe, @ziyunfei, and @bmeurer.
Follow to g/devtools-reviews@chromium.org mailing list for all reviews of pending code, and view the log, or follow @DevToolsCommits on Twitter.
Checkout all open DevTools tickets on crbug.com
Use Chrome Canary and poke around the experiments.