boundary.devtools.shell.router — org.boundary-app/boundary-devtools 1.0.0-beta-1

Stateful router management for runtime route/tap modifications. Tracks dynamic routes and taps in atoms, rebuilds the handler via platform's swap-handler!.

add-dynamic-route! clj

(add-dynamic-route! method path handler-fn)

add-tap! clj

(add-tap! handler-name tap-fn)

apply-dynamic-routes clj

(apply-dynamic-routes base-routes)

apply-taps clj

(apply-taps routes)

clear-all-state! clj

(clear-all-state!)

Clear ALL dynamic state including taps. Use for full cleanup.

clear-dynamic-state! clj

(clear-dynamic-state!)

Clear ephemeral dynamic state on reset. Taps are NOT cleared — they persist across resets because (reset) is the documented way to activate them.

has-taps? clj

(has-taps?)

list-dynamic-routes clj

(list-dynamic-routes)

list-taps clj

(list-taps)

rebuild-router! clj

(rebuild-router! base-routes compile-fn swap-fn)

Rebuild the HTTP handler with current dynamic routes and taps applied.

remove-dynamic-route! clj

(remove-dynamic-route! method path)

remove-tap! clj

(remove-tap! handler-name)

wrap-dynamic-dispatch clj

(wrap-dynamic-dispatch base-handler)

Ring middleware that checks dynamic routes via a Reitit router. Supports path parameters (e.g. /api/foo/:id matches /api/foo/123). Matched requests go through the standard HTTP middleware stack (params, cookies, content negotiation/body parsing via Muuntaja) so dynamic handlers behave like normal Boundary routes. Otherwise the request falls through to the base handler.

wrap-taps clj

(wrap-taps base-handler)

Ring middleware that invokes registered tap callbacks. Uses the Reitit router (from handler metadata) to pre-match the request. Matches taps in order of preference:

1. Route :name keyword (exact match — works for all named routes)
2. Handler function string (regex match — fallback for unnamed routes) The tap receives {:request request :match match-data} and its return value replaces the context (allowing request modification).