cloudfoundry / cloudfoundry/go-pubsub
pubsub-gen assumes repos live in GOPATH
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 57
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
The current implementation of pubsub-gen assumes dependencies and repos exist in the GOPATH, which golang has moved away from in favor of modules and workspaces.
In order to use pubsub-gen I have to manually clone repos into some directory I've designated as the GOPATH, as go get is module-aware now and will not install whole repos into the GOPATH.
This tool should use some other mechanism to determine where structs live, either:
- use a direct path to determine the package;
- or, use workspaces to determine the relative path;
- or, some combination of both.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the pubsub-gen implementation and tracing how it resolves dependencies and struct packages through GOPATH. The work is done when it can determine those packages using direct paths, workspaces, or both, without requiring repositories to be manually cloned into GOPATH.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100