Files
zeekayandHanzo Dev bbabddeaa8 examples: declare typed ops, because that is what the examples are teaching
Ten of eleven examples declared their surface with untyped handlers. An untyped
route registers no op, so every one of them modelled the single pattern that
leaves an endpoint out of the OpenAPI document, out of the MCP tool list, out of
the CLI and out of the call plane — while the README two files away calls that
registry the one source of truth. The examples are where the default is learned,
and they were teaching the wrong one.

hello, subsystem-mount, migrate-from-chi, migrate-from-beego, plugin/billing,
plugin/host and internal/testplugin now declare typed ops. The migrate-from-*
examples show the port as the two steps it is: mechanical first (same handler
shape, one edit, and invisible to every projection), typed second, because
stopping after the first leaves exactly the surface you were migrating away
from.

sse-streaming and websocket stay untyped and now say why in the file header: a
typed op is one decode, one call, one serialize, and a stream has no single
value to return while an upgrade has no response body at all. That is the whole
list of reasons — a stream, an upgrade, a proxied byte range, a non-JSON body.

express-in-zip registered two routes on app.Fiber(), BELOW zip entirely: no
*zip.Ctx, no error handler, no middleware, no Authorizer, and no projection —
served by the app but not governed by it, which is a security seam and not a
shortcut. Both move onto the zip router. /runtime/:lang becomes a typed op, so
"run this source in this language" is now in the document and is a tool an agent
can call; the legacy JS wildcard stays a wildcard and says what that costs.

testplugin's catch-all stays untyped for the reason it exists: it answers paths
that do not exist, so a host mounting it at two prefixes can tell its own 404
from the plugin's. A wildcard is deliberately not one named endpoint with one
schema.

Every example was run and probed, not just built: 30 assertions across all
eleven, including the openapi/mcp routes the typed ops now light up.

Co-authored-by: Hanzo Dev <[email protected]>
2026-07-28 16:38:21 -07:00

64 lines
1.9 KiB
Go

// migrate-from-beego example — beego → zip migration via http.Handler
// adapter. beego.BeeApp exposes Handlers as an http.Handler-compatible
// surface; the same AdaptNetHTTP adapter that fronted chi handles beego too.
//
// In a real port:
//
// import (
// "github.com/beego/beego/v2/server/web"
// "github.com/zap-proto/zip"
// )
//
// beeApp := web.NewHttpSever() // your existing beego app
// zipApp := zip.New(zip.Config{AppName: "iam"})
// zipApp.Group("/legacy/iam").All("/*", zip.AdaptNetHTTP(beeApp.Handlers))
//
// This example uses a stand-in http.Handler so the file builds without
// pulling beego — same adapter pattern in either case.
//
// The adapted subtree is a wildcard route and registers no operation, so nothing
// behind /legacy/iam is in the OpenAPI document, the MCP tool list, the CLI or
// the call plane. New work goes in as a TYPED op, and a native route added later
// wins by specificity — so the legacy tree shrinks one op at a time.
package main
import (
"context"
"log"
"net/http"
"github.com/zap-proto/zip"
)
type beegoStub struct{}
func (beegoStub) ServeHTTP(w http.ResponseWriter, _ *http.Request) {
w.Header().Set("Content-Type", "application/json")
_, _ = w.Write([]byte(`{"legacy_beego":true}`))
}
// Health is what the probe answers.
type Health struct {
Status string `json:"status"`
}
// Nothing is an operation that takes no input.
type Nothing struct{}
// Healthz reports whether IAM is up.
func healthz(context.Context, *Nothing) (*Health, error) {
return &Health{Status: "ok"}, nil
}
func main() {
app := zip.New(zip.Config{AppName: "migrate-from-beego"})
// New native zip routes, typed:
zip.Get(app, "/v1/iam/healthz", healthz)
// Legacy beego app under /legacy/iam — one adapted wildcard route:
app.Group("/legacy/iam").All("/*", zip.AdaptNetHTTP(beegoStub{}))
log.Fatal(app.Listen("http://:8080"))
}