Skip to content

support building code outside of GOPATH for go module support #1914

@jtnord

Description

@jtnord

If I have a project that is using Go Modules (as opposed to the old GOPATH layout) I would still like to be able to use goagen. Alas it seems goagen will not work at all unless you are using the legacy GOPATH layout.

Expected Behavior

goagen app -d ${PACKAGE_NAME}/${DESIGN_DIR} -o pkg/controller works with no error.

Actual Behavior

goagen errors with

Go source file "C:\workarea\source\github\someorg\some-repo\goagen053437807\design" not in Go workspace, adjust GOPATH C:\PATH\to\go

Steps to Reproduce the Problem (including complete and simple design if relevant)

Specifications

  • goa Version: goagen v1.3.1
  • Platform (Linux/Windows etc.): Windows 10

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions