microsoft / chart-parts
Source Code Overview

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

Source Code Analysis Scope
Files includes and excluded from analyses
npmignore
snap
plist
gitattributes
properties
watchmanconfig
editorconfig
pro
txt
mjs
eslintignore
prettierignore
  • 29 extensions are included in analyses: ts, json, tsx, md, js, npmignore, yml, cjs, snap, plist, xml, gitignore, m, gradle, gitattributes, java, properties, watchmanconfig, xib, bat, bzl, editorconfig, svg, h, pro, txt, mjs, eslintignore, prettierignore
  • 10 criteria are used to exclude files from analysis:
    • exclude files with path like ".*/[.][a-zA-Z0-9_]+.*" (Hidden files and folders) (51 files).
    • exclude files with path like ".*/bin/.*" (Binaries for distribution) (0 files).
    • exclude files with path like ".*/proguard[-]rules[.]pro" (ProGuard) (1 file).
    • exclude files with path like ".*/gradle/wrapper/.*" (Gradle) (1 file).
    • exclude files with path like ".*/Chart\.js" (Chart.js) (1 file).
    • exclude files with path like ".*\.d\.ts" (Typescript definition files) (1 file).
    • 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).
    • exclude files with path like ".*/sokrates_conventions[.]json" (Sokrates scoping conventions) (1 file).
    • exclude files with path like ".*[.]txt" (Text files) (0 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.

main16648 LOC (27%) 399 files
test2638 LOC (4%) 40 files
generated0 LOC (0%) 0 files
build and deployment193 LOC (<1%) 4 files
other42047 LOC (68%) 105 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 ".*".
  • 399 files match defined criteria (16,648 lines of code, 100.0% vs. main code):
    • 277 *.ts files (9,329 lines of code)
    • 97 *.tsx files (6,544 lines of code)
    • 18 *.js files (625 lines of code)
    • 3 *.m files (82 lines of code)
    • 2 *.java files (46 lines of code)
    • 1 *.bzl files (17 lines of code)
    • 1 *.h files (5 lines of code)
  • " *.ts" is biggest, containing 56.04% of code.
  • " *.h" is smallest, containing 0.03% of code.


*.ts9329 LOC (56%) 277 files
*.tsx6544 LOC (39%) 97 files
*.js625 LOC (3%) 18 files
*.m82 LOC (<1%) 3 files
*.java46 LOC (<1%) 2 files
*.bzl17 LOC (<1%) 1 files
*.h5 LOC (<1%) 1 files
Test Code
Used only for testing of the product. Normally not deployed in a production environment.
snap
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*__tests__.*".
    • files with paths like ".*[.]spec[.]ts".
    • files with paths like ".*[.]snap".
    • files with any line of content like ".*/simpletest/.*".
  • 40 files match defined criteria (2,638 lines of code, 15.8% vs. main code):
    • 33 *.ts files (1,567 lines of code)
    • 6 *.snap files (1,065 lines of code)
    • 1 *.js files (6 lines of code)
  • " *.ts" is biggest, containing 59.4% of code.
  • " *.js" is smallest, containing 0.23% of code.


*.ts1567 LOC (59%) 33 files
*.snap1065 LOC (40%) 6 files
*.js6 LOC (<1%) 1 files
Build and Deployment Code
Source code used to configure or support build and deployment process.
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*[.]git[a-z]+".
    • files with paths like ".*/[.]gitattributes".
    • files with paths like ".*/[.]gitignore".
    • files with paths like ".*/package[.]json".
    • files with paths like ".*[.]gradle".
    • files with paths like ".*/AndroidManifest[.]xml".
    • files with paths like ".*[.]bat".
  • 4 files match defined criteria (193 lines of code, 1.2% vs. main code):
    • 3 *.gradle files (117 lines of code)
    • 1 *.bat files (76 lines of code)
  • " *.gradle" is biggest, containing 60.62% of code.
  • " *.bat" is smallest, containing 39.38% of code.


*.gradle117 LOC (60%) 3 files
*.bat76 LOC (39%) 1 files
Other Code
plist
properties
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*[.]json".
    • files with paths like ".*[.]editorconfig".
    • files with paths like ".*/[.]eslintignore".
    • files with paths like ".*[.]md".
    • files with paths like ".*/[.]gitignore".
    • files with paths like ".*/[.]prettierignore".
    • files with paths like ".*/README[.][a-z0-9]+".
    • files with paths like ".*/[.]npmignore".
    • files with paths like ".*[.]properties".
    • files with paths like ".*[.]plist".
    • files with paths like ".*[.]xib".
    • files with paths like ".*/[Dd]ocumentation/.*".
    • files with paths like ".*[.]txt".
    • files with paths like ".*[.](xml|xsd|robot|sql|pgsql|dashboard|profile|ipynb|raml|avsc|al)".
  • 105 files match defined criteria (42,047 lines of code, 252.6% vs. main code):
    • 65 *.json files (40,820 lines of code)
    • 30 *.md files (970 lines of code)
    • 4 *.plist files (162 lines of code)
    • 1 *.xib files (42 lines of code)
    • 4 *.xml files (37 lines of code)
    • 1 *.properties files (16 lines of code)
  • " *.json" is biggest, containing 97.08% of code.
  • " *.properties" is smallest, containing 0.04% of code.


*.json40820 LOC (97%) 65 files
*.md970 LOC (2%) 30 files
*.plist162 LOC (<1%) 4 files
*.xib42 LOC (<1%) 1 files
*.xml37 LOC (<1%) 4 files
*.properties16 LOC (<1%) 1 files
Analyzers
Info about analyzers used for source code examinations.
  • *.ts files are analyzed with TypeScriptAnalyzer:
    • All basic standard analyses supported (source code overview, duplication, file size, concerns, findings, metrics, controls)
    • Advanced code cleaning (empty lines and comments removed for LOC calculations, additional cleaning for duplication calculations)
    • Unit size analysis
    • Conditional complexity analysis
    • No dependency analysis
  • *.tsx files are analyzed with TypeScriptAnalyzer:
    • All basic standard analyses supported (source code overview, duplication, file size, concerns, findings, metrics, controls)
    • Advanced code cleaning (empty lines and comments removed for LOC calculations, additional cleaning for duplication calculations)
    • Unit size analysis
    • Conditional complexity analysis
    • No dependency analysis
  • *.js files are analyzed with JavaScriptAnalyzer:
    • All basic standard analyses supported (source code overview, duplication, file size, concerns, findings, metrics, controls)
    • Advanced code cleaning (empty lines and comments removed for LOC calculations, additional cleaning for duplication calculations)
    • Unit size analysis
    • Conditional complexity analysis
    • No dependency analysis
  • *.m files are analyzed with CppAnalyzer:
    • All basic standard analyses supported (source code overview, duplication, file size, concerns, findings, metrics, controls)
    • Advanced code cleaning (empty lines and comments removed for LOC calculations, additional cleaning for duplication calculations)
    • Unit size analysis
    • Conditional complexity analysis
    • Advanced heuristic dependency analysis
  • *.java files are analyzed with JavaAnalyzer:
    • All basic standard analyses supported (source code overview, duplication, file size, concerns, findings, metrics, controls)
    • Advanced code cleaning (empty lines and comments removed for LOC calculations, additional cleaning for duplication calculations)
    • Unit size analysis
    • Conditional complexity analysis
    • Advanced heuristic dependency analysis (based on package names)
  • *.bzl files are analyzed with DefaultLanguageAnalyzer:
    • All basic standard analyses supported (source code overview, duplication, file size, concerns, findings, metrics, controls)
    • Basic code cleaning (empty lines removed for LOC calculations and duplication calculations)
    • No unit size analysis
    • No conditional complexity analysis
    • No dependency analysis
  • *.h files are analyzed with CppAnalyzer:
    • All basic standard analyses supported (source code overview, duplication, file size, concerns, findings, metrics, controls)
    • Advanced code cleaning (empty lines and comments removed for LOC calculations, additional cleaning for duplication calculations)
    • Unit size analysis
    • Conditional complexity analysis
    • Advanced heuristic dependency analysis


2022-01-30 22:01