fix(RichObjectStrings): Make exception messages for invalid parameters more useful for debugging #51442
+9
−9
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
provokateurin
requested review from
icewind1991,
Altahrim and
yemkareems
and removed request for
a team
|
/backport to stable31 |
provokateurin
force-pushed
the
fix/rich-object-strings/better-exception-messages
branch
from
71f8c4d to
b1b21bf
Compare
…s more useful for debugging Signed-off-by: provokateurin <[email protected]>
provokateurin
force-pushed
the
fix/rich-object-strings/better-exception-messages
branch
from
b1b21bf to
3c698c6
Compare
nickvergessen
approved these changes
Mar 12, 2025
8 tasks
provokateurin
deleted the
fix/rich-object-strings/better-exception-messages
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Makes it easier to figure what exactly is wrong, given that only the value was currently logged and this was not enough to properly debug it even with an available stacktrace.
Checklist