Skip to content

Commit 6e64d8c

Browse files
Merge pull request #39 from heiligerdankgesang/spell-checker-update
Updated Spell Checker documentation
2 parents 48955d6 + 387782e commit 6e64d8c

File tree

1 file changed

+15
-0
lines changed

1 file changed

+15
-0
lines changed

docs/ide/text-spell-checker.md

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -62,6 +62,10 @@ By configuring an EditorConfig file, you can establish the coding standards that
6262

6363
Here are some examples and use-case scenarios of the switches you can configure in an EditorConfig file:
6464

65+
66+
- Apply the spelling options to a specific set of files. **This is a required specification to add, as spelling error options are file-specific.** In this example, the spelling options are applied to all C# files in the solution.
67+
```[*.cs]```
68+
6569
- List the languages for Visual Studio to use. In this example, Visual Studio would only use the "en-us" and "fr-fr" dictionaries when checking for spelling issues.
6670

6771
```spelling_languages = _language_[,_language_]```<br>
@@ -93,6 +97,17 @@ Here are some examples and use-case scenarios of the switches you can configure
9397
```spelling_use_default_exclusion_dictionary = true OR false```<br>
9498
```(Example: = spelling_use_default_exclusion_dictionary = false)```
9599

100+
Here is a complete example:
101+
102+
```
103+
[*.{cs,vb}]
104+
spelling_languages = en-us,fr-fr
105+
spelling_checkable_types = identifiers,comments
106+
spelling_error_severity = error
107+
spelling_exclusion_path = exclusion.dic
108+
spelling_use_default_exclusion_dictionary = false
109+
```
110+
96111
## Special case handling
97112

98113
There are a few special behaviors in how Visual Studio checks code for spelling errors that are different from a traditional spell checker that's designed for written text. Some of these behaviors include:

0 commit comments

Comments
 (0)