You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Unfortunately the project I've been working on most likely wont use this anymore but I figure you might want this source code anyway.
It may seem that there are a lot changes here. Mostly I just made the quotation marks consistent throughout the JS file.
Something I've found wierd about this API is that you require a different access token for the custom speech and regular speech. This might become a consideration going forward cause currently you'd be instantiating two instances of watson-js in order to use functionality. It might be good to save the access token per scope.
As I haven't used the Speech API since 2012, I'd imagine that things have changed a bit. I'll review the code and see if it makes sense to make the modifications you recommended.
I may also ping the good folks at AT&T to see if they have someone willing to be an active maintainer, since not using the API actively has left me with little context for this update.
Thanks for your work on making the API and its Node wrapper better, either way!
Unfortunately the project I've been working on most likely wont use this anymore but I figure you might want this source code anyway.
It may seem that there are a lot changes here. Mostly I just made the quotation marks consistent throughout the JS file.
Something I've found wierd about this API is that you require a different access token for the custom speech and regular speech. This might become a consideration going forward cause currently you'd be instantiating two instances of watson-js in order to use functionality. It might be good to save the access token per scope.
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
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.
I've started implementing the custom speech api.
Unfortunately the project I've been working on most likely wont use this anymore but I figure you might want this source code anyway.
It may seem that there are a lot changes here. Mostly I just made the quotation marks consistent throughout the JS file.
Something I've found wierd about this API is that you require a different access token for the custom speech and regular speech. This might become a consideration going forward cause currently you'd be instantiating two instances of watson-js in order to use functionality. It might be good to save the access token per scope.