An early attempt at updating documentation

Author: jedidja

StyleCop.Analyzers/StyleCop.Analyzers/NamingRules/SA1300ElementMustBeginWithUpperCaseLetter.cs

@@ -30,6 +30,9 @@ namespace StyleCop.Analyzers.NamingRules
     /// class. A <c>NativeMethods</c> class is any class which contains a name ending in <c>NativeMethods</c>, and is
     /// intended as a placeholder for Win32 or COM wrappers. StyleCop will ignore this violation if the item is placed
     /// within a <c>NativeMethods</c> class.</para>
+    ///
+    /// <para>For namespace components that begin with a small letter, due to branding issues or other reasons, add the
+    /// term to the <c>allowedNamespaceComponentTerms</c> list.</para>
     /// </remarks>
     [DiagnosticAnalyzer(LanguageNames.CSharp)]
     internal class SA1300ElementMustBeginWithUpperCaseLetter : DiagnosticAnalyzer

StyleCop.Analyzers/StyleCop.Analyzers/Settings/stylecop.schema.json

@@ -128,6 +128,15 @@
                 "uniqueItems": true
               }
             },
+            "allowedNamespaceComponentTerms": {
+              "type": "array",
+              "description": "Allowed namesapce component terms, such as ones beginning with a lowercase letter.",
+              "default": [],
+              "items": {
+                "type": "string",
+                "uniqueItems": true
+              }
+            },
             "includeInferredTupleElementNames": {
               "type": "boolean",
               "description": "Specifies whether inferred tuple element names will be analyzed as well.",

documentation/Configuration.md

@@ -314,6 +314,30 @@ The following example shows a settings file which allows the common prefixes as
 }
 ```
 
+### Namespace Components
+
+The following property is used to configure allowable namespace component terms (e.g. ones that start with a lowercase letter).
+
+| Property | Default Value | Minimum Version | Summary |
+| --- | --- | --- | --- |
+| `allowedNamespaceComponentTerms` | `[ ]` | 1.2.0 | Specifies namespace component terms that are allowed to be used. See the example below for more information. |
+
+The following example shows a settings file which allows the namespace such as `eBay` or `Apple.iPod`.
+
+```json
+{
+  "settings": {
+    "namingRules": {
+      "allowedNamespaceComponentTerms": [
+        "eBay",
+        "iPod"
+      ]
+    }
+  }
+}
+```
+
+
 ### Tuple element names
 
 The following properties are used to configure the behavior of the tuple element name analyzers.

documentation/SA1300.md

@@ -42,10 +42,14 @@ begin with a lower-case letter, place the field or variable within a special `Na
 class is any class which contains a name ending in `NativeMethods`, and is intended as a placeholder for Win32 or COM
 wrappers. StyleCop will ignore this violation if the item is placed within a `NativeMethods` class.
 
+For namespace components that begin with a small letter, due to branding issues or other reasons, add the appropriate
+term to the `allowedNamespaceComponentTerms` list.
+
 ## How to fix violations
 
-To fix a violation of this rule, change the name of the element so that it begins with an upper-case letter, or place
-the item within a `NativeMethods` class if appropriate.
+To fix a violation of this rule, change the name of the element so that it begins with an upper-case letter, place
+the item within a `NativeMethods` class if appropriate, or add it to the `allowedNamespaceComponentTerms` list if
+it is a namespace component.
 
 ## How to suppress violations