GeertJohan / GeertJohan/go.rice
`rice embed-go` doesn't work for go modules beyond v1?
- Dominant language
- Go
- Stars
- 2.4k
- Forks
- 185
- PR merge metrics
- No merged PRs in 30d
Description
The `rice embed-go` command worked while my `go.mod` package was in v1. However, after upgrading my go.mod file so the `module` is using the `/v2` suffix, `rice embed-go` now fails with "error creating embedded box file: open \/rice-box.go: permission denied", where "v1 package path" would be my package's v1 directory under my $GOPATH/pkg/mod.
Is this expected or am I missing something obvious?
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing `rice embed-go` with a `go.mod` module using a `/v2` suffix, then inspect how the command resolves the package path and writes `rice-box.go` under `$GOPATH/pkg/mod`. Done means the command no longer targets the v1 package directory and completes successfully for the v2 module.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100