Open labra opened 1 year ago
After more thinking...maybe it is not necessary to remove the repo, but just to mode the code in the utils
module to different sub-modules which can be independently published as JARs. In this way, it can be easier to update different dependencies and docs, while allowing the consumers of code from this repo to indicate which specific parts they depen on.
The final goal is not to depend on a single shared utils
library with un-connected things...but to depend on more specific jars with more expressive names.
I wonder if this repo is really necessary. At the end, the repo is mostly a "catch-all" repo which contains different utilities for different purposes.
I think this is really an anti-pattern and will try to split the module into other modules/components which have a more clear name and goal.
In this issue we will keep track of the roadmap.
typing
: Contains a genericTyping
type class, it can be extracted to its own repovalidating
: contains a genericChecker
trait that has been implemented in Cats. It was originally implemented using theEff
library. We will remove this module and create a new checker repo.utilsTest
: this module includes JsonMatchers which are no longer used. We may remove the whole module.testSuite
: this module could be extracted as a single repoThe
utils
folder contains the following packages:json
: contains several utilities to work with Json entities in Scala likeDecoderUtils
,JsonCompare
,JsonTest
andJsonTwirl
. We may just create aJsonWeso
repo for those utilitiesEitherUtils
contains two helper methods to work with Either values,sequence
andtakeSingle
. I am not even sure if we use them anymore.FileUtils
contains some helper methods to work with files:getContents
,getFileFromFolderWithExt
,writeFile
,formatLines
, etc.