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
{{ message }}
This repository has been archived by the owner on May 7, 2024. It is now read-only.
In markdown snippet, Grammarly complains about name of programming variable, function, class, etc.
Whether to check if variable name is correct should be done by configuring linter, like eslint-plugin-markdown.
I think it'd be better to ignore, by default, various cases widely used in programming, like kebab-case, CAPITAL_SNAKE_CASE, camelCase, etc.
Or the extension may disassemble those words. For example, parse the word 'changedFiles' and give it to Grammarly by 'changed files'. So if there's a type in the variable, like 'chagedFiles'(n is missing), Grammarly will complain.
Providing a config option to disable Grammarly for fenced code snippet(```) is also good, if comments in the snippet are OK to be ignored.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In markdown snippet, Grammarly complains about name of programming variable, function, class, etc.
Whether to check if variable name is correct should be done by configuring linter, like eslint-plugin-markdown.
I think it'd be better to ignore, by default, various cases widely used in programming, like kebab-case, CAPITAL_SNAKE_CASE, camelCase, etc.
Or the extension may disassemble those words. For example, parse the word 'changedFiles' and give it to Grammarly by 'changed files'. So if there's a type in the variable, like 'chagedFiles'(n is missing), Grammarly will complain.
Providing a config option to disable Grammarly for fenced code snippet(```) is also good, if comments in the snippet are OK to be ignored.
The text was updated successfully, but these errors were encountered: