relayjs / relay-examples
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
txt
babelrc
watchmanconfig
eslintignore
prettierignore
  • 13 extensions are included in analyses: js, json, md, css, gitignore, txt, yml, html, graphql, babelrc, watchmanconfig, eslintignore, prettierignore
  • 4 criteria are used to exclude files from analysis:
    • exclude files with path like ".*/[.][a-zA-Z0-9_]+.*" (Hidden files and folders) (10 files).
    • exclude files with path like ".*/flow-typed/.*\.js" (flow-typed) (32 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).
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.

main3025 LOC (43%) 52 files
test0 LOC (0%) 0 files
generated3585 LOC (51%) 34 files
build and deployment0 LOC (0%) 0 files
other377 LOC (5%) 10 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 ".*".
  • 52 files match defined criteria (3,025 lines of code, 100.0% vs. main code):
    • 45 *.js files (2,322 lines of code)
    • 4 *.css files (552 lines of code)
    • 1 *.graphql files (119 lines of code)
    • 2 *.html files (32 lines of code)
  • " *.js" is biggest, containing 76.76% of code.
  • " *.html" is smallest, containing 1.06% of code.


*.js2322 LOC (76%) 45 files
*.css552 LOC (18%) 4 files
*.graphql119 LOC (3%) 1 files
*.html32 LOC (1%) 2 files
Generated Code
Automatically generated files, not manually changed after generation.
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*/__generated__/.*".
  • 34 files match defined criteria (3,585 lines of code, 118.5% vs. main code). All matches are in *.js files.


*.js3585 LOC (100%) 34 files
Other Code
txt
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*[.]md".
    • files with paths like ".*[.]json".
    • files with paths like ".*/README[.][a-z0-9]+".
    • files with paths like ".*/[.]gitignore".
    • files with paths like ".*/[.]eslintignore".
    • files with paths like ".*/[.]prettierignore".
    • files with paths like ".*[.]txt".
  • 10 files match defined criteria (377 lines of code, 12.5% vs. main code):
    • 4 *.json files (242 lines of code)
    • 5 *.md files (133 lines of code)
    • 1 *.txt files (2 lines of code)
  • " *.json" is biggest, containing 64.19% of code.
  • " *.txt" is smallest, containing 0.53% of code.


*.json242 LOC (64%) 4 files
*.md133 LOC (35%) 5 files
*.txt2 LOC (<1%) 1 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
  • *.css files are analyzed with CssAnalyzer:
    • 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)
    • No unit size analysis
    • No conditional complexity analysis
    • No dependency analysis
  • *.graphql 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
  • *.html files are analyzed with HtmlAnalyzer:
    • 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-04-16 07:06