✨ Export MiddlewareSlot utility type from context-api

[taras]

Motivation

The Around<A> mapped type defines how each API member maps to its middleware signature, but there is no public type to extract the middleware type for a single slot. Writing generic middleware helpers today requires duplicating the conditional-type logic from Around<A>, which is fragile — if the mapping changes, hand-rolled extractions silently drift.

Approach

Export MiddlewareSlot<A, K> — a type alias defined as Around<A>[K]. This gives the slot type a stable public name at zero runtime cost, so typed helpers can reference it directly instead of reconstructing the mapping by hand.

Summary by CodeRabbit

• New Features
  • Added a developer-facing type convenience to simplify middleware slot configuration for individual API operations.
• Chores
  • Bumped package version to 0.6.0.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: c6414a7a-6d41-4a46-aaa6-7d9e34613a25

📥 Commits

Reviewing files that changed from the base of the PR and between d76f26f and 3eb628b.

📒 Files selected for processing (1)

• context-api/package.json

---

📝 Walkthrough

Walkthrough

Added a new exported type alias MiddlewareSlot<A, K extends keyof A> to context-api/mod.ts, defined as Around<A>[K]. No runtime behavior or control flow changes.

Changes

Cohort / File(s)	Summary
Type Alias Addition context-api/mod.ts	Added exported type alias MiddlewareSlot<A, K extends keyof A> = Around<A>[K] to simplify typing middleware for a single API operation key.
Package Version Bump context-api/package.json	Updated package version from 0.5.3 to 0.6.0.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• ✨ Support any handler type in context-api #196 — Adds or modifies Around<A>-related types which MiddlewareSlot depends on.
• ♻️ Refactor context-api to use @effectionx/middleware with min/max priority #189 — Refactors middleware type exports / around signature related to the new alias.

Suggested reviewers

• cowboyd

🚥 Pre-merge checks | ✅ 4

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly describes the main change: exporting a new MiddlewareSlot utility type from context-api, which matches the primary code change.
Description check	✅ Passed	The description follows the required template with both Motivation and Approach sections fully completed, clearly explaining the problem and solution.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Policy Compliance	✅ Passed	Pull request fully complies with all applicable policies: no-agent-marketing, package-json-metadata, and version-bump.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/export-middleware-slot-type

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/@effectionx/context-api@208

commit: 3eb628b

[cowboyd]

Seems good. If we're going to have it, then we should use it in the definition of Around<A> itself. What about SlotMiddleware, or even PropertyMiddleware which feels more inline with how JS names things.