epam / edp-ddm-process-history-modelFile Size

Intro

File size measurements show the distribution of size of files.
Files are classified in four categories based on their size (lines of code): 1-100 (very small files), 101-200 (small files), 201-500 (medium size files), 501-1000 (long files), 1001+(very long files).
It is a good practice to keep files small. Long files may become "bloaters", code that have increased to such gargantuan proportions that they are hard to work with.

File Size Overall

Legend:

1001+

501-1000

201-500

101-200

1-100

File Size per Extension

1001+

501-1000

201-500

101-200

1-100

File Size per Logical Decomposition

primary

1001+

501-1000

201-500

101-200

1-100

Longest Files (Top 5)

File	# lines	# units
HistoryProcess.java in src/main/java/com/epam/digital/data/platform/bphistory/model	122	26
HistoryTask.java in src/main/java/com/epam/digital/data/platform/bphistory/model	115	24
create-release.groovy in root	2	-
code-review.groovy in root	2	-
build.groovy in root	2	-

Files With Most Units (Top 2)

File	# lines	# units
HistoryProcess.java in src/main/java/com/epam/digital/data/platform/bphistory/model	122	26
HistoryTask.java in src/main/java/com/epam/digital/data/platform/bphistory/model	115	24

Files With Long Lines (Top 0)

There are 0 files with lines longer than 120 characters. In total, there are 0 long lines.

File	# lines	# units	# long lines

Correlations

File Size vs. Commits (all time): 0 points

No data for "commits (all time)" vs. "lines of code".

No data for "contributors (all time)" vs. "lines of code".

No data for "commits (30d)" vs. "lines of code".

No data for "contributors (30d)" vs. "lines of code".

No data for "commits (90d)" vs. "lines of code".

No data for "contributors (90d)" vs. "lines of code".