iris/HISTORY.md

FAQ

Looking for free support?

http://support.iris-go.com
https://kataras.rocket.chat/channel/iris

Looking for previous versions?

https://github.com/kataras/iris#version

Should I upgrade my Iris?

Developers are not forced to upgrade if they don't really need it. Upgrade whenever you feel ready.

Iris uses the vendor directory feature, so you get truly reproducible builds, as this method guards against upstream renames and deletes.

How to upgrade: Open your command-line and execute this command: go get -u github.com/kataras/iris. For further installation support, please click here.

About our new home page

http://iris-go.com

Thanks to Santosh Anand the http://iris-go.com has been upgraded and it's really awesome!

Santosh is a freelancer, he has a great knowledge of nodejs and express js, Android, iOS, React Native, Vue.js etc, if you need a developer to find or create a solution for your problem or task, please contact with him.

The amount of the next two or three donations you'll send they will be immediately transferred to his own account balance, so be generous please!

Sa, 10 June 2017 | v7.0.3

• New context.Session().PeekFlash("key") added, unlike GetFlash this will return the flash value but keep the message valid for the next requests too.
• Complete the httptest example.
• Fix the (marked as deprecated) ListenLETSENCRYPT function.
• Upgrade the iris-contrib/middleware including JWT, CORS and Secure handlers.
• Add OAuth2 example -- showcases the third-party package goth integration with Iris.

Community

• Add github integration on https://kataras.rocket.chat/channel/iris , so users can login with their github accounts instead of creating new for the chat only.

Th, 08 June 2017 | v7.0.2

• Able to set immutable data on sessions and context's storage. Aligned to fix an issue on slices and maps as reported here.

We, 07 June 2017 | v7.0.1

• Proof of concept of an internal release generator, navigate here to read more.
• Remove tray icon "feature", click here to learn why.

Sa, 03 June 2017

After 2+ months of hard work and collaborations, Iris version 7 was published earlier today.

If you're new to Iris you don't have to read all these, just navigate to the updated examples and you should be fine:)

Note that this section will not cover the internal changes, the difference is so big that anybody can see them with a glimpse, even the code structure itself.

Changes from v6

The whole framework was re-written from zero but I tried to keep the most common public API that iris developers use.

Vendoring /w update

The previous vendor action for v6 was done by-hand, now I'm using the go dep tool, I had to do some small steps:

• remove files like testdata to reduce the folder size
• rollback some of the "golang/x/net/ipv4" and "ipv6" source files because they are downloaded to their latest versions by go dep, but they had lines with the typealias feature, which is not ready by current golang version (it will be on August)
• fix "cannot use internal package" at golang/x/net/ipv4 and ipv6 packages
  • rename the interal folder to was-internal, everywhere and fix its references.
• fix "main redeclared in this block"
  • remove all examples folders.
• remove main.go files on jsondiff lib, used by gavv/httpexpect, produces errors on test -v ./... while jd and jp folders are not used at all.

The go dep tool does what is says, as expected, don't be afraid of it now. I am totally recommending this tool for package authors, even if it's in its alpha state. I remember when Iris was in its alpha state and it had 4k stars on its first weeks/or month and that helped me a lot to fix reported bugs by users and make the framework even better, so give love to go dep from today!

General

• Several enhancements for the typescript transpiler, view engine, websocket server and sessions manager
• All Listen methods replaced with a single Run method, see here
• Configuration, easier to modify the defaults, see here
• HandlerFunc removed, just Handler of func(context.Context) where context.Context derives from import "github.com/kataras/iris/context" (on August this import path will be optional)
  • Simplify API, i.e: instead of Handle,HandleFunc,Use,UseFunc,Done,DoneFunc,UseGlobal,UseGlobalFunc use Handle,Use,Done,UseGlobal.
• Response time decreased even more (9-35%, depends on the application)
• The Adaptors idea replaced with a more structural design pattern, but you have to apply these changes:
  • app.Adapt(view.HTML/Pug/Amber/Django/Handlebars...) -> app.AttachView(view.HTML/Pug/Amber/Django/Handlebars...)
  • app.Adapt(sessions.New(...)) -> app.AttachSessionManager(sessions.New(...))
  • app.Adapt(iris.LoggerPolicy(...)) -> app.AttachLogger(io.Writer)
  • app.Adapt(iris.RenderPolicy(...)) -> removed and replaced with the ability to replace the whole context with a custom one or override some methods of it, see below.

Routing

• Remove of multiple routers, now we have the fresh Iris router which is based on top of the julien's httprouter
• Subdomains routing algorithm has been improved.
• Iris router is using a custom interpreter with parser and path evaluator to achieve the best expressiveness, with zero performance loss, you ever seen so far, i.e:
  • app.Get("/", "/users/{userid:int min(1)}", handler),
    • {username:string} or just {username}
    • {asset:path},
    • {firstname:alphabetical},
    • {requestfile:file} ,
    • {mylowercaseParam regexp([a-z]+)}.
    • The previous syntax of :param and *param still working as expected. Previous rules for paths confliction remain as they were.
      • Also, path parameter names should be only alphabetical now, numbers and symbols are not allowed (for your own good, I have seen a lot the last year...).

Click here for details.

It was my first attempt/experience on the interpreters field, so be good with it :)

Context

• iris.Context pointer replaced with context.Context interface as we already mention
  • in order to be able to use a custom context and/or catch lifetime like BeginRequest and EndRequest from context itself, see below
• context.JSON, context.JSONP, context.XML, context.Markdown, context.HTML work faster
• context.Render("filename.ext", bindingViewData{}, options) -> context.View("filename.ext")
  • View renders only templates, it will not try to search if you have a restful renderer adapted, because, now, you can do it via method overriding using a custom Context.
  • Able to set context.ViewData and context.ViewLayout via middleware when executing a template.
• context.SetStatusCode(statusCode) -> context.StatusCode(statusCode)
  • which is equivalent with the old EmitError too:
    • if status code >=400 given can automatically fire a custom http error handler if response wasn't written already.
  • context.StatusCode() -> context.GetStatusCode()
  • app.OnError -> app.OnErrorCode
  • Errors per party are removed by-default, you can just use one global error handler with logic like "if path starts with 'prefix' fire this error handler, else...".
• Easy way to change Iris' default Context with a custom one, see here
• context.ResponseWriter().SetBeforeFlush(...) works for Flush and HTTP/2 Push, respectfully
• Several improvements under the Request transactions
• Remember that you had to set a status code on each of the render-relative methods? Now it's not required, it just renders with the status code that user gave with context.StatusCode or with 200 OK, i.e: -context.JSON(iris.StatusOK, myJSON{}) -> context.JSON(myJSON{}).
  • Each one of the context's render methods has optional per-call settings,
  • the new API is even more easier to read, understand and use.

Server

• Able to set custom underline *http.Server(s) with new Host (aka Server Supervisor) feature
  • Done and Err channels to catch shutdown or any errors on custom hosts,
  • Schedule custom tasks(with cancelation) when server is running, see here
• Interrupt handler task for gracefully shutdown (when CTRL/CMD+C) are enabled by-default, you can disable its via configuration: app.Run(iris.Addr(":8080"), iris.WithoutInterruptHandler)

Future plans

• Future Go1.9's ServeTLS is ready when 1.9 released
• Future Go1.9's typealias feature is ready when 1.9 released, i.e context.Context -> iris.Context just one import path instead of todays' two.