[bindings] Rename SymbolizedError to SymbolizedErrorObject
The ConsoleViewMessage knows (roughly) 3 different types of errors:
* Ones it can fully parse and linkify.
* SyntaxErrors, that don't have a stack but where we manually add
a source-mapped location to the description.
* and unparsable errors where we try to linkify anything that looks
like a URL on a best effort basis.
We'll add a dedicated type for all of these under the `SymbolizedError`
union. A widget can then render `SymbolizedError` depending on the
concrete shape.
R=alexrudenko@chromium.org
Bug: 485140575
Change-Id: I2cc207d4c2c0b4c6b1ce4da81efce45317996652
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/7785957
Reviewed-by: Alex Rudenko <alexrudenko@chromium.org>
Commit-Queue: Simon Zünd <szuend@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.