This repository has been archived by the owner on Feb 17, 2023. It is now read-only.
Refactoring based on co-change dependency #1038
Open
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
… method fromContent: from class ContentDescription to class AbsContent
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Dear all,
My name is Davi Freitas. Currently I am supporting a research project led by Marcos Cesar de Oliveira (a software engineering Phd student). As part of my research project I’m investigating refactoring opportunities that might improve the modularization of Java projects. We developed a tool for this purpose (https://github.com/project-draco), and the tool suggested 1 refactoring that might benefit this project, by moving methods that have frequently changed together to the same module (a Java class). I’m sending this refactoring suggestion in this PR.
Are you willing to integrate these changes? If that is not the case, could you explain why this PR is not useful? This might suggest that keeping things that frequently change together in the same module is not so relevant. Any feedback would be greatly appreciated and could be extremely valuable for our research.
Thank you in advance,
Davi & Marcos.