Skip to content

fix(handler): infer output type for defineHandler with middleware - #490

Merged
Brooooooklyn merged 3 commits into
voidzero-dev:mainfrom
ashunar0:fix/define-handler-middleware-output
Oct 19, 2026
Merged

Brooooooklyn merged 3 commits into
voidzero-dev:mainfrom
ashunar0:fix/define-handler-middleware-output

Conversation

@ashunar0

Copy link
Copy Markdown
Contributor

Fixes #489.

The middleware overloads of defineHandler returned TypedHandler without type arguments, so __output was unknown and InferProps broke. They now return TypedHandler<{}, Exclude<Awaited<R>, Response>>, like the single-handler overload. No runtime change.

Added cases with one and three middlewares to infer-props.typecheck.ts from #478.

Checked: pnpm check:sdk, define-handler.test.ts

@Brooooooklyn

Copy link
Copy Markdown
Member

@codex review

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 19, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-19T08:27:38.570951Z 5d24c3c New commits
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 61f7401cb0

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread packages/void/src/runtime/handler.ts Outdated
`(c) => R | Response | Promise<R | Response>` binds R from one promise,
so a non-async loader that can return one of two promises, such as
`cond ? loadAuthor() : loadBook()`, was rejected. The middleware forms
accepted it before this branch. Take `(c) => R` and apply Awaited and
Exclude<Response> to the output only, as withValidator does, in every
overload.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@Brooooooklyn

Copy link
Copy Markdown
Member

@codex review

The previous commit typed the handler as `(c) => R`, which broke the
documented `defineHandler<Props>(async (c) => ...)`: R is the loader's
data, not its return value (platform dashboard typecheck failed). Keep
`(c) => R | Response | Promise<R | Response>` for every overload, as on
main, and give each middleware form a second overload that infers from
the handler's return type, for loaders like `cond ? loadA() : loadB()`.
The single-handler overload is unchanged from main.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@Brooooooklyn
Brooooooklyn merged commit 4270ac0 into voidzero-dev:main Oct 19, 2026
18 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

InferProps is unknown for a defineHandler loader with middleware

2 participants