Move all utility classes into a separate module #194
Closed
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
Extracts a majority of the utility classes into a separate module. I've made changes to the existing API to avoid package conflicts between the parent module and the newly introduced
util
module.The
util
module consists of the following package structureThe remaining utility classes in the parent module will not, and should, be included into the new module since they are tightly coupled to the module they are currently in. In doing so, we're also able to create and maintain a unidirectional dependency tree.