Post-Implementation refactoring of application #9
No reviewers
Labels
No labels
blocked
bug
duplicate
enhancement
help wanted
invalid
meta
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: jotoho/waituntil#9
Loading…
Reference in a new issue
No description provided.
Delete branch "refactoring"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Now that the software's initial implementation is completed, I want to try and improve the readability and maintainability of this tool by extracting logic and functionality from start.kt into smaller files and doing some minor internal refactoring. I also hope to do some sort of automated testing (writing tests) but that may be another PR.
Post-Implementation refactoring of applicationto WIP: Post-Implementation refactoring of applicationa9cde56333
to92a226dd02
WIP: Post-Implementation refactoring of applicationto Post-Implementation refactoring of applicationThis MR is quite a leap in technical and maintainablity terms compared to the current state of
master
.I have been able to get rid of the annoying app directory, the project now automatically uses the newest versions of it's dependencies, the formatting of the code and build files has been modified to be more in line with Kotlin style guidelines and many more improvements have been made while the behaviour and user-experience remains exactly the same - which is the goal of a refactoring.
Because of this and my testing regarding the MR, I believe that it is now ready for merging and significant enough to warrant a new patch release (
0.1.1
). I will mark and publish that release version after the merge is complete.MERGING WITHOUT APPROVALS due to being the only developer.