Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dialect doesn't appear to be an optional param #33

Open
jambran opened this issue May 9, 2022 · 2 comments
Open

Dialect doesn't appear to be an optional param #33

jambran opened this issue May 9, 2022 · 2 comments

Comments

@jambran
Copy link

jambran commented May 9, 2022

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.

results = await premium.analyse(sentence, 5000, "american");
@jambran
Copy link
Author

jambran commented May 9, 2022

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.

@stewartmcgown
Copy link
Owner

stewartmcgown commented May 10, 2022 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants