Skip to content
This repository has been archived by the owner on May 7, 2024. It is now read-only.

Investigate: Use internal API instead of Developer API #396

Open
linusheck opened this issue Oct 19, 2023 · 1 comment
Open

Investigate: Use internal API instead of Developer API #396

linusheck opened this issue Oct 19, 2023 · 1 comment

Comments

@linusheck
Copy link

Grammarly is shutting down its developer APIs. We should investigate if it is possible to tap into the internal APIs instead.

I saw that most language servers are using this OAuth Client ID:

client_BaDkMgx4X19X9UxxYRCXZo

Maybe it is possible to somehow grep the internal client IDs (are they using OAuth?) and replace it.
@linusheck
Copy link
Author

Apparently, this version of the plugin already uses the internal APIs. It is probably possible to switch back.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@linusheck