iris/_examples/http_responsewriter/herotemplate
2018-03-08 05:21:16 +02:00
..
template create a new package, name it as hero, I was thinking super or superb but hero is better name for what it does - the goal is to split the new 'mvc handlers' from the mvc system because they are not the same, users should know that they can use these type of rich binded handlers without controllers as well, like a normal handler and that I implemented here, the old files exist on the mvc package but will be removed at the next commit, I have to decide if we want type aliases for Result or no 2017-12-25 20:05:32 +02:00
app.go add examples for read using custom decoder per type, read using custom decoder via iris#UnmarshalerFunc and to complete it add an example for the context#ReadXML. 2018-03-08 05:21:16 +02:00
README.md create a new package, name it as hero, I was thinking super or superb but hero is better name for what it does - the goal is to split the new 'mvc handlers' from the mvc system because they are not the same, users should know that they can use these type of rich binded handlers without controllers as well, like a normal handler and that I implemented here, the old files exist on the mvc package but will be removed at the next commit, I have to decide if we want type aliases for Result or no 2017-12-25 20:05:32 +02:00

Hero Template Example

This folder contains the iris version of the original hero's example: https://github.com/shiyanhui/hero/tree/master/examples/app.

Iris is 100% compatible with net/http so you don't have to change anything else except the handler input from the original example.

The only inline handler's changes were:

From:

if _, err := w.Write(buffer.Bytes()); err != nil {
// and
template.UserListToWriter(userList, w)

To:

if _, err := ctx.Write(buffer.Bytes()); err != nil {
// and
template.UserListToWriter(userList, ctx)

So easy.

Read more at: https://github.com/shiyanhui/hero