-
Notifications
You must be signed in to change notification settings - Fork 64
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Final updates for initial release of the code analyzer
- Added an Ignore Word option to the code analyzer to add the ignored word to an Ignore Spelling directive comment. It's the best I can do for now as it doesn't appear to be possible to add them to the ignored words file or user dictionary. - Updated the documentation for the initial release of the code analyzer. Closes #111.
- Loading branch information
1 parent
46cdb64
commit b2118cc
Showing
39 changed files
with
1,151 additions
and
191 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,45 @@ | ||
<?xml version="1.0" encoding="utf-8"?> | ||
<topic id="12d44ba0-2bef-4fac-a6f9-7990ecf057c2" revisionNumber="1"> | ||
<developerConceptualDocument xmlns="http://ddue.schemas.microsoft.com/authoring/2003/5" xmlns:xlink="http://www.w3.org/1999/xlink"> | ||
<introduction> | ||
<para>The code analyzer in the spell checker extension is used to spell check identifiers in source code. | ||
Only C# is supported right now but future support for Visual Basic and, if possible, F# are planned. Code | ||
analyzer spell checking differs from the string and comments spell checker implemented using the tagger in the | ||
editor. Identifiers are always split up into separate words on capital letters and other separators such as the | ||
underscore. In addition, there are some extra options related to visibility and placement that can control when | ||
spell checking of identifiers occurs. See the <link xlink:href="09cc5bfa-9eba-47e5-ba5f-a36e04f09b0d" /> | ||
configuration category topic for details. Due to the way code analyzers work, there are some limitations. See | ||
the <link xlink:href="a9ff4ce1-0d6b-4376-8d32-02dae64e2075" /> topic for more information.</para> | ||
</introduction> | ||
|
||
<section address="Section1"> | ||
<content> | ||
<para>The code analyzer contains two rules: <codeInline>VSSpell001</codeInline> used to flag misspelled | ||
words in identifiers and offer suggested fixes and <codeInline>VSSpell002</codeInline> used to offer an option | ||
to add the misspelling to an Ignore Spelling directive comment in the source code file. The first rule defaults | ||
to a warning and will show the usual warning underline on the misspellings. The second rule is hidden by default | ||
and only appears on the smart tag when it is opened.</para> | ||
|
||
<para>Place the mouse over the misspelled identifier and click the down arrow on the smart tag to see the | ||
available options. Alternately, you can place the cursor anywhere in the identifier and press <ui>Ctrl+.</ui> or | ||
<ui>Shift+Alt+F10</ui> depending on your version of Visual Studio to show the smart tag options. Note that if an | ||
identifier consists of multiple words and more than one is misspelled, each misspelled part is flagged and | ||
corrected separately.</para> | ||
|
||
<para>Select the "Correct spelling of 'XXX'" option to see the suggested replacements. If the | ||
misspelling represents only a part of the identifier, you will see the rest of the identifier in each suggestion. | ||
Select a suggestion to get a preview of the changes that will occur if it is selected. To add the misspelling to | ||
an Ignore spelling directive comment in the file, select the "Ignore word 'XXX'" option and a preview of the | ||
directive will be displayed. The directive comments is placed at the top of the file below any header comments | ||
and above the first directive, using statement, or namespace declaration. If a directive comment already exists | ||
in that location, the new ignored word will be added to it.</para> | ||
</content> | ||
</section> | ||
|
||
<relatedTopics> | ||
<link xlink:href="3094ee74-88ae-4355-b702-23dcd55b4197" /> | ||
<link xlink:href="a7120f4c-5191-4442-b366-c3e792060569" /> | ||
<link xlink:href="83ff9063-294f-4a18-b765-1510c86ad0d4" /> | ||
</relatedTopics> | ||
</developerConceptualDocument> | ||
</topic> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.