Unable to generate spec (bitrot in schematyper dependency)
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 974
- Forks
- 296
- Avg merge
- 6d 14h
- Merged PRs (30d)
- 9
Description
Bug
The generate script depends on https://github.com/idubinskiy/schematyper, but this dependency is unmaintained and uninstallable since 2023.
There's an upstream pull request that should fix this, but it's just sitting there:
https://github.com/idubinskiy/schematyper/pull/22
If this has been already solved (for instance by forking), then the docs need to be updated.
Expected Behavior
go get should install the dependency.
Actual Behavior
$ go get -u github.com/idubinskiy/schematyper
go: gopkg.in/alecthomas/kingpin.v2@v2.4.0: parsing go.mod:
module declares its path as: github.com/alecthomas/kingpin/v2
but was required as: gopkg.in/alecthomas/kingpin.v2
trying gopkg.in/alecthomas/kingpin.v2@v2.3.2
go: gopkg.in/alecthomas/kingpin.v2@v2.3.2: parsing go.mod:
module declares its path as: github.com/alecthomas/kingpin/v2
but was required as: gopkg.in/alecthomas/kingpin.v2
trying gopkg.in/alecthomas/kingpin.v2@v2.3.1
go: gopkg.in/alecthomas/kingpin.v2@v2.3.1: parsing go.mod:
module declares its path as: github.com/alecthomas/kingpin/v2
but was required as: gopkg.in/alecthomas/kingpin.v2
trying gopkg.in/alecthomas/kingpin.v2@v2.3.0
go: gopkg.in/alecthomas/kingpin.v2@v2.3.0: go.mod has non-....v2 module path "github.com/alecthomas/kingpin" at revision v2.3.0
restoring gopkg.in/alecthomas/kingpin.v2@v2.2.6
Reproduction Steps
- uninstall schematyper if already present, clear package cache
- go get -u github.com/idubinskiy/schematyper
Contributor guide
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 with the generate script and reproduce the go get -u github.com/idubinskiy/schematyper failure after clearing the package cache. Check whether the upstream schematyper pull request or another maintained source resolves installation; done means the dependency can be installed, or the documentation accurately points to the working solution.
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