schema

gofiber/schema

Package gofiber/schema converts structs to and from form values.

Per-commit benchmark charts: https://gofiber.github.io/schema/benchmarks/

Example

Here's a quick example: we parse POST form values and then decode them into a struct:

// Set a Decoder instance as a package global, because it caches
// meta-data about structs, and an instance can be shared safely.
var decoder = schema.NewDecoder()

type Person struct {
    Name  string
    Phone string
}

func MyHandler(w http.ResponseWriter, r *http.Request) {
    err := r.ParseForm()
    if err != nil {
        // Handle error
    }

    var person Person

    // r.PostForm is a map of our POST form values
    err = decoder.Decode(&person, r.PostForm)
    if err != nil {
        // Handle error
    }

    // Do something with person.Name or person.Phone
}

Conversely, contents of a struct can be encoded into form values. Here's a variant of the previous example using the Encoder:

var encoder = schema.NewEncoder()

func MyHttpRequest() {
    person := Person{"Jane Doe", "555-5555"}
    form := url.Values{}

    err := encoder.Encode(person, form)

    if err != nil {
        // Handle error
    }

    // Use form values, for example, with an http client
    client := new(http.Client)
    res, err := client.PostForm("http://my-api.test", form)
}

To define custom names for fields, use a struct tag "schema". To not populate certain fields, use a dash for the name and it will be ignored:

type Person struct {
    Name  string `schema:"name,required"`  // custom name, must be supplied
    Phone string `schema:"phone"`          // custom name
    Admin bool   `schema:"-"`              // this field is never set
}

The supported field types in the struct are:

• bool
• float variants (float32, float64)
• int variants (int, int8, int16, int32, int64)
• string
• uint variants (uint, uint8, uint16, uint32, uint64)
• struct
• a pointer to one of the above types
• a slice or a pointer to a slice of one of the above types
• a map with string keys whose values are one of the non-struct types above, a type with a registered converter or an encoding.TextUnmarshaler implementation, or a pointer or slice of those (see below)

Unsupported types are simply ignored, however custom types can be registered to be converted.

Map fields

A map field is filled from keys of the form <field>.<key>, one map entry per key:

type Filter struct {
    Attributes map[string]string   `schema:"attributes"` // attributes.colour=red
    Tags       map[string][]string `schema:"tags"`       // tags.size=m&tags.size=l
    Limits     map[string]int      `schema:"limits"`     // limits.max=10
}

The field name matches case-insensitively like any other field, while the key is kept exactly as sent, and everything after the field name is the key (attributes.a.b gives the key a.b). Each value is decoded as a field of the map's value type would be, so a single-value map takes the last of several values. For a plain built-in value type (a string, bool or number), an empty value adds no entry unless ZeroEmpty is set; any other value type, such as a slice, a pointer or a type with a converter or encoding.TextUnmarshaler, gets an entry decoded from the empty value as such a field would be. A map is allocated on first use and entries are added to an existing one. A map type with a registered converter or an encoding.TextUnmarshaler implementation is decoded as a whole from the field's own key instead.

Decoding Key/Value Pairs

When values arrive one key/value pair at a time, as a parsed query string's do, DecodeValues decodes the pairs without first building the map Decode takes:

keys := []string{"name", "phone", "phone"}
values := []string{"Jane Doe", "555-5555", "555-0100"}

err := decoder.DecodeValues(&person, keys, values)

values[i] is a value of the key keys[i], and a key given more than once has all of its values in the order given, as it would in the map. The two slices must be the same length.

Limits

Keys usually come from a client, so the decoder bounds what they can make it allocate: a key may name at most 64 fields, and a slice index may be at most 1000 (or MaxSize, if lower). One call may also allocate at most 8 MiB in all for the values behind nil pointers on its keys' paths and for the slices it grows, counting the capacity each growth reserves. Maps and file fields are not counted, nor are the slice fields declared on the destination struct itself unless the struct embeds an exported pointer or the call grew eight other slices at a key's first index before them. The first eight slices a call grows at a key's first index grow geometrically, any other slice to exactly the index plus one. A key past a limit is not decoded and is reported under its own name in the returned MultiError, also when IgnoreUnknownKeys is set.

Setting Defaults

It is possible to set default values when encoding/decoding by using the default tag option. The value of default is applied when a field has a zero value, a pointer has a nil value, or a slice is empty.

type Person struct {
    Phone string `schema:"phone,default:+123456"`          // custom name
    Age int     `schema:"age,default:21"`
	Admin bool    `schema:"admin,default:false"`
	Balance float64 `schema:"balance,default:10.0"`
    Friends []string `schema:friends,default:john|bob`
}

The default tag option is supported for the following types:

• bool
• float variants (float32, float64)
• int variants (int, int8, int16, int32, int64)
• uint variants (uint, uint8, uint16, uint32, uint64)
• string
• a slice of the above types. As shown in the example above, | should be used to separate between slice items.
• a pointer to one of the above types (pointer to slice and slice of pointers are not supported).

[!NOTE]
Because primitive types like int, float, bool, unint and their variants have their default (or zero) values set by Golang, it is not possible to distinguish them from a provided value when decoding/encoding form values. In this case, the value provided by the default option tag will be always applied. For example, let's assume that the value submitted in the form for balance is 0.0 then the default of 10.0 will be applied, even if 0.0 is part of the form data for the balance field. In such cases, it is highly recommended to use pointers to allow schema to distinguish between when a form field has no provided value and when a form has a value equal to the corresponding default set by Golang for a particular type. If the type of the Balance field above is changed to *float64, then the zero value would be nil. In this case, if the form data value for balance is 0.0, then the default will not be applied.

☕ Supporters

Fiber is an open-source project that runs on donations to pay the bills, e.g., our domain name, hosting, and serverless infrastructure. If you want to support Fiber, please become a GitHub Sponsor.

_{Tool Sponsors - supporting Fiber with free IDE licenses and AI credits}

📅 Monthly Sponsors

🔥 Fiber Guardian
☕ Fiber Supporter
🪴 Fiber Friend

🎁 One-time Sponsors

🚀 Fiber Hero
🪴 Fiber Friend

License

BSD licensed. See the LICENSE file for details.