Fix error messages for UseDotNetV2 #20225
Merged
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
Replaced the mocker run method with the async version
…dotnetv2-error-messages' into users/DenisRumyantsev/v-denikulin-fix-usedotnetv2-error-messages
DenisNikulin5
approved these changes
Jul 30, 2024
max-zaytsev
approved these changes
Jul 30, 2024
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.
Task name: UseDotNetV2
Description: Fixed a bug with error messages when "{}" string was printed instead of exception message. The root cause of the issue is a wrong conversion of JS object to string (using JSON.stringify) since it could work only with enumerable properties.
Documentation changes required: (Y/N) N
Added unit tests: (Y/N) N
Attached related issue: (Y/N) #20159
Checklist:
Copied from this PR.