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
"Axiallary" isn't a word. #1626
Comments
you can try and find what local dictionary that might have it by running |
We are using cspell via the GitHub Action, and when I try running |
could try running it after cloning the action repo https://github.com/streetsidesoftware/cspell-action/blob/main/action/package.json |
If you have node / npm installed on your system, then the following should work:
If you are only seeing the issue in certain types of files, like
|
Is it also possible to copy your |
I wonder how "No matches found" wound up in the middle of the output and whether it's by design that cspell exited with error code 1?
Here is our {
"version": "0.1",
"language": "en-US",
"import": ["@cspell/dict-medicalterms/cspell-ext.json"],
"dictionaryDefinitions": [
{
"name": "custom",
"path": "./.dictionary.txt"
}
],
"dictionaries": [
"bash",
"csharp",
"custom",
"dotnet",
"filetypes",
"fonts",
"medicalterms",
"powershell",
"python",
"softwareTerms"
],
"ignorePaths": [
".jscpd.json",
".vs",
".vscode",
"**/*.lock*",
"**/*.user",
"bin/**",
"obj/**",
"AppPackages/**",
"BundleArtifacts/**",
"super-linter.log",
"node_modules",
"package.json",
"Pipfile",
".virtualenv"
],
"flagWords": [
"bicep",
"tricep"
]
} |
It exits with error code 1 when No Matches are found. That is by design. Strange that it ended up in the middle. I think it is because the output goes to two different streams: |
There doesn't seem to be an issue with your configuration. A couple of questions:
Is it possible to give some sample code or document with the issue? |
Ah yes, the output going to different streams make sense. I wonder if it would make sense to flush
Here is a minimal reproduction that I made in a file named Axiallary.cs: namespace axiallary
{
public class Axiallary
{
public static string axiallary = "axiallary";
public static string dalek = "dalek";
}
} Here is the output of
|
It is the To turn it off: "languageSettings": [
{
"languageId": "*", // "*" for all languages or "csharp,python" for just C# and Python files.
"allowCompoundWords": false
}
], |
Glorious; yep, that was it. That helped me find a lot of other misspelled words as well, but as you might expect they are mixed in with a lot of false positives too, so I like that this setting defaults to |
Ideally |
Note: Please see Custom Dictionaries - CSpell. In your dictionary try using the compound syntax:
will allow any combination of |
Thanks for the pointer. I may be missing something, but I don't understand why |
The default setting for With C#, it defaults to I hope to remove all cases where |
Ohhh, that makes a lot of sense given Microsoft's embrace of ALLCAPSWITHOUTUNDERSCORES, for example. In that case, should |
Since the
|
You make a good point. It doesn't seem reasonable to open a new can of worms by trying to guess. Thank you! |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
"Axillary" is a medical term meaning "relating to the armpit," which appears correctly spelled in the medical terms dictionary. I can't figure out why "axiallary" is a false negative though; I have yet to find it in any cspell dictionary. The obvious workaround in the meantime is to list it as a flag word. I double checked that the term wasn't in an ignored file or listed in a custom dictionary.
The text was updated successfully, but these errors were encountered: