-
Notifications
You must be signed in to change notification settings - Fork 529
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
socketPath option is not passed to the connect function #3486
Comments
Good catch, would you like to send a PR? |
@metcoder95 |
Hmm, bit if we specify socketPath, connect function should receive if, or how it should work? |
Well, in theory it should, we are just not passing it to the We have documented that we support these options to the default connector factory. I'd also expect that they are passed down to the custom factory that its submitted. |
Ok. what is your decision? |
I think it should be fixed. |
I think a PR with the change would help us spot why we did not pass it. If it's that's the case there is likely a test to cover it. |
+1 |
What happens if you specify some file like |
Error, because this is not a socket. |
So, I carefully looked at the code. |
|
We are preparing the cut for new major, so it should be ok to do breaking changes. Feel free to move forward with a PR so we can iterate over it |
It is actually breaking if we add more options? |
I think refers to removing it from Not so sure we should do that, but maybe I'm overseeing something; happy to see the PR to validate |
Bug Description
In
Pool
dispatchersocketPath
option is not passed to theconnect
ifconnect
is a function.Reproducible By
Expected Behavior
Expecting to see
socketPath
in options, passed to theconnect
function.When
connect
is specified as object - it works, but for function you just forget to passsocketPath
.Logs & Screenshots
Environment
Additional context
The text was updated successfully, but these errors were encountered: