CodeVetter · Repo Unpack · Extension points
labstack/echo
Extension is primarily through Go interfaces, handler factories, and callbacks. Router replacement has an explicit context-population contract, while middleware factories offer configurable request policies. Binding, rendering, serialization, errors, proxying, and rate limiting each expose narrower integration boundaries. There is no need to alter the core dispatch path for most application-specific behavior described here.
- Config.Router accepts implementations of Add, Remove, Routes, and Route; Route must initialize Context route/path values. NewConcurrentRouter wraps an implementation with read/write locks and returns cloned route metadata for callers.
- Route carries method, path, name, handler, and middleware, and AddRoute returns registration errors rather than panicking like Add. OnAddRoute runs before Router.Add and can reject registration; RouteInfo and Routes provide reversal and metadata lookup.
- MiddlewareFunc transforms HandlerFunc, and MiddlewareConfigurator.ToMiddleware can return configuration errors. Applications can attach middleware through Pre, Use, groups, or routes; middleware development guidance recommends returning request errors through the chain.
- Binder.Bind is replaceable, BindUnmarshaler supports custom parameter conversion, and ValueBinder exposes ValueFunc, ValuesFunc, ErrorFunc, and CustomFunc. Reflection metadata caches explicitly couple the four source tags to tagName and bindMetaFor.
- Config allows custom JSONSerializer, Renderer, and Validator implementations. Context delegates Bind/Validate/Render to configured services, reports absent validator/renderer registrations, and buffers rendered templates before sending output.
- HTTPErrorHandler is an assignable callback; the default recognizes HTTPStatusCoder and status-bearing json.Marshaler implementations. ProblemDetailsHTTPErrorHandler additionally accepts ProblemErrorer, while BindingError.MarshalJSON supplies structured field/message output.
- ProxyBalancer exposes AddTarget, RemoveTarget, and Next(Context); ProxyConfig accepts RetryFilter, ErrorHandler, Transport, ModifyResponse, and rewrite maps. Next can replace the Context request, which proxy execution rereads before upstream forwarding.
- RateLimiterStore supplies Allow, with optional AllowContext for response-aware decisions; IdentifierExtractor and denial/error handlers are configurable. IPExtractor and SchemeExtractor separately let applications adapt request identity and transport interpretation to their proxy topology.