deck.gl
Source Code Overview

Source Code Analysis Scope
Files includes and excluded from analyses
  • 1 extension is included in analyses: js
  • 1 criterion is used to exclude files from analysis:
    • exclude files with path like ".*/[.][a-zA-Z0-9_]+.*" (Hidden files and folders) (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.

main38562 LOC (57%) 489 files
test27492 LOC (40%) 309 files
build and deployment1547 LOC (2%) 65 files
generated0 LOC (0%) 0 files
other0 LOC (0%) 0 files
Main Code
All manually created or maintained source code that defines logic of the product that is run in a production environment.
  • The following criteria are used to filter files:
    • files with paths like ".*".
  • 489 files match defined criteria (38,562 lines of code, 100.0% vs. main code). All matches are in *.js files.


*.js38562 LOC (100%) 489 files
Test Code
Used only for testing of the product. Normally not deployed in a production environment.
  • The following criteria are used to filter files:
    • files with paths like ".*/test/.*".
    • files with paths like ".*[.]spec[.]js".
    • files with paths like ".*[-]test[-].*".
    • files with paths like ".*[-]tests/.*".
  • 309 files match defined criteria (27,492 lines of code, 71.3% vs. main code). All matches are in *.js files.


*.js27492 LOC (100%) 309 files
Build and Deployment Code
Source code used to configure or support build and deployment process.
  • The following criteria are used to filter files:
    • files with paths like ".*([.]|/)webpack([.]|/).*".
  • 65 files match defined criteria (1,547 lines of code, 4.0% vs. main code). All matches are in *.js files.


*.js1547 LOC (100%) 65 files
Analyzers
Info about analyzers used for source code examinations.
  • *.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

2020-09-11 22:21