Improve interface and implementation support in jump actions#236
Conversation
- Enhanced CorrespondingTypeSearcher to look for tests of supertypes and implementations. - Included concrete implementations in the results when an interface/abstract class is matched. - Excluded 'pure' interfaces/abstract classes from results when concrete implementations are found, unless they have default methods or non-abstract methods. - Added comprehensive tests in InterfaceCorrespondingTypeSearcherTest. Closes #205 Co-authored-by: RoiSoleil <3462260+RoiSoleil@users.noreply.github.com>
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
- Enhanced CorrespondingTypeSearcher to look for tests of supertypes and implementations. - Included concrete implementations in the results when an interface/abstract class is matched. - Excluded 'pure' interfaces/abstract classes from results when concrete implementations are found, unless they have default methods or non-abstract methods. - Optimized subclass search in SearchTools to use SearchEngine instead of full hierarchy. - Added comprehensive tests in InterfaceCorrespondingTypeSearcherTest. Closes #205 Co-authored-by: RoiSoleil <3462260+RoiSoleil@users.noreply.github.com>
- Enhanced CorrespondingTypeSearcher to look for tests of supertypes and implementations. - Included concrete implementations in the results when an interface/abstract class is matched. - Excluded 'pure' interfaces/abstract classes from results when concrete implementations are found, unless they have default methods or non-abstract methods. - Refined TypeHierarchy usage to avoid compilation issues and improve reliability. - Added comprehensive tests in InterfaceCorrespondingTypeSearcherTest. Closes #205 Co-authored-by: RoiSoleil <3462260+RoiSoleil@users.noreply.github.com>
- Fix not working cases
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #236 +/- ##
=======================================
Coverage ? 0
=======================================
Files ? 0
Lines ? 0
Branches ? 0
=======================================
Hits ? 0
Misses ? 0
Partials ? 0 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
The "Jump to Test/Code" functionality in MoreUnit now better supports interfaces and their implementations.
Key changes:
java.lang.*). This allows jumping from a class likeFooImpltoFooTestifFooImplimplementsFoo.InterfaceCorrespondingTypeSearcherTestto verify these navigation scenarios.PR created automatically by Jules for task 18132929899494660556 started by @RoiSoleil