Swallow exceptions when calling toString on ConfigProxy objects #743
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
nowucca
approved these changes
Feb 13, 2025
I like ignore as well here, switched to ignore |
rgallardo-netflix
approved these changes
Feb 14, 2025
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.
We are currently running into an issue where a user has extended the ConfigProxy interface in a custom manner, adding support for, effectively, Map<String, JSONObject>. We do not support this kind of map (as our decoders assume that a single value is decoded into values, instead of collapsing a tree into a single object).
We want to avoid unnecessary logging for this case, so specifically for the toString call on ConfigProxy objects, we choose to swallow exceptions.