fix: align mapResponse and onAfterHandle with unified return types an… #1250
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
…d handler definitions
|
Unfortunately, I don't think this will work As |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Changes
mapResponseto support primitive values (e.g. string, number), aligning its behavior withAfterHandler.onAfterHandleto useAfterHandlerinstead ofOptionalHandlerfor consistency and clarity in handler semantics.Motivation
This change improves the developer experience by making the behavior of response handlers more predictable and flexible. It also eliminates subtle inconsistencies between
mapResponseandonAfterHandle.No breaking changes expected for users following the current type contracts.