How can the middleware throw an error and continue the execution of the later middleware?

[JellyTony]

How can the middleware throw an error and continue the execution of the later middleware?

[aldas]

Go does not have concept of "throwing an error". Do you mean panics or just how Echo middleware/handler chain works?

This is barebones example how can decide whether to call next middleware or handler and how you can do additional work after next handler/middleware returns

	e.Use(func(next echo.HandlerFunc) echo.HandlerFunc {
		return func(c echo.Context) error {
			// do some work. and decide if next middleware is worth calling or stop execution by returning an error
			// work work more work
			err := next(c) // call next middleware in chain (in this case next is handler function)
			// do some additional work after next middleware/handler has returned
			return err // return to previous middleware or eventually to global error handler
		}
	})

[JellyTony]

Yes, I write like you above, the middleware behind the panic middleware will not continue to execute

The logging middleware will not continue to execute

[aldas]

This

			defer func() {
				if r := recover(); r != nil {

will be run when there was panic in next middleware - in this case logger, ratelimit or handler. If panic happens in handler panic will "bubble up" until first recover() is seen and middlewares between are "skipped"

I suggest putting recovery just before handler so panic is converted to error. Recovery middleware is "convert panic to error" middleware.