Better go module reflection of GOPATH

[matzew]

When creating a project, inside my $GOPATH, like:

func create -l go -t cloudevents      
Created go function in /home/matzew/go/src/github.com/matzew/payments

I was thinking that the go.mod, would reflect this a bit, and be like:

module github.com/matzew/payments

...

But instead it is a generic function module: https://github.com/knative/func/blob/main/templates/go/cloudevents/go.mod#L1

[lance]

@matzew this is an artifact of the way Go functions are currently constructed. The template files which comprise main() are currently part of the buildpack, and expect a module named function.

https://github.com/boson-project/packs/blob/e8e1b3b08ac5599c71e999a52a0ff4c0432baa29/buildpacks/go/faas/main.go#L19

In #1451 I propose a path forward that removes this explicit dependency. (Also potentially in knative/community#1220 which would extract most of what's in #1451 into a new repository).

[matzew]

Ugh, that's quiet some disadvantage, thanks for sharing

[github-actions]

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

[zroubalik]

/remove-lifecycle stale

[github-actions]

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.