Replace Kotlin setters with direct property access for models from Fuzzer #1241 #1243
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.
Description
Previously calls to Kotlin setters in Fuzzer models were not replaced with direct accesses because check
fieldId.setter == methodId
failed due to different types of operands (MethodId
vsFuzzerMockableMethodId
, seeExecutableId.equals()
). Now this check is rewritten with new methoddescribesSameMethodAs
that checks onlydeclaringClass
andsignature
but ignores javaClass.Fixes #1241
Type of Change
How Has This Been Tested?
Manual Scenario
Checked on scenario from #1241 -- works as expected
Checklist (remove irrelevant options):
This is the author self-check list