[Console Insights] Render 'related content' section containing references This CL adds a section containing references to related content to console insights answers. This section is only being rendered if AIDA's response contains `factualityMetadata`, which is only the case when AIDA uses Search RAG. Currently Search RAG needs to be enabled via command line, so this change has no effect on non-testers of Search RAG. Screenshot: https://i.imgur.com/zzCzjL7.png Bug: 381228083 Change-Id: Iaf265e96c6eb58e2a238806b280ccd804a35420f Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/6105676 Reviewed-by: Alex Rudenko <alexrudenko@chromium.org> Auto-Submit: Wolfgang Beyer <wolfi@chromium.org> Commit-Queue: Alex Rudenko <alexrudenko@chromium.org> Commit-Queue: Wolfgang Beyer <wolfi@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.