commit | d3b2fc4408deb8d33967dc3d3417ff25dbd870e0 | [log] [tgz] |
---|---|---|
author | Danil Somsikov <dsv@chromium.org> | Tue Apr 04 09:13:07 2023 |
committer | Devtools-frontend LUCI CQ <devtools-frontend-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Apr 04 10:15:03 2023 |
tree | 14b93c787d2bbbef05ba899ed1788bbcaeb6ed41 | |
parent | 6eddd1061f24c172985554281adf533d72605c70 [diff] |
Use real model in IssuesAggregator_test. This makes the code closer to the real behavior, needed to test the upcoming change with handling scopes. Bug: 1417112 Change-Id: If9e785f496178e5b87b613be2f84a85d2dea725b Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/4397703 Commit-Queue: Danil Somsikov <dsv@chromium.org> Reviewed-by: Wolfgang Beyer <wolfi@chromium.org> Auto-Submit: Danil Somsikov <dsv@chromium.org> Commit-Queue: Wolfgang Beyer <wolfi@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