Editor diagnostics restored from saved sessions are checked for junk before being shown, so bad data can't garble your screen.
What's wrong with this entry?
Diagnostics restored from a replayed attachment are now sanitized, so a malformed or crafted payload cannot reach the renderer.
- a new
sanitizeDiagnosticFilesstatic drops non-array payloads and logs once per payload shape - file entries are dropped unless they have a string
uriand an array of diagnostics; individual diagnostics are dropped unless they have a string message and numeric range start line and character - missing ranges are normalized, and the count of dropped files and diagnostics is logged once per payload
- severity strings map through an explicit table (error, warning, info, information, hint), and
getSeveritySymbolnow usesObject.hasOwnand rejects non-string input, so a crafted severity cannot reach an inherited property
Dropped a ${o} diagnostics files payload from a replayed attachment, diagnostics files payload from a replayed attachment
Strings lifted out of the shipped bundle, so the claim above can be checked against them.