[FIX] Update StringExtension method to vaidate JSON before parsing #151
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Refactor of VerifyBodyContent Method in StringExtension:
Added validation to the VerifyBodyContent method to check the input string for valid JSON format before attempting to parse it. Previously, if the input was an empty string or invalid JSON, it would throw an exception, triggering the catch block. While the exception was handled, the unnecessary overhead of a try-catch block—particularly for scenarios where the input is clearly invalid—was avoided by performing the validation upfront. This improves performance by reducing unnecessary exception handling overhead, which can be costly.