The echo.WrapHandler method feels somewhat redundant.

[dage212]

I’m currently developing my open-source project fire-doc and want to use an any route. My handler is written using Go’s standard library, and I’d like to integrate it with Echo. However, I found that I need to use an additional WrapHandler. Why is this method necessary? Why not keep it consistent with the standard library so that compatibility would be better?

[aldas]

This is because Echo handler has different function signature - mainly the Context interface which has different methods that give you extra functionality when dealing with requests/responses.