You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: HISTORY.md
+36
Original file line number
Diff line number
Diff line change
@@ -13,10 +13,46 @@
13
13
### Should I upgrade my Iris?
14
14
15
15
Developers are not forced to upgrade if they don't really need it. Upgrade whenever you feel ready.
16
+
16
17
> Iris uses the [vendor directory](https://docs.google.com/document/d/1Bz5-UB7g2uPBdOx-rw5t9MxJwkfpx90cqG9AFL0JAYo) feature, so you get truly reproducible builds, as this method guards against upstream renames and deletes.
17
18
18
19
**How to upgrade**: Open your command-line and execute this command: `go get -u github.com/kataras/iris`.
19
20
21
+
22
+
# We, 26 July 2017 | v8.1.0
23
+
24
+
The `app.Logger() *logrus.Logger` was replaced with a custom implementation [[golog](https://github.com/kataras/golog)], it's compatible with the [logrus](https://github.com/sirupsen/logrus) package and other open-source golang loggers as well, because of that: https://github.com/kataras/iris/issues/680#issuecomment-316184570.
25
+
26
+
The API didn't change much except these:
27
+
28
+
- the new implementation does not recognise `Fatal` and `Panic` because, actually, iris never panics
29
+
- the old `app.Logger().Out = io.Writer` should be written as `app.Logger().SetOutput(io.Writer)`
30
+
31
+
The new implementation, [golog](https://github.com/kataras/golog) is more featured
32
+
and it completes more use cases than the before external implementation.
33
+
34
+
At general you have to know that the low-level relative fields and functions are actually inside `app.Logger().Printer` object, i.e: `app.Logger().Printer.Output` to get the `io.Writer` or `app.Logger().Printer.AddOuput/SetOutput` to set or add more output(`io.Writer`) targets.
35
+
36
+
### Integration
37
+
38
+
I understand that many of you may use logrus outside of Iris too. To integrate an external `logrus` logger just
39
+
`Install` it-- all print operations will be handled by the provided `logrus instance`.
40
+
41
+
```go
42
+
import (
43
+
"github.com/kataras/iris"
44
+
"github.com/sirupsen/logrus"
45
+
)
46
+
47
+
packagemain(){
48
+
app:= iris.New()
49
+
app.Logger().Install(logrus.StandardLogger()) // the package-level logrus instance
50
+
// [...]
51
+
}
52
+
```
53
+
54
+
For more information about our new logger please navigate to: https://github.com/kataras/golog - contributions are welcomed as well!
55
+
20
56
# Sa, 23 July 2017 | v8.0.7
21
57
22
58
Fix [It's true that with UseGlobal the "/path1.txt" route call the middleware but cause the prepend, the order is inversed](https://github.com/kataras/iris/issues/683#issuecomment-317229068)
Each new release is pushed to the master. It stays there until the next version. When a next version is released then the previous version goes to its own branch with `gopkg.in` as its import path (and its own vendor folder), in order to keep it working "for-ever".
0 commit comments