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
Cheers for the excellent work here. Has made interfacing with Grammarly a breeze.
In the README, it indicates that dialect is an optional param to analyze, but I can't seem to get different results when I pass in "american".
Interacting with the web browser, I have no corrections for the word yogurt. But through the API, where it seems the dialect is "british", I get corrections for yogurt to be yoghurt instead.
Any chance I'm doing something wrong with the API? My call looks like this.
Ah, I think I've got it. It looks like the latest release to npm doesn't include the changes made to handle dialect. I got it to work by installing locally instead of through npm.
On Mon, 9 May 2022, 21:48 Jamie Brandon, ***@***.***> wrote:
Ah, I think I've got it. It looks like the latest release to npm doesn't
include the changes made to handle dialect. I got it to work by installing
locally instead of through npm.
—
Reply to this email directly, view it on GitHub
<#33 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAIVNFFOQG3BII66FFP4LP3VJFTZZANCNFSM5VOU56YQ>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
Cheers for the excellent work here. Has made interfacing with Grammarly a breeze.
In the README, it indicates that
dialect
is an optional param toanalyze
, but I can't seem to get different results when I pass in"american"
.Interacting with the web browser, I have no corrections for the word
yogurt
. But through the API, where it seems the dialect is"british"
, I get corrections foryogurt
to beyoghurt
instead.Any chance I'm doing something wrong with the API? My call looks like this.
The text was updated successfully, but these errors were encountered: