fill importpath from mod info

[sio4]

When here runs against the go package but there are no go files in the root, here should provide valid package information but currently Info.ImportPath is not set even though Info.Module is filled by go.mod.

I think this could be the right direction but not fully sure since there are not enough code comments (even for the exported things) and also there is no design document.

This fix will help to resolve cli issue gobuffalo/cli#142

[sio4]

@paganotoni @fasmat I think this could be fine but I want to hear your opinion, or if I missed something.

[paganotoni]

IMO this is one of those things we should simplify to be an internal packages within the CLI. I say this because in the context where this was written initially we needed to support GOPATH and modules. Buffalo lives a different reality at this point in which we don't support GOPATH mode, and in that sense we might be carrying a lot of technical debt by keeping using packages like this one.

[sio4]

I agree. Some of our toolings are somewhat complex and I hope to make them simple. However, this is about grift which is the core of buffalo task and currently it was broken. (from version 0.18.4, buffalo task is no longer working and it was already released to users)

What do you think? Can we make buffalo work and improve/simplify the structure?

Additionally, I thought bringing markbates/grift into gobuffalo/grift could be one parallel option if we will not throw it away soon.

[sio4]

Also dropping GOPATH part from here could be a good thing too.

At the same time, I found a lot of packages indirectly depend on here too. I checked some of them, they depend on here via pkger or some other buffalo-related packages. I think we can keep them using it as v0 or v1, and we can go forward as v2.

[sio4]

@paganotoni Could you please take a look at this issue again? currently buffalo task is broken in the cli version 0.18.4 and this PR will be the start point of the fix. If you think of another approach, please let me know. I would like to fix the issue as soon as possible since the issue could break buffalo users' workflows.