Yes, this works and suffices my needs for now. So if I understand right, I should be creating just the single main package and import all other files as packages into the main package. Only then will the documentation show up for my local project as well.
On Monday, March 6, 2017 at 2:42:19 AM UTC+5:30, Rejoy wrote: > > In my local project folder (a web app) that has the go source files, I use > the go run command to get the output. Each of these files is called a > package main. I 'd like to create the documentation for the project. I run > godoc -http=:6060, but don't see any of the source files of my local > project. All I see is the list of subdirectories. > What would be the correct way to do the documentation of the local project > . > Thanks > > > > > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
