Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/gwali-1/meeseeks
Lighweight and powerful http router written in Go
https://github.com/gwali-1/meeseeks
go golang router routing
Last synced: about 1 month ago
JSON representation
Lighweight and powerful http router written in Go
- Host: GitHub
- URL: https://github.com/gwali-1/meeseeks
- Owner: Gwali-1
- License: mit
- Created: 2023-06-12T13:25:18.000Z (over 1 year ago)
- Default Branch: main
- Last Pushed: 2023-06-22T23:14:10.000Z (over 1 year ago)
- Last Synced: 2024-01-26T02:35:05.778Z (10 months ago)
- Topics: go, golang, router, routing
- Language: Go
- Homepage:
- Size: 28.3 KB
- Stars: 2
- Watchers: 1
- Forks: 1
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# Meeseeks
Meeseek is lightweight and provides powerful http routing functionality
#### current meeseeks features
- you can have **named parameters** in your routes.
- you can provide **Custom handlers** for `404 Not Found` and `405 Method Not Allowed` responses.
- Sets an `Allow` header for all `405 Method Not Allowed` responses.
- create and register middlewares to be used on all your routes
- Provide `http.HandlerFunc` functions as your path handlers and middlewares(straightfoward and easy)
- Zero dependencies.
- lightweight and gives you maximum control
### Installation
```
$ go get github.com/Gwali-1/Meeseeks
```
### Example Usage
```go
package main
import (
"fmt"
"log"
"net/http"
" github.com/Gwali-1/Meeseeks"
func main() {
// Initialize a new meeseeks router.
router := meeseeks.NewMeeseeks()
//register a handler function to handle get request on the /rocket/:name route
//you can use : to denote a named path parameter
//register handlers with route patterns using the http verb named methods on the meeseeks router (currently supports just GET and POST)
router.GET("/rocket/:name", func(w http.ResponseWriter, r *http.Request) {
// Using meeseeks.LoadParam() you can retrieve the path parameter specifed in you route with by passing
//the request context and the parameter name
// request context.
name := meeseeks.LoadParam(r.Context(), "name")
fmt.Fprintf(w, "rocket name is %s", name)
})
err := http.ListenAndServe(":2323", router)
log.Fatal(err)
}
```
### Using Middleware
```go
router := meeseeks.NewMeeseeks()
// The Use() method can be used to register middleware. Middleware registered
//on the router will be available on routes registered after the after the middle are regitration.
router.Use(exampleMiddleware1)
router.Use(exampleMiddleware2)
router.Use(exampleMiddleware3)
router.Use(exampleMiddleware4)
//middleware excution is bottom to top meaning exampleMiddleware4 is executed first in the middleware chain then
//exampleMiddleware3 and so on. This is useful if you need your middleware to execute in a particular order
```
### Things To Note
- You can have conflicting routes such as (e.g. `/posts/:id` and `posts/new`). The order in which they are declared is how they are matched
- Trailing slashes are significant; `/profile/:id` and `/profile/:id/` are not the same and won't match.
- An `Allow` header is automatically set for all `405 Method Not Allowed` responses
- Middleware must be declared _before_ a route in order for it to be used by that route. Any middleware declared after a route won't act on that route.
- For example:
```go
router := meeseeks.NewMeeseeks()
router.Use(middleware1)
router.GET("/foo",foo) // This route will use middleware1 only.
router.Use(middleware2)
router.GET("/bar",bar) // This route will use both middleware1 and middleware2.
```
### Contributing
Feel free to send in any contributions (bug fixes, feature suggestions, etc)
Was motivated to write meeseeks after reading source code for [alexedwards/flow](https://github.com/alexedwards/flow)
### Todo
- in memory session store
- provide in-built middlewares for file serving
- middleware usage tests