fix: stop ignoring serviceUrl for Websocket methods #1060
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.
The Websocket methods
recognizeUsingWebsocket
(STT) andsynthesizeUsingWebsocket
(TTS) were not using theserviceUrl
parameter defined by the core. They were only looking forurl
.The
serviceUrl
parameter is the correct one,url
is deprecated (but still supported). In the core,serviceUrl
andurl
are both mapped tobaseOptions.serviceUrl
, so we only need to look at that single parameter and both are supported. This is a compatible change. I updated the test to make sure the user can provide bothserviceUrl
andurl
.Resolves #1059