fix(1270): throw descriptive error when opts.dispatcher–passed instance methods#5007
Merged
mcollina merged 1 commit intonodejs:mainfrom Apr 9, 2026
Hidden character warning
The head ref may contain hidden characters: "fix/1270/throw-descriptive-error-when-opts.dispatcher\u2013passed-instance-methods"
Conversation
…ce methods Signed-off-by: Roberto Bianchi <roberto.bianchi@spendesk.com>
cf65295 to
fe51bea
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #5007 +/- ##
=======================================
Coverage 92.93% 92.94%
=======================================
Files 110 110
Lines 35735 35739 +4
=======================================
+ Hits 33212 33216 +4
Misses 2523 2523 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Merged
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
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.
This relates to...
Fixes #1270
Rationale
When a user passes
dispatcheras an option toPool.request(),Client.request(), or any other instance method, it is silently ignored, since the request goes through the instance the method was called on, not the provided dispatcher. This is confusing and leads to hard-to-debug behavior, especially for users behind a proxy trying to combinePoolwithProxyAgent.Changes
dispatcherfromoptsvia destructuring before forwarding to instance methodsInvalidArgumentErrorinDispatcherBase.dispatch()ifopts.dispatcheris present, with a message guiding the user to either use top-level functions or call the dispatcher directlyPool.request()rejection,Client.request()rejection, and top-levelrequest()still working withopts.dispatcherFeatures
Bug Fixes
Breaking Changes and Deprecations
Status