Is your feature request related to a problem? Please describe.
How about extending support for frameworks like Gin and Echo similarly? I was looking for something similar for Gin and modified some of this library's components to achieve it.
Describe the solution you'd like
- Create separate packages for each framework/default HTTP package.
- Reuse versioning and deprecation packages.
- Add examples for each framework.
Describe alternatives you've considered
- I tried to wrap the existing solution for gin but figured that instead, we could segregate it and make it more readable.
(I have the wrapper solution for Gin ready for the PR, Let me know if you would like to review it.)
- Also it should not affect the end user, as
go mo tidy would remove the unused indirect dependency on the user end.
Additional context
I would like to work on the solution, let's discuss potential pitfalls and outcomes. Looking forward to contribute.
(If this repository is not actively maintained, I would like to create one for Gin and Echo using a similar idea 😉.)
Is your feature request related to a problem? Please describe.
How about extending support for frameworks like Gin and Echo similarly? I was looking for something similar for Gin and modified some of this library's components to achieve it.
Describe the solution you'd like
Describe alternatives you've considered
(I have the wrapper solution for Gin ready for the PR, Let me know if you would like to review it.)
go mo tidywould remove the unused indirect dependency on the user end.Additional context
I would like to work on the solution, let's discuss potential pitfalls and outcomes. Looking forward to contribute.
(If this repository is not actively maintained, I would like to create one for Gin and Echo using a similar idea 😉.)