6.9 KiB
httpin
HTTP Input for Go - Decode an HTTP request into a custom struct
Define the struct for your input and then fetch your data!
Quick View
BEFORE (use net/http) | AFTER (use httpin) |
---|---|
|
|
Features
- Builtin directive
form
to decode a field from HTTP form values, i.e.http.Request.Form
- Builtin directive
query
to decode a field from HTTP querystring parameters, i.e.http.Request.URL.Query()
- Builtin directive
header
to decode a field from HTTP headers, i.e.http.Request.Header
- Builtin decoders used by
form
,query
, andheader
directives for basic types, e.g.bool
,int
,int64
,float32
,time.Time
, ... full list - Decode a field by inspecting a set of keys from the same source, e.g.
in:"form=per_page,page_size"
- Decode a field from multiple sources, e.g. both form, querystring, and headers,
in:"form=access_token;query=token;header=x-api-token"
- Register custom type decoders by implementing
httpin.Decoder
interface - Compose an input struct by embedding struct fields
- Builtin directive
required
to tag a field as required - Builtin directive
body
to parse HTTP request body asJSON
orXML
- Register custom directive executors to extend the ability of field resolving, see directive required as an example and think about implementing your own directives like
trim
,to_lowercase
,base58_to_int
, etc. - Easily integrating with popular Go web frameworks and packages
Example (Use http.Handler)
First, set up the middleware for your handlers (bind Input vs. Handler). We recommend using alice to chain your HTTP middleware functions.
type Authorization struct {
// Decode from multiple sources, the former with higher priority
Token string `in:"form=access_token;header=x-api-token;required"`
}
type Pagination struct {
Page int `in:"form=page"`
// Decode from multiple keys in the same source, the former with higher priority
PerPage int `in:"form=per_page,page_size"`
}
type ListUsersInput struct {
Gender string `in:"form=gender"`
AgeRange []int `in:"form=age_range"`
IsMember bool `in:"form=is_member"`
Pagination // Embedded field works
Authorization // Embedded field works
}
func init() {
http.Handle("/users", alice.New(
httpin.NewInput(ListUsersInput{}),
).ThenFunc(ListUsers))
}
Second, fetch your input with only ONE LINE of code.
func ListUsers(rw http.ResponseWriter, r *http.Request) {
input := r.Context().Value(httpin.Input).(*ListUsersInput)
// Do sth.
}
Integrate with Popular Go Web Frameworks and Packages
Parse HTTP Request Body
There're two ways of parsing HTTP request body into your input struct.
Parse HTTP request body into the input struct (body -> input)
Embed one of our body decoder annotations into your input struct:
// POST /users with JSON body
type CreateUserInput struct {
httpin.JSONBody // annotation
Username string `json:"username"`
Gender int `json:"gender"`
}
httpin.JSONBody
: parse request body in JSON formathttpin.XMLBody
: parse request body in XML format
Parse HTTP request body into a field of the input struct (body -> input.field)
Use body
directive.
// PATCH /users/:uid with JSON body
type UpdateUserProfileInput struct {
UserID int64 `in:"path=uid"` // get user id from path variable
Patch struct {
Username string `json:"username"`
Gender int `json:"gender"`
} `in:"body=json"` // use body=xml to decode in XML format
}
Advanced
🔥 Extend httpin
by adding custom directives
Know the concept of a Directive
:
type Authorization struct {
Token string `in:"form=access_token,token;header=x-api-token;required"`
^---------------------^ ^----------------^ ^------^
d1 d2 d3
}
There are three directives above, separated by semicolons (;
):
- d1:
form=access_token,token
- d2:
header=x-api-token
- d3:
required
A directive consists of two parts separated by an equal sign (=
). The left part is the name of an executor who was designed to run this directive. The right part is a list of arguments separated by commas (,
) which will be passed to the corresponding executor at runtime.
For instance, form=access_token,token
, here form
is the name of the executor, and access_token,token
is the argument list which will be parsed as []string{"access_token", "token"}
.
There are several builtin directive executors, e.g. form
, header
, required
, ... full list. And you can define your own by:
First, create a directive executor by implementing the httpin.DirectiveExecutor
interface:
func toLower(ctx *DirectiveContext) error {
if ctx.ValueType.Kind() != reflect.String {
return errors.New("not a string")
}
currentValue := ctx.Value.Elem().String()
newValue := strings.ToLower(currentValue)
ctx.Value.Elem().SetString(newValue)
return nil
}
// Adapt toLower to httpin.DirectiveExecutor.
var MyLowercaseDirectiveExecutor = httpin.DirectiveExecutorFunc(toLower)
Seconds, register it to httpin
:
httpin.RegisterDirectiveExecutor("to_lowercase", MyLowercaseDirectiveExecutor, nil)
Finally, you can use your own directives in the struct tags:
type Authorization struct {
Token string `in:"form=token;required;to_lowercase"`
}
The directives will run in the order as they defined in the struct tag.