Netflix/ember-nf-graph
Code Volume Analysis scope, overview of main, test, generated, deployment, build, and other code. |
Source Code Analysis Scope
Files includes and excluded from analyses
scoping details...
- 13 extensions are included in analyses: js, html, hbs, css, gitignore, txt, md, json, npmignore, svg, watchmanconfig, editorconfig, yml
- 8 criteria are used to exclude files from analysis:
- exclude files with path like ".*/docs/.*" (Documentation) (95 files).
- exclude files with path like ".*/yui([^.]*)\.js" (YUI) (0 files).
- exclude files with path like ".*/[Vv]endors?/.*" (Dependencies) (0 files).
- exclude files with path like ".*/git[-]commit[-]trailers[.]txt" (Git history trailers) (1 file).
- exclude files with path like ".*/git[-][a-zA-Z0-9_]+[.]txt" (Git data exports for sokrates analyses) (1 file).
- exclude files with path like ".*/_sokrates/.*" (Sokrates files) (0 files).
- exclude files with path like ".*/_sokrates_landscape/.*" (Sokrates landscape files) (0 files).
- exclude files with path like ".*/sokrates_.*?[.]json" (Sokrates conventions and configurations) (0 files).
- The source code folder contains 299 files:
- 177 files are included in analyses.
- 122 files are excluded from analyses:
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.
Main Code
All manually created or maintained source code that defines logic of the product that is run in a production environment.
Test Code
Used only for testing of the product. Normally not deployed in a production environment.
scope details...
- The following criteria are used to filter files:
- files with paths like ".*/[Tt]ests/.*".
- files with paths like ".*[.]spec[.]js".
- files with paths like ".*/protractor[.]conf[.]js".
- 49 files match defined criteria (1,491 LOC, 38.4% vs. main code):
- 36 js files (914 LOC)
- 10 hbs files (526 LOC)
- 2 html files (48 LOC)
- 1 css files (3 LOC)
Build and Deployment Code
Source code used to configure or support build and deployment process.
scope details...
- The following criteria are used to filter files:
- files with paths like ".*/[.]npmignore".
- files with paths like "(.*/)?[.]npmignore".
- files with paths like ".*[.]git[a-z]+".
- files with paths like ".*/[.]gitignore".
- files with paths like ".*[.]editorconfig".
- files with paths like "(.*/)?[.]editorconfig".
- files with paths like ".*/package[.]json".
- files with paths like "(.*/)?[.]eslintrc([.].*)?".
- files with paths like ".*/[.]travis[.]yml".
- 8 files match defined criteria (165 LOC, 4.3% vs. main code):
- 1 js files (76 LOC)
- 1 yaml files (31 LOC)
- 4 gitignore files (23 LOC)
- 1 npmignore files (20 LOC)
- 1 editorconfig files (15 LOC)
Other Code
scope details...
- The following criteria are used to filter files:
- files with paths like ".*[.]md".
- files with paths like ".*/LICENSE[.][a-z0-9]+".
- files with paths like ".*[.]json".
- files with paths like ".*[.]svg".
- files with paths like ".*[.]txt".
- files with paths like ".*/vendor/.*".
- files with paths like ".*/README[.][a-z0-9]+".
- 7 files match defined criteria (428 LOC, 11.0% vs. main code):
- 3 md files (345 LOC)
- 2 json files (76 LOC)
- 1 svg files (4 LOC)
- 1 txt files (3 LOC)
About This Analysis
learn more about scopes (main, test, generated, build, 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.
learn more about used code analyzers...
- *.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
- *.hbs 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
- *.watchmanconfig 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