Open sujaypatil96 opened 2 years ago
Great, @sujaypatil96 . I'll review this in the next day or two.
@sujaypatil96 can you please make sure that #47 gets merged in? I can do that if you tell me a good time to do it.
My contributions for enum annotation need major refactoring, but I don't mean to say you should do that.
@sujaypatil96 - these still seem like a good list of things to do, is the idea that it's just a very low priority? :) If not going to be completed in a reasonable amount of time, maybe we unassign and close?
@sierra-moxon: yup, this was just low priority at the time. I can put this issue in our backlogs, add a low priority label, and unassign myself. A new person coming into the repo can look and it and take it up if he/she has the time.
Some practices we can choose to follow in order to tidy the repository contents:
__init__.py
file and turn it into a package. Similarly, we can add an__init__.py
within each of the sub folders, making each of them sub packageslocal
folder necessary?pre_poetry
has contents which were present before the current version of the repo? This can be removed because we can always get to that version by going back through the commit historytarget
folder? Unless there are paths in the source CLIs that default to this path, I think we can safely remove this and allow the users to configure the target folders themselves?CC: @cmungall @turbomam