1
0
mirror of https://github.com/labstack/echo.git synced 2024-12-20 19:52:47 +02:00
High performance, minimalist Go web framework https://echo.labstack.com/
Go to file
2019-03-01 08:27:11 +01:00
_fixture Test cased for Echo#Start/Shutdown 2016-09-24 17:50:38 -07:00
.github Added probot-stale 2018-11-29 16:28:21 -08:00
middleware feat(secure): support Content-Security-Policy-Report-Only header (#1287) 2019-02-26 22:32:07 -08:00
.editorconfig updated docs 2016-11-16 21:26:56 -08:00
.gitattributes Updated website and examples 2017-01-17 10:47:16 -08:00
.gitignore Fixed build 2017-06-28 19:08:45 -07:00
.travis.yml Add go 1.12 to TravisCI (#1294) 2019-02-26 10:15:24 -08:00
bind_test.go Replace http constants with stdlib ones, i.e.: http.MethodGet instead of echo.GET (#1205) 2018-10-14 20:46:58 +05:30
bind.go Remove unreachable code (#1254) 2019-01-28 07:59:36 -08:00
context_test.go Increase Context tests coverage (#1279) 2019-02-19 10:18:42 -08:00
context.go Use concurrency safe context by default. (#1158) 2019-02-12 10:56:26 -08:00
echo_test.go Echo.StartTLS: accept string or []byte as parameters. (#1277) 2019-02-15 09:51:54 -08:00
echo.go feat(secure): support Content-Security-Policy-Report-Only header (#1287) 2019-02-26 22:32:07 -08:00
go.mod Introduced Go module support as v4, removed obsolete CloseNotifier() mechanism 2019-01-30 16:11:42 +02:00
go.sum Introduced Go module support as v4, removed obsolete CloseNotifier() mechanism 2019-01-30 16:11:42 +02:00
group_test.go Replace http constants with stdlib ones, i.e.: http.MethodGet instead of echo.GET (#1205) 2018-10-14 20:46:58 +05:30
group.go Replace http constants with stdlib ones, i.e.: http.MethodGet instead of echo.GET (#1205) 2018-10-14 20:46:58 +05:30
LICENSE Update website 2017-01-09 20:20:51 -08:00
log.go the logging interface add SetHeader method (#1092) 2018-09-28 10:47:23 -07:00
Makefile Updated ci 2018-11-10 11:01:00 -08:00
README.md Introduced Go module support as v4, removed obsolete CloseNotifier() mechanism 2019-01-30 16:11:42 +02:00
response_test.go Replace http constants with stdlib ones, i.e.: http.MethodGet instead of echo.GET (#1205) 2018-10-14 20:46:58 +05:30
response.go Introduced Go module support as v4, removed obsolete CloseNotifier() mechanism 2019-01-30 16:11:42 +02:00
router_test.go tests and fix for findChildByKind executed on nil node 2019-03-01 08:27:11 +01:00
router.go tests and fix for findChildByKind executed on nil node 2019-03-01 08:27:11 +01:00

Sourcegraph GoDoc Go Report Card Build Status Codecov Join the chat at https://gitter.im/labstack/echo Forum Twitter License

Supported Go versions

As of version 4.0.0, Echo is available as a Go module. Therefore a Go version capable of understanding /vN suffixed imports is required:

  • 1.9.7+
  • 1.10.3+
  • 1.11+

Any of these versions will allow you to import Echo as github.com/labstack/echo/v4 which is the recommended way of using Echo going forward.

For older versions, please use the latest v3 tag.

Feature Overview

  • Optimized HTTP router which smartly prioritize routes
  • Build robust and scalable RESTful APIs
  • Group APIs
  • Extensible middleware framework
  • Define middleware at root, group or route level
  • Data binding for JSON, XML and form payload
  • Handy functions to send variety of HTTP responses
  • Centralized HTTP error handling
  • Template rendering with any template engine
  • Define your format for the logger
  • Highly customizable
  • Automatic TLS via Let’s Encrypt
  • HTTP/2 support

Benchmarks

Date: 2018/03/15
Source: https://github.com/vishr/web-framework-benchmark
Lower is better!

Guide

Example

package main

import (
	"net/http"

	"github.com/labstack/echo/v4"
	"github.com/labstack/echo/v4/middleware"
)

func main() {
	// Echo instance
	e := echo.New()

	// Middleware
	e.Use(middleware.Logger())
	e.Use(middleware.Recover())

	// Routes
	e.GET("/", hello)

	// Start server
	e.Logger.Fatal(e.Start(":1323"))
}

// Handler
func hello(c echo.Context) error {
	return c.String(http.StatusOK, "Hello, World!")
}

Help

Contribute

Use issues for everything

  • For a small change, just send a PR.
  • For bigger changes open an issue for discussion before sending a PR.
  • PR should have:
    • Test case
    • Documentation
    • Example (If it makes sense)
  • You can also contribute by:
    • Reporting issues
    • Suggesting new features or enhancements
    • Improve/fix documentation

Credits

License

MIT