Running the reporter from another directory

[qax-os]

Running the reporter from another directory

[wgliang]

Thank you for these useful questions：

Feedback：
goreporter -p . -r . -t $GOPATH/src/github.com/wgliang/goreporter/templates/template.html?

• 1.This is my bug,I used to be a strict way to limit the way of writing for -p. In addition, -r you must specify a valid template file(May be my negligence misleading you). Now I fix in rewrite flags and fix project vendors fix#10 .
• 2.Support all vendors.
  If there are errors, please point out.Thanks very much.

[antonsteenvoorden]

Im still having issues when running the reporter in my project folder when using the command you suggested:

[Apollo]2017/04/24 14:56:23 The report path is not specified, and the current path is used by default
[Apollo]2017/04/24 14:56:23 There are no packages that are excepted, review all items of the package
[Apollo]2017/04/24 14:56:23 start code quality assessment...
panic: runtime error: slice bounds out of range

goroutine 1 [running]:
main.DirList.func1(0xc4203c7ac0, 0x14, 0x18d4160, 0xc42043bc70, 0x0, 0x0, 0x0, 0x0)
	/Users/anton/development/go/src/github.com/wgliang/goreporter/utils.go:30 +0x216
path/filepath.walk(0xc4203c7ac0, 0x14, 0x18d4160, 0xc42043bc70, 0xc420101440, 0x0, 0x0)
	/usr/local/Cellar/go/1.8/libexec/src/path/filepath/path.go:351 +0x81
path/filepath.walk(0x7fff5fbffad6, 0x1, 0x18d4160, 0xc42010d790, 0xc420101440, 0x0, 0x30)
	/usr/local/Cellar/go/1.8/libexec/src/path/filepath/path.go:376 +0x414
path/filepath.Walk(0x7fff5fbffad6, 0x1, 0xc420101440, 0xc42010d6c0, 0x0)
	/usr/local/Cellar/go/1.8/libexec/src/path/filepath/path.go:398 +0x14c
main.DirList(0x7fff5fbffad6, 0x1, 0x15a6ea3, 0x8, 0x0, 0x0, 0x1043f85, 0x10, 0x0)
	/Users/anton/development/go/src/github.com/wgliang/goreporter/utils.go:38 +0x1ec
main.(*Reporter).Engine(0xc420164180, 0x7fff5fbffad6, 0x1, 0x0, 0x0)
	/Users/anton/development/go/src/github.com/wgliang/goreporter/engine.go:44 +0x10c
main.main()
	/Users/anton/development/go/src/github.com/wgliang/goreporter/main.go:70 +0x378

Do you have a solution?