BREAKING CHANGE: move sock options into an object #2593
Merged
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.
For Bugs and Features; did you add new tests?
Yes
Motivation / Use-Case
All the breaking changes are listed below
I created a new option called
clientOptions
that has propertieshost
,path
, andport
. Is this a good name, or would we prefer something likewsOptions
? I think we should not use "sock" anymoreI also added an API method to server to easily get the path we want:
server.getClientOptionsPath()
. We can also consider if there is a better name for this (maybeserver.getClientWsPath()
?)Breaking Changes
sockPath
,sockHost
,sockPort
options removed in favor ofclientOptions
objectserver.sockPath
and switch it with an API methodserver.getClientOptionsPath()
host
,path
, andport
(rather thansockHost
,sockPath
,sockPort
)Additional Info
We also need to update the docs for this