Replies: 1 comment 2 replies
-
Having a pkg directory would be helpful for plugins so that we could publish interfaces and other utilities for plugin developers |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Currently, all of the kvm functions are under one "kvm" package. I think it would be more beneficial as this project becomes active in the future to condense the features under one package.
All of the files are in the root of the repository which is tacky and hard to search through.
I propose we implement the same style of https://github.com/golang-standards/project-layout which is a basic layout and is not an official standard. I've adopted this layout and it has made so much of a difference when others work on my projects.
We would essentially keep
cmd/
to keep our entry executables, moving/main.go
intocmd/kvm/main.go
ascmd/main.go
just calls that.. We would move some of the some of the functions into their own packages under ainternal/
directory. Any future public clients we would want to write and be importable underpkg/
Beta Was this translation helpful? Give feedback.
All reactions