Duplication · guardian/article-with-signup-counter

Duplication Overall

19% duplication:

501 cleaned lines of cleaned code (without empty lines, comments, and frequently duplicated constructs such as imports)
96 duplicated lines

4 duplicates

dependency graphs: 2D graph | 2D graph (with duplicates)... | 3D graph | 3D graph (with duplicates)...

Duplication per Extension

Duplication per Component (primary)

Longest Duplicates

The list of 4 longest duplicates.

See data for all 4 duplicates...

Size	#	Folders	Files	Lines	Code
27	x 2	src src	countNewSignUpTagsBySection.ts countOldEmbedBySection.ts	45:82 (34%) 42:79 (36%)	view
8	x 2	src src	countNewSignUpTagsBySection.ts countOldEmbedBySection.ts	20:29 (10%) 17:26 (10%)	view
7	x 2	src src	countNewSignUpTagsBySection.ts countOldEmbedBySection.ts	103:110 (8%) 100:107 (9%)	view
6	x 2	src/modules src/modules	fetchData.ts fetchData.ts	54:62 (9%) 75:82 (9%)	view

About This Analysis

For duplication, we look at places in code where there are 6 or more lines of code that are exactly the same.
Before duplication is calculated, the code is cleaned to remove empty lines, comments, and frequently duplicated constructs such as imports.
You should aim at having as little as possible (<5%) of duplicated code as high-level of duplication can lead to maintenance difficulties, poor factoring, and logical contradictions.

Learn more...

To learn more about duplications and techniques for eliminating duplication, Sokrates recommends the following resources:

Avoid Repetition, MartinFlower.com (IEEE Software article)
Refactoring duplicated code, sourcemaking.com
Beck Design Rules, MartinFowler.com
DRY (Don't Repeat Yourself) Principle, Wikipedia
The Cut-and-Paste Programming Software Development Anti-Pattern, sourcemaking.com
Code Smells / Duplicated Code, Jeff Atwood, codinghorror.com:

"Duplicated code is the bane of software development. Stamp out duplication whenever possible. You should always be on the lookout for more subtle cases of near-duplication, too. Don't Repeat Yourself!"

Reducing Coupling, MartinFlower.com (IEEE Software article):

"There are several ways to describe coupling, but it boils down to this: If changing one module in a program requires changing another module, then coupling exists. ... Duplication always implies coupling, because changing one piece of duplicate code implies changing the other."