Martti T.

At this point - routes (adding a route, note: there is no way to remove a route) or any of the echo fields is not meant to be mutated after...

I really can not say what intentions @vishr had but `echo.Echo` fields are public since `v3`. Probably assumptions is that getters are annoying when 99.9% cases users do not change...

Probably is related to https://github.com/labstack/echo/blob/7f502b1ff10913aeab28abab64f2bf45952c768d/group.go#L28-L29 when group is created it adds 2 routes so middlewares will be executed for that group in case of 404

well it depends. for router [match](https://github.com/labstack/echo/blob/7f502b1ff10913aeab28abab64f2bf45952c768d/router.go#L554) created by `.Any` is a valid route. `Any` adds a route for `POST` that results 404. Router does not know that result would be...

If you comment out ```go //g.Any("", NotFoundHandler) //g.Any("/*", NotFoundHandler) ``` you would get 405 but this means that your Logger middleware will not be fired for that request. When logger...

well, removing those 2 lines would probably be surprise after update for some (probably rare cases?). We are planning to remove those lines in `v5` but it is far in...

@ymotongpoo Logger middleware and echo.Logger are 2 different things. So `e.Logger.SetLevel(0)` is not related to what specifically Logger mw logs. Logger mw is about logging request/response related info but `logger.SetLevel`...

we could add some callback that takes in that line buff, context and error and developer can add whatever he/she chooses by that. Currently we have in unreleased state this...

@ymotongpoo `v4.6.0` has been released. You might want to try [request logger middleware](https://github.com/labstack/echo/blob/master/middleware/request_logger.go)

assumption was that timestamps are added by logging library but I get what you mean - are timestamps for beginning of the request or end of request. I'll add field...