Wrong project name
tredoe opened this issue · 3 comments
tredoe commented
If the package name is "stringy", the project name must be named like it ("stringy"), not "Stringy".
gobeam commented
Okay @tredoe project name police it was named after danielstjules/Stringy because I took inspiration from that package. So nothing wrong with naming it that way.
tredoe commented
The real issue is because when someone import your project using import "github.com/gobeam/Stringy", then the public functions and constants can not be called using "Stringy.SomeFunc()".
That's the reason why all projects in Go are named in lower case.