Added a fix for resolving names to static inner classes #1212
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
amandelpie
force-pushed
the
amandelpie/feature-1172
branch
from
a9bbba9 to
115132a
Compare
EgorkaKulikov
approved these changes
Oct 28, 2022
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.
Description
In the existing solution, we could get the symbol
$in the class names of the parameters due to the canonical name of java classes. But this symbol can not be used in JavaDoc and should be replaced with the dot symbol.Also some tests were added and related to the cases submitted by @alisevych and @EgorkaKulikov
Fixes #1172
Type of Change
How Has This Been Tested?
Automated Testing
Manual Scenario
Run the proposed solution on the example from the module
utbot-sample/org.utbot.examples.unsafe/UnsafeWithFieldand see the resolved names in JavaDocs for@methodUnderTesttag