go-packages/iris
1
0
Fork 0
mirror of https://github.com/kataras/iris.git synced 2025-03-13 22:26:26 +01:00
Code Issues Actions Packages Projects Releases Wiki Activity

minor misspell

Gerasimos (Makis) Maropoulos 2019-08-12 12:04:08 +03:00
parent 62df999ef3
commit 033b2b4639
No known key found for this signature in database
GPG Key ID: F169457BBDA4ACF4
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Routing-subdomains.md

@ -1,4 +1,4 @@
Iris has the simplest known form for subdomains registration to a single application. Of course you can always use nginx or caddy for managment in production.
Iris has the simplest known form for subdomains registration to a single application. Of course you can always use nginx or caddy for management in production.
Subdomains are separated into two categories: **static** and **dynamic/wildcard**.

2
View.md

@ -1,6 +1,6 @@
Iris offers support for **6 template parsers out of the box** through its universal [View Engine](https://godoc.org/github.com/kataras/iris/view#Engine). Of course developers can still use various go template parsers as the `Context.ResponseWriter()` completes the `http.ResponseWriter` and `io.Writer`.
Iris puts some common rules and features that their original parsers don't support by default. For example we have support for `yield`, `render`, `render_r`, `current`, `urlpath` template funcs and `Layouts` and `binding` accross middlewares and **embedded template files** for all Engines.
Iris puts some common rules and features that their original parsers don't support by default. For example we have support for `yield`, `render`, `render_r`, `current`, `urlpath` template funcs and `Layouts` and `binding` across middlewares and **embedded template files** for all Engines.
To use unique features of a template engine you have to learn the characteristics and the syntax by reading its documentation (click the links below). Choose what fits your app's needs the most.