Closed solyarisoftware closed 3 years ago
If it’s just an oversight, could you make a npm publish? Thanks!
Done
A collateral request/suggestion: when you release a "main" release (e.g. v0.3.30) I'd suggest to publish a small documentation (just few lines) to track updates, as new features. I mean just writing down really few lines in a CHANGELOG.md (I do this just as a rough example) to introduce ne functionalities.
We will consider that, thank you
BTW, reading code I guess new functions are recognizer methods setMaxAlternatives and setWords, but why you stated that "API changed unfortunately" ? It seems to me that the interface isn't broken.
It doesn't print words anymore if you don't mention setWords(True) like it was before.
Thanks Nicolay.
Maybe it could be a good idea to add a npm publish
everytime you git commit? :-)
BTW, beside the suggested CHANGELOG.md, I'd propose to insert in this README.md a "install" section" to remind people they have to do npm install vosk
in the project directory (here an example of the install section) ;-)
About last point, maybe you would avoided API change just reversing the logic, setting setWords(True) by default. But evidently there are good reasons why setWords(False) as default is better. Maybe to save performances/log data in long transcripts? Never mind.
Thanks
Hi Nicolay
you didn't published last version of node package:
If it’s just an oversight, could you make a
npm publish
? Thanks!A collateral request/suggestion: when you release a "main" release (e.g. v0.3.30) I'd suggest to publish a small documentation (just few lines) to track updates, as new features. I mean just writing down really few lines in a CHANGELOG.md (I do this just as a rough example) to introduce ne functionalities.
BTW, reading code I guess new functions are recognizer methods
setMaxAlternatives
andsetWords
, but why you stated that "API changed unfortunately" ? It seems to me that the interface isn't broken.Thanks for your great work and your continuous support to people! Giorgio