[PR #14668] Fix an issue where JsonUtils produces a bad error message #30203

Open
opened 2026-01-31 09:39:19 +00:00 by claunia · 0 comments
Owner

Original Pull Request: https://github.com/microsoft/terminal/pull/14668

State: closed
Merged: Yes


CascadiaSettings relies on getting a JsonUtils::DeserializationException
from the various JSON Utility functions, and then formatting that into
an error message. Well, DeserializationException tries to include an
object representation in its what() message . . . and generates an
exception trying to do so. CascadiaSettings never gets the
DeserializationException, and displays a weird message.

It's safe to remove the stringification in DeserializationException
because CascadiaSettings was never using it (and because
CascadiaSettings was using an even better version of the same logic.)

Fixes #14373

**Original Pull Request:** https://github.com/microsoft/terminal/pull/14668 **State:** closed **Merged:** Yes --- CascadiaSettings relies on getting a JsonUtils::DeserializationException from the various JSON Utility functions, and then formatting that into an error message. Well, DeserializationException tries to include an object representation in its what() message . . . and generates an exception trying to do so. CascadiaSettings never gets the DeserializationException, and displays a weird message. It's safe to remove the stringification in DeserializationException because CascadiaSettings was never using it (_and_ because CascadiaSettings was using an even better version of the same logic.) Fixes #14373
claunia added the pull-request label 2026-01-31 09:39:19 +00:00
Sign in to join this conversation.
No Label pull-request
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#30203