azure / azure-functions-dotnet-extensions

Analysis scope, overview of main, test, generated, deployment, build, and other code.

Source Code Analysis Scope

Files includes and excluded from analyses

csproj

txt

editorconfig

8 extensions are included in analyses: cs, yaml, csproj, json, gitignore, md, txt, editorconfig
3 criteria are used to exclude files from analysis:

exclude files with path like ".*/[.][a-zA-Z0-9_]+.*" (Hidden files and folders) (4 files).
exclude files with path like ".*/git[-]history[.]txt" (Git history) (1 file).
exclude files with path like ".*/git[-][a-zA-Z0-9_]+[.]txt" (Git data exports for sokrates analyses) (0 files).

The source code folder contains 51 files:

34 files are included in analyses.
17 files are excluded from analyses:

Explore all files....

Overview of Analyzed Files

Basic stats on analyzed files

Intro

For analysis purposes we separate files in scope into several categories: main, test, generated, deployment and build, and other.

The main category contains all manually created source code files that are being used in the production.
Files in the main category are used as input for other analyses: logical decomposition, concerns, duplication, file size, unit size, and conditional complexity.
Test source code files are used only for testing of the product. These files are normally not deployed to production.
Build and deployment source code files are used to configure or support build and deployment process.
Generated source code files are automatically generated files that have not been manually changed after generation.
While a source code folder may contain a number of files, we are primarily interested in the source code files that are being written and maintained by developers.
Files containing binaries, documentation, or third-party libraries, for instance, are excluded from analysis. The exception are third-party libraries that have been changed by developers.

10 files

3 files

1 file

20 files

Main Code

All manually created or maintained source code that defines logic of the product that is run in a production environment.

Explore: circles | sunburst

The following criteria are used to filter files:

files with paths like ".*".

10 files match defined criteria (158 LOC, 100.0% vs. main code). All matches are in *.cs files.

Test Code

Used only for testing of the product. Normally not deployed in a production environment.

csproj

Explore: circles | sunburst

The following criteria are used to filter files:

files with paths like ".*/[Tt]est/.*".
files with paths like ".*[.][Tt]ests/.*".
files with paths like ".*[.][Tt]ests[.].*".

3 files match defined criteria (59 LOC, 37.3% vs. main code):

2 *.cs files (42 LOC)
1 *.csproj files (17 LOC)

" *.cs" is biggest, containing 71.19% of LOC.
" *.csproj" is smallest, containing 28.81% of LOC.

Build and Deployment Code

Source code used to configure or support build and deployment process.

csproj

Explore: circles | sunburst

The following criteria are used to filter files:

files with paths like ".*[.]csproj".
files with paths like ".*[.]git[a-z]+".
files with paths like ".*/[.]gitignore".

1 file matches defined criteria (28 LOC, 17.7% vs. main code). All matches are in *.csproj files.

Other Code

csproj

Explore: circles | sunburst

The following criteria are used to filter files:

files with paths like ".*[.]md".
files with paths like ".*/README[.][a-z0-9]+".
files with paths like ".*/[Ss]amples/.*".
files with paths like ".*/[.]gitignore".
files with paths like ".*[.]json".
files with paths like ".*[.]editorconfig".
files with paths like ".*[.]txt".

20 files match defined criteria (290 LOC, 183.5% vs. main code):

12 *.cs files (195 LOC)
2 *.csproj files (54 LOC)
2 *.md files (29 LOC)
4 *.json files (12 LOC)

" *.cs" is biggest, containing 67.24% of LOC.
" *.json" is smallest, containing 4.14% of LOC.