You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

History

josebarn e2ca326b66 fixing up dockerfile for build and added missing vendor		8 years ago
..
LICENSE	fixing up dockerfile for build and added missing vendor	8 years ago
README.md	fixing up dockerfile for build and added missing vendor	8 years ago
content_type.go	fixing up dockerfile for build and added missing vendor	8 years ago
decoder.go	fixing up dockerfile for build and added missing vendor	8 years ago
render.go	fixing up dockerfile for build and added missing vendor	8 years ago
responder.go	fixing up dockerfile for build and added missing vendor	8 years ago

README.md

render

The render package helps manage HTTP request / response payloads.

Every well-designed, robust and maintainable Web Service / REST API also needs well-defined request and response payloads. Together with the endpoint handlers, the request and response payloads make up the contract between your server and the clients calling on it.

Typically in a REST API application, you will have your data models (objects/structs) that hold lower-level runtime application state, and at times you need to assemble, decorate, hide or transform the representation before responding to a client. That server output (response payload) structure, is also likely the input structure to another handler on the server.

This is where render comes in - offering a few simple helpers and interfaces to provide a simple pattern for managing payload encoding and decoding.

We've also combined it with some helpers for responding to content types and parsing request bodies. Please have a look at the rest example which uses the latest chi/render sub-pkg.

All feedback is welcome, thank you!