navigation

UnnestedFunctionNames (FL0080)

Introduced in 0.21.8

Cause

Unnested function naming does not match the specified config.

Rationale

Consistency aides readability.

How To Fix

Update the unnested function names to be consistent with the rules you have specified.

Rule Settings

{
    "UnnestedFunctionNames": {
        "enabled": false,
        "config": {
            "naming": "PascalCase",
            "underscores": "None"
        }
    }
}