🌠 KCD
KCD is a grandiose REST helper that wrap your shiny handler into a classic http handler. It manages all you want for building REST services.
This library is opinionated by default but customizable which mean it uses some other libraries like Chi, Logrus... KCD is modular so each pieces of the code that rely on a specific library can be changed.
💪 Example
- Demo simple
- Demo standard http handler
- Bind query parameters
- Bind path parameters
- Bind json body
- Bind context value
- Set default value
- Split string with exploder tag
- Nested struct
- Validation
- Errors
- Real world example: pagination
🚀 QuickStart
package main
import (
"fmt"
"net/http"
"github.com/go-chi/chi"
"github.com/go-chi/chi/middleware"
"github.com/alexisvisco/kcd"
)
func main() {
r := chi.NewRouter()
r.Use(middleware.RequestID)
// You can configure kcd with kcd.Config
r.Get("/{name}", kcd.Handler(YourHttpHandler, http.StatusOK))
// ^ Here the magic happen this is the only thing you need
// to do. Adding kcd.Handler(your handler)
_ = http.ListenAndServe(":3000", r)
}
// CreateCustomerInput is an example of input for an http request.
type CreateCustomerInput struct {
Name string `path:"name"` // you can extract value from: 'path', 'query', 'header', 'ctx'
Emails []string `query:"emails" exploder:","` // exploder split value with the characters specified
Subject string `json:"body"` // it also works with json body
}
// CreateCustomerOutput is the output type of the http request.
type CreateCustomerOutput struct {
Name string `json:"name"`
}
// YourHttpHandler is your http handler but in a shiny version.
// You can add *http.ResponseWriter or http.Request in params if you want.
func YourHttpHandler(in *CreateCustomerInput) (CreateCustomerOutput, error) {
// do some stuff here
fmt.Printf("%+v", in)
return CreateCustomerOutput{Name: in.Name}, nil
}Install
go get github.com/alexisvisco/[email protected]Compatibility with framework
- chi (by default)
- gorilla/mux
- gin
- echo
☕ Benefits
- More readable code
- Focus on what it matters: business code
- No more code duplication with unmarshalling, verifying, validating, marshalling ...
- You could have one interface for the client and server implementation