CodeVetter · Repo Unpack · Extension points
gofiber/fiber
Fiber primarily extends through Go interfaces, factories, handlers, and callback lists. Route registration is the main composition surface, while codecs and binders adapt application data formats. Storage, views, and services connect external resources without embedding provider implementations in the core. Some compatibility contracts, especially constraints and generated contexts, require preserving multiple interfaces together.
- Router composition uses Add, Use, Group, Domain, and mounted App values; toFiberHandler is the central adaptation table for supported handler signatures.
- RegisterCustomBinder appends CustomBinder implementations with Name, MIMETypes, and Parse; Body tries registered MIME matches before built-in decoders.
- CustomConstraint registration overrides exact matching names before built-ins; ConstraintAnalyzer preprocesses arguments, while customConstraintWrapper preserves the legacy variadic-string Execute contract.
- Config codec functions replace JSON/XML defaults and enable MessagePack/CBOR; StructValidator.Validate runs for struct destinations unless SkipValidation is enabled.
- New's context pool calls a configured context factory or NewDefaultCtx; CustomCtx extends generated Ctx with Reset, release, abandonment, and internal routing methods.
- Storage adapters implement Get/Set/Delete/Reset variants and Close; session NewStore defaults to memory only when Storage is nil, and SharedState accepts Config.SharedStorage.
- Views implements Load/Render, Service implements Start/String/State/Terminate, and Hooks registers route, group, listen, startup-message, shutdown, fork, and mount callbacks.
- Client factories accept standard, host, or load-balancing fasthttp transports and supply three request-hook stages; limiter.Handler supplies replaceable limiting strategies, while Extractor supports custom callbacks and source-aware chains.