swagger-api / swagger-api/swagger-codegen
[GO] server codegen uses gorilla/mux which is no longer maintained.
Nobody has claimed this yet.
- Dominant language
- Mustache
- Stars
- 17.8k
- Forks
- 6k
- PR merge metrics
- No merged PRs in 30d
Description
Description
Hi all!
I just noticed the Go Server Stub is using the gorilla/mux package. I believe this is no longer maintained as of Dec. 2022. Are there any plans to update that template?
Thanks for taking time to look at this, and all the work to keep swagger going!
Swagger-codegen version
current
Swagger declaration file content or url
n/a
Command line used for generation
n/a
Steps to reproduce
n/a
Related issues/PRs
https://github.com/gorilla/mux
Suggest a fix/enhancement
Open to other options, but using chi seems like a good option.
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 modules/swagger-codegen/src/main/resources/go-server/routers.mustache and inspect how the generated Go server wires in gorilla/mux. Compare the available router replacement options, including chi, and verify the generated server no longer depends on the unmaintained package.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, tooling
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100