Overview - Router

router

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
7325
97f09f4d fix(start-server-core): guard against undefined ctx.response in HEAD fallback If a fallback GET/ANY handler exits without returning a Response, ctx.response is undefined. Without the guard, handleRedirectResponse passes undefined through and new Response(null, undefined) silently synthesizes a 200 OK, masking the handler bug. Calling throwRouteHandlerError() surfaces the mistake with the same error used everywhere else in the file. Also removes the unsafe cast -- TypeScript narrows the type correctly after the never-returning guard.
by Zelys
Canceled
7325
97f09f4d fix(start-server-core): guard against undefined ctx.response in HEAD fallback If a fallback GET/ANY handler exits without returning a Response, ctx.response is undefined. Without the guard, handleRedirectResponse passes undefined through and new Response(null, undefined) silently synthesizes a 200 OK, masking the handler bug. Calling throwRouteHandlerError() surfaces the mistake with the same error used everywhere else in the file. Also removes the unsafe cast -- TypeScript narrows the type correctly after the never-returning guard.
by Zelys
Failed
7325
Environment issue→
0d3549e0 ci: apply automated fixes
by autofix-ci...
Canceled
7325
d9d24f02 refactor(start-server-core): use new Response(null, resolved) per reviewer suggestion Adopts the tighter form suggested by @schiller-manuel: passing the resolved Response directly as the ResponseInit arg copies status, statusText, and headers in one shot instead of spreading them manually.
by Zelys
Succeeded
7325
0f65fbf8 fix(start-server-core): fall back to GET handler for HEAD requests When no explicit HEAD or ANY handler is defined, HEAD requests now use the GET handler and return its headers with no body, per RFC 9110 §9.3.2.
by Zelys-DFKH