1. The users of this style guide will probably expect that all of the rules that it prescribes will be enforced by eslint. However, this is not the case - there is a secret, non-documented segmentation where some rules are enforced and others are not, because they would be "too noisy on a legacy codebase". An example of a problematic rule like this is covered in issue #2020. I propose that all of

Rule Names should be written with their most general part first and their most specific part last is not usual because ex. infoLabel, cancelButton are very common names in iOS which is also encouraged in the next rule Include a hint about type in a name if it would otherwise be ambiguous examples.

https://github.com/airbnb/swift#general-part-first
https://github.com/airbnb/swift#hi

PEP8 describes "Capitals_With_Underscores" as ugly (https://www.python.org/dev/peps/pep-0008/#descriptive-naming-styles) and never recommends that it be used anywhere, but, as far as I can tell, pep8-naming doesn't show a warning for variable names that follow it.

Add JavaScript as a topic

We are currently missing the whole topic for JavaScript naming conventions.

Acceptance Criteria:

• Add at least 5 different topics for JavaScript naming conventions.
• Add a home page for JavaScript naming conventions and list all the covered section.
• Make sure nothing is copied from internet. All the examples and descriptions should be origin

In the readme.me file (https://github.com/dsheiko/jscodesniffer/blob/master/README.md), under "Declaring coding style", there is an example file.

Well, there is a colon missing in the "ParametersSpacing" option, in the 4th line of the "lastParam":

        "lastParam": {
          "for": [ "Identifier" ],
          "allowParamPrecedingWhitespaces": 1
          "allowParamTrailingWhitespaces":

Relevant for the manual

• Nullable reference types (default settings, how to use)
• Default implementations (rework the extension methods section/advice)
• Target-typed new expressions
• Switch expressions (lightweight pattern-matching)
• Note on Ranges/indices