Closed KOLANICH closed 1 year ago
Not any file based repo: there are a lot of design decisions encoded in those classes (many not git-related, that's true). There are definitely other file based designs that will not want to make the same decisions.
That's why
of the same structure.
:)
GitRepository and GitMetadata combined are less than 200 lines of code: if this issue is saying that they should be further divided into something, it's unlikely to happen in this project.
If the issue is about naming: I think "git" is the defining feature for this Repository implementation.
So closing, please reopen if you disagree with any of those
if this issue is saying that they should be further divided into something
Yes, it was about this.
OK.
_git
is only called inclose
andadd_target
, the rest of functionality should suit any file-based repo of the same structure.