Additional refactoring to maintain cohesion and solid principles. #1059
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.
Hello,
I have refactored some code in the project.
Refactor : Rename Variable
Description : The variables didn’t explain the exact use. The fetched value was a fraction and not percentage. The Aliphatic index is converted into percentage at the end. The formulation was also broken down for readability.
Refactor : Extract Class
Description: Separated file network operations and basic read write operations to different utility class to have single principle property.
Refactor : Move method
Description : The method convertDNAtoProteinSequence in ProteinMappingTools.java was very specific to DNASequence.java class and hence the code was refactored to move the method to maintain cohesion.
Refactor : Pull up method
Description : The GeneSequence class along with other classes qualify for Broken Hierarchy Design smell. Upon further analysis, it can be seen that the getLength() method can be pulled up the hierarchy. That is what this refactoring does.
A new class DNAExtractSequence is introduced to handle this situation which extends the original DNASequence.