Fix( Issue #1073): Bug fix for the issue with mocking value classes with coEvery #1332
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
…ses with coEvery. Enable few disabled tests for support nested value classes (issue: 859)
|
@Raibaz Could you please review this PR? |
|
Out of curiosity, why are you converting the class names to strings when doing comparisons? Does the class to class comparison not work? |
|
@Raibaz |
Raibaz
approved these changes
Jan 4, 2025
|
Thanks for putting this together and for the follow up commits! |
3 tasks
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.
Fix( Issue #1073): Bug fix for the issue with mocking value classes with coEvery.
Enable few disabled tests for support nested value classes (issue: 859)