Next: v26 #2939
Draft
Next: v26 #2939
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the ✨ Finishing touches🧪 Generate unit tests (beta)
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. Comment |
It can now be replaced with `${method} /` syntax
## todo
- [x] rename tests
- [x] fate of `Routable`
- [x] migration
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit
- Breaking Changes
- Removed DependsOnMethod from the public API.
- Routing now uses flat, path-scoped objects with explicit "METHOD /"
keys (e.g., "get /").
- Deprecation is applied per Endpoint; Endpoint now provides nest().
- New Features
- Added an automatic migration rule to convert DependsOnMethod usages to
the new routing syntax.
- Documentation
- README and CHANGELOG updated with new routing examples and deprecation
guidance.
- Examples
- Updated example routing to the new flat object mapping.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
I realized that context is more clear naming for that entity, which is also the same in hono and trpc. It should also reduce the potential confusion with "config options" and `OPTIONS` request method. However, it might not be possible to rename in without breaking changes, since it's present in public interfaces. ## todo - [x] diagram - [x] migration - [x] changelog <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - Breaking Changes - Standardized context naming: replace options with ctx across handlers, middleware, and factory APIs. Renamed addOptions to addContext. This affects handler signatures and how context is accessed. - Documentation - Updated README and examples to reflect ctx-based usage and patterns. - Tooling/Migration - Added automated migration rules to rename options→ctx and addOptions→addContext. - Tests - Updated test suites to align with ctx terminology and behavior. - Chores - CHANGELOG updated to document the API rename and guidance. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
RobinTail
added
breaking
RobinTail
commented
Oct 4, 2025
RobinTail
commented
Oct 4, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
DependsOnMethod#2938optionstoctx#2934