Next steps; Use Grammarly official API
znck opened this issue ยท 17 comments
I am working on Grammarly for developers, our first project was to build a web embedable SDK for editors and we shipped it today. Next, we'll work to support nodejs environment like vscode extension.
Over coming months, this vscode extension would get full Grammarly support; stay tuned!
Is the API usable with the free version?
Yes
I am interested in helping. Please let me know how I can participate.
I am primarily interested in using Grammarly under emacs.
Is this project still active or no longer maintained?
Obviously dead, the extension doesn't even work anymore.
The extension works fine for me.
I am on the team building official Grammarly SDK and this extension will get major updates when official SDK for nodejs is available, likely to happen in second half of 2022. Until then this project is on halt and will receive only fixes for critical issues.
It seems that today the plugin stopped working. Here is the log:
(node:38576) UnhandledPromiseRejectionWarning: Error: Socket connection failed: NOT_AUTHORIZED
at GrammarlyClient._connect (/home/yury/.vscode/extensions/znck.grammarly-0.14.0/dist/server/index.js:38903:19)
at GrammarlyClient._queueOrSend (/home/yury/.vscode/extensions/znck.grammarly-0.14.0/dist/server/index.js:38978:18)
at /home/yury/.vscode/extensions/znck.grammarly-0.14.0/dist/server/index.js:38876:18
at new Promise (<anonymous>)
at GrammarlyClient.send (/home/yury/.vscode/extensions/znck.grammarly-0.14.0/dist/server/index.js:38874:16)
at GrammarlyClient.start (/home/yury/.vscode/extensions/znck.grammarly-0.14.0/dist/server/index.js:39160:21)
at GrammarlyClient.onConnection [as _onConnection] (/home/yury/.vscode/extensions/znck.grammarly-0.14.0/dist/server/index.js:39809:32)
Should I report this as a new issue?
ok
If you need a tester I'm here to help. I used to write code tutorials with WordPress but I want to move to blogs built by SSGs that are based on md with mdx - but I need Grammarly and other tools like readability and SEO checkers. Showing snippets and extending the content with custom "blocks" is a bit cumbersome when you are not in an editor like VS Code. In some context it's not even a choice, like if you were building a docs site with mkdocs, you probably still want to grammar check your writing. So I'm eagerly waiting for the official API to roll out so I can finally focus on writing only in markdown, and only in VS Code.
I am a volunteer too if you need a tester, I even think I can get my employer to chip in and pay some money to speed up the development
Also willing to help, test, etc. We have a whole team of engineers that do technical reporting via markdown and this integration would save us so much effort.
I do not know how long it would take to make an official API and to update this project to use it. I also believe in open source and would like to see an open-source alternative where users can control features, etc. As somebody who is very interested in a usable version of it right now, I am ready to put my money where my mouth is and will be sponsoring an effort to fix, improve and support this project. Here is more information: https://gist.github.com/vzaliva/b3f11805e54647feca20dfb88b439075