matthewmueller / matthewmueller/joy
Investigate fallback $GOPATHs
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.3k
- Forks
- 34
- PR merge metrics
- No merged PRs in 30d
Description
I think we could simplify our importer a bit by having fallback $GOPATHs rather than custom loader logic.
Source: https://groups.google.com/d/msg/golang-nuts/1QGQozhB2SA/fXUV4N5WAgAJ
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 reading the importer and the linked golang-nuts discussion about fallback $GOPATHs. Determine whether fallback GOPATH handling can replace the existing custom loader logic, and define the concrete scope and acceptance criteria before making changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- compilers
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100