Which parts of the go-toolkit should be moved here? #24
-
This repository is planned to be, intially, mostly comprised of code currently residing in the go-toolkit repo. The obvious portion of the code consists of what is currently called the |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
I would say everything that is directly used by the CLI commands and that we don't want to offer as a Go API to integrators. So the remote fetchers should probably stay in the Go toolkit, as I guess they could be useful if someone implement their own publication server using the Go API, or if they want to open a remote publication. |
Beta Was this translation helpful? Give feedback.
I would say everything that is directly used by the CLI commands and that we don't want to offer as a Go API to integrators.
So the remote fetchers should probably stay in the Go toolkit, as I guess they could be useful if someone implement their own publication server using the Go API, or if they want to open a remote publication.