Public report of plotly/Plotly.NET, published 13 November 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.3). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 13 November 2026, 10:29 UTC · Survey ID cd_2249a91b6d9b4915b866e1346ed021df
plotly/Plotly.NET
Measured 13 November 2026, 10:27 UTC, at code version 8f12280
Supply-chain provenance & signing is not measured: Supply-chain provenance is not scored (this pipeline releases no artifact), but its build steps or GitHub Actions workflows have integrity defects, or nothing watches its dependency set for published advisories.
CAI scoreAdequate
CriticalWeakAdequateStrongExemplary
Up 4 since the last survey
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A medium codebase: 60,231 lines of product code in 4 projects, tests not counted · Estimated rebuild effort: about 0.5 person-years · Weakest lens: Production Readiness, 58
Findings by how serious they are
13 critical497 serious13 minor
8 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Canine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
13 November 2026, 10:27 UTC
A measurement, not a certificate. The Code Assurance Index records a number
together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee
the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that
implements it, and today the Canine Code Analyzer is the only one that does.
The score is deterministic, which means the same code always gets the same score. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸
40of 40 dimensions measured by tools.
516of 523 findings point to an exact file and line, so you can open each one in the code. The other 7 concern the repository as a whole, such as missing documentation.
40dimensions across 6 lenses, read from 60,231 lines of product code in 4 projects.
plotly/Plotly.NET falls short of our standard for production because we found no automated security scanning of the code, its secrets or its dependencies. It scores 69 out of 100 and is rated Adequate, and all 13 of its critical findings are security problems.
Production Readiness, at 58, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 7 points. Adding a release approval would lift Production Readiness itself, worth about 4 points. Raising Production Readiness to 70 would lift the score to about 72.
Twelve pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. One password or key is open to anyone who can read the repository. Pinning each tool to an exact version and replacing the exposed password or key would close both risks.
The product code is 60,231 lines, about €78,000 to rebuild. Two of our security checks couldn't finish, among them the one for known security holes in its packages, so those results are missing, not clean passes.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
We compare every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.
Fixed since the last survey: 2 findings
These 2 critical or serious findings were in the previous survey, on 23 October 2026, and are gone from this one.
€26,000 to €130,000, for 431 to 1,362 hours of work, about 0.5 person-years for 1 to 2 engineers
Difficulty of the problem
Low, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×1.0 at a score of 69. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Medium: 60,231 lines of product code
Comment lines
The estimate prices 57,431 lines. Comment lines count towards the size of 60,231 lines but aren't priced as work.
What it is not
Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.
How the estimate is made: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Record your significant design decisions.
Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
Resolve the 1 Off-boarding risk finding(s) in Bus Factor.
Raises the score by about 0.8 points · Low effort · Bus Factor
Diagnosis: what the measurements show together
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
Where the investment is most exposed · Value at risk
This code would cost about €78,000 to build again, about 0.5 person-years of work. Its weakest lens is Production Readiness, at 58 (Adequate). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
If you do one thing first · First action
Record your significant design decisions. Of all the actions in this report, it raises the score most for the work it takes: about 7 points for medium effort. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
Architecture — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.
Architecture: which parts of the code depend on which
The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.
65 modules, with 119 dependencies between them. One loop runs through 3 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 25 more are left out to keep it readable.
Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
Plotly.NET.ConfigObjects uses Plotly.NET.StyleParam, so a change to Plotly.NET.StyleParam can break Plotly.NET.ConfigObjects, while a change to Plotly.NET.ConfigObjects can't break Plotly.NET.StyleParam.
Position
Below the diagonal: Plotly.NET.ConfigObjects uses a module listed above it, which is the healthy direction.
150 pairs of types, where a type in Plotly.NET.LayoutObjects uses a type in Plotly.NET.StyleParam. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Plotly.NET.LayoutObjects uses Plotly.NET.StyleParam, so a change to Plotly.NET.StyleParam can break Plotly.NET.LayoutObjects, while a change to Plotly.NET.LayoutObjects can't break Plotly.NET.StyleParam.
Position
Below the diagonal: Plotly.NET.LayoutObjects uses a module listed above it, which is the healthy direction.
4→6 Plotly.NET.LayoutObjects uses Plotly.NETpart of a loop✕
Connections
57 pairs of types, where a type in Plotly.NET.LayoutObjects uses a type in Plotly.NET. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Plotly.NET.LayoutObjects uses Plotly.NET, so a change to Plotly.NET can break Plotly.NET.LayoutObjects, while a change to Plotly.NET.LayoutObjects can't break Plotly.NET.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
35 pairs of types, where a type in Plotly.NET.TraceObjects uses a type in Plotly.NET.StyleParam. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Plotly.NET.TraceObjects uses Plotly.NET.StyleParam, so a change to Plotly.NET.StyleParam can break Plotly.NET.TraceObjects, while a change to Plotly.NET.TraceObjects can't break Plotly.NET.StyleParam.
Position
Below the diagonal: Plotly.NET.TraceObjects uses a module listed above it, which is the healthy direction.
Plotly.NET.TraceObjects uses Plotly.NET.LayoutObjects, so a change to Plotly.NET.LayoutObjects can break Plotly.NET.TraceObjects, while a change to Plotly.NET.TraceObjects can't break Plotly.NET.LayoutObjects.
Position
Below the diagonal: Plotly.NET.TraceObjects uses a module listed above it, which is the healthy direction.
5→6 Plotly.NET.TraceObjects uses Plotly.NETpart of a loop✕
Connections
42 pairs of types, where a type in Plotly.NET.TraceObjects uses a type in Plotly.NET. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Plotly.NET.TraceObjects uses Plotly.NET, so a change to Plotly.NET can break Plotly.NET.TraceObjects, while a change to Plotly.NET.TraceObjects can't break Plotly.NET.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
220 pairs of types, where a type in Plotly.NET uses a type in Plotly.NET.StyleParam. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Plotly.NET uses Plotly.NET.StyleParam, so a change to Plotly.NET.StyleParam can break Plotly.NET, while a change to Plotly.NET can't break Plotly.NET.StyleParam.
Position
Below the diagonal: Plotly.NET uses a module listed above it, which is the healthy direction.
Plotly.NET uses Plotly.NET.ConfigObjects, so a change to Plotly.NET.ConfigObjects can break Plotly.NET, while a change to Plotly.NET can't break Plotly.NET.ConfigObjects.
Position
Below the diagonal: Plotly.NET uses a module listed above it, which is the healthy direction.
77 pairs of types, where a type in Plotly.NET uses a type in Plotly.NET.LayoutObjects. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Plotly.NET uses Plotly.NET.LayoutObjects, so a change to Plotly.NET.LayoutObjects can break Plotly.NET, while a change to Plotly.NET can't break Plotly.NET.LayoutObjects.
Position
Below the diagonal: Plotly.NET uses a module listed above it, which is the healthy direction.
65 pairs of types, where a type in Plotly.NET uses a type in Plotly.NET.TraceObjects. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Plotly.NET uses Plotly.NET.TraceObjects, so a change to Plotly.NET.TraceObjects can break Plotly.NET, while a change to Plotly.NET can't break Plotly.NET.TraceObjects.
Position
Below the diagonal: Plotly.NET uses a module listed above it, which is the healthy direction.
Plotly.NET.Chart2D_Area uses Plotly.NET.StyleParam, so a change to Plotly.NET.StyleParam can break Plotly.NET.Chart2D_Area, while a change to Plotly.NET.Chart2D_Area can't break Plotly.NET.StyleParam.
Position
Below the diagonal: Plotly.NET.Chart2D_Area uses a module listed above it, which is the healthy direction.
Plotly.NET.Chart2D_Area uses Plotly.NET.TraceObjects, so a change to Plotly.NET.TraceObjects can break Plotly.NET.Chart2D_Area, while a change to Plotly.NET.Chart2D_Area can't break Plotly.NET.TraceObjects.
Position
Below the diagonal: Plotly.NET.Chart2D_Area uses a module listed above it, which is the healthy direction.
Plotly.NET.Chart2D_Area uses Plotly.NET, so a change to Plotly.NET can break Plotly.NET.Chart2D_Area, while a change to Plotly.NET.Chart2D_Area can't break Plotly.NET.
Position
Below the diagonal: Plotly.NET.Chart2D_Area uses a module listed above it, which is the healthy direction.
Plotly.NET.Chart2D_Bar uses Plotly.NET.StyleParam, so a change to Plotly.NET.StyleParam can break Plotly.NET.Chart2D_Bar, while a change to Plotly.NET.Chart2D_Bar can't break Plotly.NET.StyleParam.
Position
Below the diagonal: Plotly.NET.Chart2D_Bar uses a module listed above it, which is the healthy direction.
Plotly.NET.Chart2D_Bar uses Plotly.NET.TraceObjects, so a change to Plotly.NET.TraceObjects can break Plotly.NET.Chart2D_Bar, while a change to Plotly.NET.Chart2D_Bar can't break Plotly.NET.TraceObjects.
Position
Below the diagonal: Plotly.NET.Chart2D_Bar uses a module listed above it, which is the healthy direction.
Plotly.NET.Chart2D_Bar uses Plotly.NET, so a change to Plotly.NET can break Plotly.NET.Chart2D_Bar, while a change to Plotly.NET.Chart2D_Bar can't break Plotly.NET.
Position
Below the diagonal: Plotly.NET.Chart2D_Bar uses a module listed above it, which is the healthy direction.
Plotly.NET.Chart2D_Distribution uses Plotly.NET.StyleParam, so a change to Plotly.NET.StyleParam can break Plotly.NET.Chart2D_Distribution, while a change to Plotly.NET.Chart2D_Distribution can't break Plotly.NET.StyleParam.
Position
Below the diagonal: Plotly.NET.Chart2D_Distribution uses a module listed above it, which is the healthy direction.
Plotly.NET.Chart2D_Distribution uses Plotly.NET.TraceObjects, so a change to Plotly.NET.TraceObjects can break Plotly.NET.Chart2D_Distribution, while a change to Plotly.NET.Chart2D_Distribution can't break Plotly.NET.TraceObjects.
Position
Below the diagonal: Plotly.NET.Chart2D_Distribution uses a module listed above it, which is the healthy direction.
Plotly.NET.Chart2D_Distribution uses Plotly.NET, so a change to Plotly.NET can break Plotly.NET.Chart2D_Distribution, while a change to Plotly.NET.Chart2D_Distribution can't break Plotly.NET.
Position
Below the diagonal: Plotly.NET.Chart2D_Distribution uses a module listed above it, which is the healthy direction.
Plotly.NET.Chart2D_Finance uses Plotly.NET.TraceObjects, so a change to Plotly.NET.TraceObjects can break Plotly.NET.Chart2D_Finance, while a change to Plotly.NET.Chart2D_Finance can't break Plotly.NET.TraceObjects.
Position
Below the diagonal: Plotly.NET.Chart2D_Finance uses a module listed above it, which is the healthy direction.
Plotly.NET.Chart2D_Finance uses Plotly.NET, so a change to Plotly.NET can break Plotly.NET.Chart2D_Finance, while a change to Plotly.NET.Chart2D_Finance can't break Plotly.NET.
Position
Below the diagonal: Plotly.NET.Chart2D_Finance uses a module listed above it, which is the healthy direction.
Plotly.NET.Chart2D_Funnel uses Plotly.NET.StyleParam, so a change to Plotly.NET.StyleParam can break Plotly.NET.Chart2D_Funnel, while a change to Plotly.NET.Chart2D_Funnel can't break Plotly.NET.StyleParam.
Position
Below the diagonal: Plotly.NET.Chart2D_Funnel uses a module listed above it, which is the healthy direction.
Plotly.NET.Chart2D_Funnel uses Plotly.NET.TraceObjects, so a change to Plotly.NET.TraceObjects can break Plotly.NET.Chart2D_Funnel, while a change to Plotly.NET.Chart2D_Funnel can't break Plotly.NET.TraceObjects.
Position
Below the diagonal: Plotly.NET.Chart2D_Funnel uses a module listed above it, which is the healthy direction.
Plotly.NET.Chart2D_Funnel uses Plotly.NET, so a change to Plotly.NET can break Plotly.NET.Chart2D_Funnel, while a change to Plotly.NET.Chart2D_Funnel can't break Plotly.NET.
Position
Below the diagonal: Plotly.NET.Chart2D_Funnel uses a module listed above it, which is the healthy direction.
Plotly.NET.Chart2D_Heatmap uses Plotly.NET.StyleParam, so a change to Plotly.NET.StyleParam can break Plotly.NET.Chart2D_Heatmap, while a change to Plotly.NET.Chart2D_Heatmap can't break Plotly.NET.StyleParam.
Position
Below the diagonal: Plotly.NET.Chart2D_Heatmap uses a module listed above it, which is the healthy direction.
Plotly.NET.Chart2D_Heatmap uses Plotly.NET.TraceObjects, so a change to Plotly.NET.TraceObjects can break Plotly.NET.Chart2D_Heatmap, while a change to Plotly.NET.Chart2D_Heatmap can't break Plotly.NET.TraceObjects.
Position
Below the diagonal: Plotly.NET.Chart2D_Heatmap uses a module listed above it, which is the healthy direction.
Plotly.NET.Chart2D_Heatmap uses Plotly.NET, so a change to Plotly.NET can break Plotly.NET.Chart2D_Heatmap, while a change to Plotly.NET.Chart2D_Heatmap can't break Plotly.NET.
Position
Below the diagonal: Plotly.NET.Chart2D_Heatmap uses a module listed above it, which is the healthy direction.
Plotly.NET.Chart2D_Histogram uses Plotly.NET.StyleParam, so a change to Plotly.NET.StyleParam can break Plotly.NET.Chart2D_Histogram, while a change to Plotly.NET.Chart2D_Histogram can't break Plotly.NET.StyleParam.
Position
Below the diagonal: Plotly.NET.Chart2D_Histogram uses a module listed above it, which is the healthy direction.
Plotly.NET.Chart2D_Histogram uses Plotly.NET.LayoutObjects, so a change to Plotly.NET.LayoutObjects can break Plotly.NET.Chart2D_Histogram, while a change to Plotly.NET.Chart2D_Histogram can't break Plotly.NET.LayoutObjects.
Position
Below the diagonal: Plotly.NET.Chart2D_Histogram uses a module listed above it, which is the healthy direction.
Plotly.NET.Chart2D_Histogram uses Plotly.NET.TraceObjects, so a change to Plotly.NET.TraceObjects can break Plotly.NET.Chart2D_Histogram, while a change to Plotly.NET.Chart2D_Histogram can't break Plotly.NET.TraceObjects.
Position
Below the diagonal: Plotly.NET.Chart2D_Histogram uses a module listed above it, which is the healthy direction.
Plotly.NET.Chart2D_Histogram uses Plotly.NET, so a change to Plotly.NET can break Plotly.NET.Chart2D_Histogram, while a change to Plotly.NET.Chart2D_Histogram can't break Plotly.NET.
Position
Below the diagonal: Plotly.NET.Chart2D_Histogram uses a module listed above it, which is the healthy direction.
Plotly.NET.Chart2D_Scatter uses Plotly.NET.StyleParam, so a change to Plotly.NET.StyleParam can break Plotly.NET.Chart2D_Scatter, while a change to Plotly.NET.Chart2D_Scatter can't break Plotly.NET.StyleParam.
Position
Below the diagonal: Plotly.NET.Chart2D_Scatter uses a module listed above it, which is the healthy direction.
Plotly.NET.Chart2D_Scatter uses Plotly.NET.TraceObjects, so a change to Plotly.NET.TraceObjects can break Plotly.NET.Chart2D_Scatter, while a change to Plotly.NET.Chart2D_Scatter can't break Plotly.NET.TraceObjects.
Position
Below the diagonal: Plotly.NET.Chart2D_Scatter uses a module listed above it, which is the healthy direction.
Plotly.NET.Chart2D_Scatter uses Plotly.NET, so a change to Plotly.NET can break Plotly.NET.Chart2D_Scatter, while a change to Plotly.NET.Chart2D_Scatter can't break Plotly.NET.
Position
Below the diagonal: Plotly.NET.Chart2D_Scatter uses a module listed above it, which is the healthy direction.
Plotly.NET.Chart2D_Splom uses Plotly.NET.StyleParam, so a change to Plotly.NET.StyleParam can break Plotly.NET.Chart2D_Splom, while a change to Plotly.NET.Chart2D_Splom can't break Plotly.NET.StyleParam.
Position
Below the diagonal: Plotly.NET.Chart2D_Splom uses a module listed above it, which is the healthy direction.
Plotly.NET.Chart2D_Splom uses Plotly.NET.TraceObjects, so a change to Plotly.NET.TraceObjects can break Plotly.NET.Chart2D_Splom, while a change to Plotly.NET.Chart2D_Splom can't break Plotly.NET.TraceObjects.
Position
Below the diagonal: Plotly.NET.Chart2D_Splom uses a module listed above it, which is the healthy direction.
Plotly.NET.Chart2D_Splom uses Plotly.NET, so a change to Plotly.NET can break Plotly.NET.Chart2D_Splom, while a change to Plotly.NET.Chart2D_Splom can't break Plotly.NET.
Position
Below the diagonal: Plotly.NET.Chart2D_Splom uses a module listed above it, which is the healthy direction.
Plotly.NET.Chart2D_Statistical uses Plotly.NET.StyleParam, so a change to Plotly.NET.StyleParam can break Plotly.NET.Chart2D_Statistical, while a change to Plotly.NET.Chart2D_Statistical can't break Plotly.NET.StyleParam.
Position
Below the diagonal: Plotly.NET.Chart2D_Statistical uses a module listed above it, which is the healthy direction.
Plotly.NET.Chart2D_Statistical uses Plotly.NET.TraceObjects, so a change to Plotly.NET.TraceObjects can break Plotly.NET.Chart2D_Statistical, while a change to Plotly.NET.Chart2D_Statistical can't break Plotly.NET.TraceObjects.
Position
Below the diagonal: Plotly.NET.Chart2D_Statistical uses a module listed above it, which is the healthy direction.
Plotly.NET.Chart2D_Statistical uses Plotly.NET, so a change to Plotly.NET can break Plotly.NET.Chart2D_Statistical, while a change to Plotly.NET.Chart2D_Statistical can't break Plotly.NET.
Position
Below the diagonal: Plotly.NET.Chart2D_Statistical uses a module listed above it, which is the healthy direction.
Plotly.NET.Chart3D_Scatter uses Plotly.NET.StyleParam, so a change to Plotly.NET.StyleParam can break Plotly.NET.Chart3D_Scatter, while a change to Plotly.NET.Chart3D_Scatter can't break Plotly.NET.StyleParam.
Position
Below the diagonal: Plotly.NET.Chart3D_Scatter uses a module listed above it, which is the healthy direction.
Plotly.NET.Chart3D_Scatter uses Plotly.NET.LayoutObjects, so a change to Plotly.NET.LayoutObjects can break Plotly.NET.Chart3D_Scatter, while a change to Plotly.NET.Chart3D_Scatter can't break Plotly.NET.LayoutObjects.
Position
Below the diagonal: Plotly.NET.Chart3D_Scatter uses a module listed above it, which is the healthy direction.
Plotly.NET.Chart3D_Scatter uses Plotly.NET.TraceObjects, so a change to Plotly.NET.TraceObjects can break Plotly.NET.Chart3D_Scatter, while a change to Plotly.NET.Chart3D_Scatter can't break Plotly.NET.TraceObjects.
Position
Below the diagonal: Plotly.NET.Chart3D_Scatter uses a module listed above it, which is the healthy direction.
Plotly.NET.Chart3D_Scatter uses Plotly.NET, so a change to Plotly.NET can break Plotly.NET.Chart3D_Scatter, while a change to Plotly.NET.Chart3D_Scatter can't break Plotly.NET.
Position
Below the diagonal: Plotly.NET.Chart3D_Scatter uses a module listed above it, which is the healthy direction.
Plotly.NET.Chart3D_Surface uses Plotly.NET.StyleParam, so a change to Plotly.NET.StyleParam can break Plotly.NET.Chart3D_Surface, while a change to Plotly.NET.Chart3D_Surface can't break Plotly.NET.StyleParam.
Position
Below the diagonal: Plotly.NET.Chart3D_Surface uses a module listed above it, which is the healthy direction.
Plotly.NET.Chart3D_Surface uses Plotly.NET.LayoutObjects, so a change to Plotly.NET.LayoutObjects can break Plotly.NET.Chart3D_Surface, while a change to Plotly.NET.Chart3D_Surface can't break Plotly.NET.LayoutObjects.
Position
Below the diagonal: Plotly.NET.Chart3D_Surface uses a module listed above it, which is the healthy direction.
Plotly.NET.Chart3D_Surface uses Plotly.NET.TraceObjects, so a change to Plotly.NET.TraceObjects can break Plotly.NET.Chart3D_Surface, while a change to Plotly.NET.Chart3D_Surface can't break Plotly.NET.TraceObjects.
Position
Below the diagonal: Plotly.NET.Chart3D_Surface uses a module listed above it, which is the healthy direction.
Plotly.NET.Chart3D_Surface uses Plotly.NET, so a change to Plotly.NET can break Plotly.NET.Chart3D_Surface, while a change to Plotly.NET.Chart3D_Surface can't break Plotly.NET.
Position
Below the diagonal: Plotly.NET.Chart3D_Surface uses a module listed above it, which is the healthy direction.
Plotly.NET.Chart3D_VectorField uses Plotly.NET.StyleParam, so a change to Plotly.NET.StyleParam can break Plotly.NET.Chart3D_VectorField, while a change to Plotly.NET.Chart3D_VectorField can't break Plotly.NET.StyleParam.
Position
Below the diagonal: Plotly.NET.Chart3D_VectorField uses a module listed above it, which is the healthy direction.
Plotly.NET.Chart3D_VectorField uses Plotly.NET.LayoutObjects, so a change to Plotly.NET.LayoutObjects can break Plotly.NET.Chart3D_VectorField, while a change to Plotly.NET.Chart3D_VectorField can't break Plotly.NET.LayoutObjects.
Position
Below the diagonal: Plotly.NET.Chart3D_VectorField uses a module listed above it, which is the healthy direction.
Plotly.NET.Chart3D_VectorField uses Plotly.NET.TraceObjects, so a change to Plotly.NET.TraceObjects can break Plotly.NET.Chart3D_VectorField, while a change to Plotly.NET.Chart3D_VectorField can't break Plotly.NET.TraceObjects.
Position
Below the diagonal: Plotly.NET.Chart3D_VectorField uses a module listed above it, which is the healthy direction.
Plotly.NET.Chart3D_VectorField uses Plotly.NET, so a change to Plotly.NET can break Plotly.NET.Chart3D_VectorField, while a change to Plotly.NET.Chart3D_VectorField can't break Plotly.NET.
Position
Below the diagonal: Plotly.NET.Chart3D_VectorField uses a module listed above it, which is the healthy direction.
Plotly.NET.Chart3D_Volume uses Plotly.NET.StyleParam, so a change to Plotly.NET.StyleParam can break Plotly.NET.Chart3D_Volume, while a change to Plotly.NET.Chart3D_Volume can't break Plotly.NET.StyleParam.
Position
Below the diagonal: Plotly.NET.Chart3D_Volume uses a module listed above it, which is the healthy direction.
Plotly.NET.Chart3D_Volume uses Plotly.NET.LayoutObjects, so a change to Plotly.NET.LayoutObjects can break Plotly.NET.Chart3D_Volume, while a change to Plotly.NET.Chart3D_Volume can't break Plotly.NET.LayoutObjects.
Position
Below the diagonal: Plotly.NET.Chart3D_Volume uses a module listed above it, which is the healthy direction.
Plotly.NET.Chart3D_Volume uses Plotly.NET.TraceObjects, so a change to Plotly.NET.TraceObjects can break Plotly.NET.Chart3D_Volume, while a change to Plotly.NET.Chart3D_Volume can't break Plotly.NET.TraceObjects.
Position
Below the diagonal: Plotly.NET.Chart3D_Volume uses a module listed above it, which is the healthy direction.
Plotly.NET.Chart3D_Volume uses Plotly.NET, so a change to Plotly.NET can break Plotly.NET.Chart3D_Volume, while a change to Plotly.NET.Chart3D_Volume can't break Plotly.NET.
Position
Below the diagonal: Plotly.NET.Chart3D_Volume uses a module listed above it, which is the healthy direction.
Plotly.NET.ChartCarpet_Base uses Plotly.NET.StyleParam, so a change to Plotly.NET.StyleParam can break Plotly.NET.ChartCarpet_Base, while a change to Plotly.NET.ChartCarpet_Base can't break Plotly.NET.StyleParam.
Position
Below the diagonal: Plotly.NET.ChartCarpet_Base uses a module listed above it, which is the healthy direction.
Plotly.NET.ChartCarpet_Base uses Plotly.NET.LayoutObjects, so a change to Plotly.NET.LayoutObjects can break Plotly.NET.ChartCarpet_Base, while a change to Plotly.NET.ChartCarpet_Base can't break Plotly.NET.LayoutObjects.
Position
Below the diagonal: Plotly.NET.ChartCarpet_Base uses a module listed above it, which is the healthy direction.
Plotly.NET.ChartCarpet_Base uses Plotly.NET, so a change to Plotly.NET can break Plotly.NET.ChartCarpet_Base, while a change to Plotly.NET.ChartCarpet_Base can't break Plotly.NET.
Position
Below the diagonal: Plotly.NET.ChartCarpet_Base uses a module listed above it, which is the healthy direction.
Plotly.NET.ChartCarpet_Contour uses Plotly.NET.StyleParam, so a change to Plotly.NET.StyleParam can break Plotly.NET.ChartCarpet_Contour, while a change to Plotly.NET.ChartCarpet_Contour can't break Plotly.NET.StyleParam.
Position
Below the diagonal: Plotly.NET.ChartCarpet_Contour uses a module listed above it, which is the healthy direction.
Plotly.NET.ChartCarpet_Contour uses Plotly.NET.TraceObjects, so a change to Plotly.NET.TraceObjects can break Plotly.NET.ChartCarpet_Contour, while a change to Plotly.NET.ChartCarpet_Contour can't break Plotly.NET.TraceObjects.
Position
Below the diagonal: Plotly.NET.ChartCarpet_Contour uses a module listed above it, which is the healthy direction.
Plotly.NET.ChartCarpet_Contour uses Plotly.NET, so a change to Plotly.NET can break Plotly.NET.ChartCarpet_Contour, while a change to Plotly.NET.ChartCarpet_Contour can't break Plotly.NET.
Position
Below the diagonal: Plotly.NET.ChartCarpet_Contour uses a module listed above it, which is the healthy direction.
Plotly.NET.ChartCarpet_Scatter uses Plotly.NET.StyleParam, so a change to Plotly.NET.StyleParam can break Plotly.NET.ChartCarpet_Scatter, while a change to Plotly.NET.ChartCarpet_Scatter can't break Plotly.NET.StyleParam.
Position
Below the diagonal: Plotly.NET.ChartCarpet_Scatter uses a module listed above it, which is the healthy direction.
Plotly.NET.ChartCarpet_Scatter uses Plotly.NET.TraceObjects, so a change to Plotly.NET.TraceObjects can break Plotly.NET.ChartCarpet_Scatter, while a change to Plotly.NET.ChartCarpet_Scatter can't break Plotly.NET.TraceObjects.
Position
Below the diagonal: Plotly.NET.ChartCarpet_Scatter uses a module listed above it, which is the healthy direction.
Plotly.NET.ChartCarpet_Scatter uses Plotly.NET, so a change to Plotly.NET can break Plotly.NET.ChartCarpet_Scatter, while a change to Plotly.NET.ChartCarpet_Scatter can't break Plotly.NET.
Position
Below the diagonal: Plotly.NET.ChartCarpet_Scatter uses a module listed above it, which is the healthy direction.
Plotly.NET.ChartComposite_SetComparison uses Plotly.NET, so a change to Plotly.NET can break Plotly.NET.ChartComposite_SetComparison, while a change to Plotly.NET.ChartComposite_SetComparison can't break Plotly.NET.
Position
Below the diagonal: Plotly.NET.ChartComposite_SetComparison uses a module listed above it, which is the healthy direction.
Plotly.NET.ChartComposite_SetComparison.UpSetUtils uses Plotly.NET.LayoutObjects, so a change to Plotly.NET.LayoutObjects can break Plotly.NET.ChartComposite_SetComparison.UpSetUtils, while a change to Plotly.NET.ChartComposite_SetComparison.UpSetUtils can't break Plotly.NET.LayoutObjects.
Position
Below the diagonal: Plotly.NET.ChartComposite_SetComparison.UpSetUtils uses a module listed above it, which is the healthy direction.
Plotly.NET.ChartComposite_SetComparison.UpSetUtils uses Plotly.NET, so a change to Plotly.NET can break Plotly.NET.ChartComposite_SetComparison.UpSetUtils, while a change to Plotly.NET.ChartComposite_SetComparison.UpSetUtils can't break Plotly.NET.
Position
Below the diagonal: Plotly.NET.ChartComposite_SetComparison.UpSetUtils uses a module listed above it, which is the healthy direction.
Plotly.NET.ChartComposite_SetComparison.VennUtils uses Plotly.NET.LayoutObjects, so a change to Plotly.NET.LayoutObjects can break Plotly.NET.ChartComposite_SetComparison.VennUtils, while a change to Plotly.NET.ChartComposite_SetComparison.VennUtils can't break Plotly.NET.LayoutObjects.
Position
Below the diagonal: Plotly.NET.ChartComposite_SetComparison.VennUtils uses a module listed above it, which is the healthy direction.
Plotly.NET.ChartComposite_SetComparison.VennUtils uses Plotly.NET, so a change to Plotly.NET can break Plotly.NET.ChartComposite_SetComparison.VennUtils, while a change to Plotly.NET.ChartComposite_SetComparison.VennUtils can't break Plotly.NET.
Position
Below the diagonal: Plotly.NET.ChartComposite_SetComparison.VennUtils uses a module listed above it, which is the healthy direction.
Plotly.NET.ChartDomain_Hierarchy uses Plotly.NET.StyleParam, so a change to Plotly.NET.StyleParam can break Plotly.NET.ChartDomain_Hierarchy, while a change to Plotly.NET.ChartDomain_Hierarchy can't break Plotly.NET.StyleParam.
Position
Below the diagonal: Plotly.NET.ChartDomain_Hierarchy uses a module listed above it, which is the healthy direction.
Plotly.NET.ChartDomain_Hierarchy uses Plotly.NET.TraceObjects, so a change to Plotly.NET.TraceObjects can break Plotly.NET.ChartDomain_Hierarchy, while a change to Plotly.NET.ChartDomain_Hierarchy can't break Plotly.NET.TraceObjects.
Position
Below the diagonal: Plotly.NET.ChartDomain_Hierarchy uses a module listed above it, which is the healthy direction.
Plotly.NET.ChartDomain_Hierarchy uses Plotly.NET, so a change to Plotly.NET can break Plotly.NET.ChartDomain_Hierarchy, while a change to Plotly.NET.ChartDomain_Hierarchy can't break Plotly.NET.
Position
Below the diagonal: Plotly.NET.ChartDomain_Hierarchy uses a module listed above it, which is the healthy direction.
Plotly.NET.ChartDomain_Icicle uses Plotly.NET.StyleParam, so a change to Plotly.NET.StyleParam can break Plotly.NET.ChartDomain_Icicle, while a change to Plotly.NET.ChartDomain_Icicle can't break Plotly.NET.StyleParam.
Position
Below the diagonal: Plotly.NET.ChartDomain_Icicle uses a module listed above it, which is the healthy direction.
Plotly.NET.ChartDomain_Icicle uses Plotly.NET.TraceObjects, so a change to Plotly.NET.TraceObjects can break Plotly.NET.ChartDomain_Icicle, while a change to Plotly.NET.ChartDomain_Icicle can't break Plotly.NET.TraceObjects.
Position
Below the diagonal: Plotly.NET.ChartDomain_Icicle uses a module listed above it, which is the healthy direction.
Plotly.NET.ChartDomain_Icicle uses Plotly.NET, so a change to Plotly.NET can break Plotly.NET.ChartDomain_Icicle, while a change to Plotly.NET.ChartDomain_Icicle can't break Plotly.NET.
Position
Below the diagonal: Plotly.NET.ChartDomain_Icicle uses a module listed above it, which is the healthy direction.
Plotly.NET.ChartDomain_Pie uses Plotly.NET.StyleParam, so a change to Plotly.NET.StyleParam can break Plotly.NET.ChartDomain_Pie, while a change to Plotly.NET.ChartDomain_Pie can't break Plotly.NET.StyleParam.
Position
Below the diagonal: Plotly.NET.ChartDomain_Pie uses a module listed above it, which is the healthy direction.
Plotly.NET.ChartDomain_Pie uses Plotly.NET.TraceObjects, so a change to Plotly.NET.TraceObjects can break Plotly.NET.ChartDomain_Pie, while a change to Plotly.NET.ChartDomain_Pie can't break Plotly.NET.TraceObjects.
Position
Below the diagonal: Plotly.NET.ChartDomain_Pie uses a module listed above it, which is the healthy direction.
Plotly.NET.ChartDomain_Pie uses Plotly.NET, so a change to Plotly.NET can break Plotly.NET.ChartDomain_Pie, while a change to Plotly.NET.ChartDomain_Pie can't break Plotly.NET.
Position
Below the diagonal: Plotly.NET.ChartDomain_Pie uses a module listed above it, which is the healthy direction.
Plotly.NET.ChartDomain_Relations uses Plotly.NET.StyleParam, so a change to Plotly.NET.StyleParam can break Plotly.NET.ChartDomain_Relations, while a change to Plotly.NET.ChartDomain_Relations can't break Plotly.NET.StyleParam.
Position
Below the diagonal: Plotly.NET.ChartDomain_Relations uses a module listed above it, which is the healthy direction.
Plotly.NET.ChartDomain_Relations uses Plotly.NET.TraceObjects, so a change to Plotly.NET.TraceObjects can break Plotly.NET.ChartDomain_Relations, while a change to Plotly.NET.ChartDomain_Relations can't break Plotly.NET.TraceObjects.
Position
Below the diagonal: Plotly.NET.ChartDomain_Relations uses a module listed above it, which is the healthy direction.
Plotly.NET.ChartDomain_Relations uses Plotly.NET, so a change to Plotly.NET can break Plotly.NET.ChartDomain_Relations, while a change to Plotly.NET.ChartDomain_Relations can't break Plotly.NET.
Position
Below the diagonal: Plotly.NET.ChartDomain_Relations uses a module listed above it, which is the healthy direction.
Plotly.NET.ChartDomain_Table uses Plotly.NET.StyleParam, so a change to Plotly.NET.StyleParam can break Plotly.NET.ChartDomain_Table, while a change to Plotly.NET.ChartDomain_Table can't break Plotly.NET.StyleParam.
Position
Below the diagonal: Plotly.NET.ChartDomain_Table uses a module listed above it, which is the healthy direction.
Plotly.NET.ChartDomain_Table uses Plotly.NET.LayoutObjects, so a change to Plotly.NET.LayoutObjects can break Plotly.NET.ChartDomain_Table, while a change to Plotly.NET.ChartDomain_Table can't break Plotly.NET.LayoutObjects.
Position
Below the diagonal: Plotly.NET.ChartDomain_Table uses a module listed above it, which is the healthy direction.
Plotly.NET.ChartDomain_Table uses Plotly.NET.TraceObjects, so a change to Plotly.NET.TraceObjects can break Plotly.NET.ChartDomain_Table, while a change to Plotly.NET.ChartDomain_Table can't break Plotly.NET.TraceObjects.
Position
Below the diagonal: Plotly.NET.ChartDomain_Table uses a module listed above it, which is the healthy direction.
Plotly.NET.ChartDomain_Table uses Plotly.NET, so a change to Plotly.NET can break Plotly.NET.ChartDomain_Table, while a change to Plotly.NET.ChartDomain_Table can't break Plotly.NET.
Position
Below the diagonal: Plotly.NET.ChartDomain_Table uses a module listed above it, which is the healthy direction.
Plotly.NET.ChartMap_Density uses Plotly.NET.StyleParam, so a change to Plotly.NET.StyleParam can break Plotly.NET.ChartMap_Density, while a change to Plotly.NET.ChartMap_Density can't break Plotly.NET.StyleParam.
Position
Below the diagonal: Plotly.NET.ChartMap_Density uses a module listed above it, which is the healthy direction.
Plotly.NET.ChartMap_Density uses Plotly.NET, so a change to Plotly.NET can break Plotly.NET.ChartMap_Density, while a change to Plotly.NET.ChartMap_Density can't break Plotly.NET.
Position
Below the diagonal: Plotly.NET.ChartMap_Density uses a module listed above it, which is the healthy direction.
Plotly.NET.ChartMap_Geo uses Plotly.NET.StyleParam, so a change to Plotly.NET.StyleParam can break Plotly.NET.ChartMap_Geo, while a change to Plotly.NET.ChartMap_Geo can't break Plotly.NET.StyleParam.
Position
Below the diagonal: Plotly.NET.ChartMap_Geo uses a module listed above it, which is the healthy direction.
Plotly.NET.ChartMap_Geo uses Plotly.NET.TraceObjects, so a change to Plotly.NET.TraceObjects can break Plotly.NET.ChartMap_Geo, while a change to Plotly.NET.ChartMap_Geo can't break Plotly.NET.TraceObjects.
Position
Below the diagonal: Plotly.NET.ChartMap_Geo uses a module listed above it, which is the healthy direction.
Plotly.NET.ChartMap_Geo uses Plotly.NET, so a change to Plotly.NET can break Plotly.NET.ChartMap_Geo, while a change to Plotly.NET.ChartMap_Geo can't break Plotly.NET.
Position
Below the diagonal: Plotly.NET.ChartMap_Geo uses a module listed above it, which is the healthy direction.
Plotly.NET.ChartMap_Mapbox uses Plotly.NET.StyleParam, so a change to Plotly.NET.StyleParam can break Plotly.NET.ChartMap_Mapbox, while a change to Plotly.NET.ChartMap_Mapbox can't break Plotly.NET.StyleParam.
Position
Below the diagonal: Plotly.NET.ChartMap_Mapbox uses a module listed above it, which is the healthy direction.
Plotly.NET.ChartMap_Mapbox uses Plotly.NET.LayoutObjects, so a change to Plotly.NET.LayoutObjects can break Plotly.NET.ChartMap_Mapbox, while a change to Plotly.NET.ChartMap_Mapbox can't break Plotly.NET.LayoutObjects.
Position
Below the diagonal: Plotly.NET.ChartMap_Mapbox uses a module listed above it, which is the healthy direction.
Plotly.NET.ChartMap_Mapbox uses Plotly.NET.TraceObjects, so a change to Plotly.NET.TraceObjects can break Plotly.NET.ChartMap_Mapbox, while a change to Plotly.NET.ChartMap_Mapbox can't break Plotly.NET.TraceObjects.
Position
Below the diagonal: Plotly.NET.ChartMap_Mapbox uses a module listed above it, which is the healthy direction.
Plotly.NET.ChartMap_Mapbox uses Plotly.NET, so a change to Plotly.NET can break Plotly.NET.ChartMap_Mapbox, while a change to Plotly.NET.ChartMap_Mapbox can't break Plotly.NET.
Position
Below the diagonal: Plotly.NET.ChartMap_Mapbox uses a module listed above it, which is the healthy direction.
Plotly.NET.ChartPolar_Bar uses Plotly.NET.StyleParam, so a change to Plotly.NET.StyleParam can break Plotly.NET.ChartPolar_Bar, while a change to Plotly.NET.ChartPolar_Bar can't break Plotly.NET.StyleParam.
Position
Below the diagonal: Plotly.NET.ChartPolar_Bar uses a module listed above it, which is the healthy direction.
Plotly.NET.ChartPolar_Bar uses Plotly.NET.TraceObjects, so a change to Plotly.NET.TraceObjects can break Plotly.NET.ChartPolar_Bar, while a change to Plotly.NET.ChartPolar_Bar can't break Plotly.NET.TraceObjects.
Position
Below the diagonal: Plotly.NET.ChartPolar_Bar uses a module listed above it, which is the healthy direction.
Plotly.NET.ChartPolar_Bar uses Plotly.NET, so a change to Plotly.NET can break Plotly.NET.ChartPolar_Bar, while a change to Plotly.NET.ChartPolar_Bar can't break Plotly.NET.
Position
Below the diagonal: Plotly.NET.ChartPolar_Bar uses a module listed above it, which is the healthy direction.
Plotly.NET.ChartPolar_Scatter uses Plotly.NET.StyleParam, so a change to Plotly.NET.StyleParam can break Plotly.NET.ChartPolar_Scatter, while a change to Plotly.NET.ChartPolar_Scatter can't break Plotly.NET.StyleParam.
Position
Below the diagonal: Plotly.NET.ChartPolar_Scatter uses a module listed above it, which is the healthy direction.
Plotly.NET.ChartPolar_Scatter uses Plotly.NET.TraceObjects, so a change to Plotly.NET.TraceObjects can break Plotly.NET.ChartPolar_Scatter, while a change to Plotly.NET.ChartPolar_Scatter can't break Plotly.NET.TraceObjects.
Position
Below the diagonal: Plotly.NET.ChartPolar_Scatter uses a module listed above it, which is the healthy direction.
Plotly.NET.ChartPolar_Scatter uses Plotly.NET, so a change to Plotly.NET can break Plotly.NET.ChartPolar_Scatter, while a change to Plotly.NET.ChartPolar_Scatter can't break Plotly.NET.
Position
Below the diagonal: Plotly.NET.ChartPolar_Scatter uses a module listed above it, which is the healthy direction.
Plotly.NET.ChartSmith_Scatter uses Plotly.NET.StyleParam, so a change to Plotly.NET.StyleParam can break Plotly.NET.ChartSmith_Scatter, while a change to Plotly.NET.ChartSmith_Scatter can't break Plotly.NET.StyleParam.
Position
Below the diagonal: Plotly.NET.ChartSmith_Scatter uses a module listed above it, which is the healthy direction.
Plotly.NET.ChartSmith_Scatter uses Plotly.NET.TraceObjects, so a change to Plotly.NET.TraceObjects can break Plotly.NET.ChartSmith_Scatter, while a change to Plotly.NET.ChartSmith_Scatter can't break Plotly.NET.TraceObjects.
Position
Below the diagonal: Plotly.NET.ChartSmith_Scatter uses a module listed above it, which is the healthy direction.
Plotly.NET.ChartSmith_Scatter uses Plotly.NET, so a change to Plotly.NET can break Plotly.NET.ChartSmith_Scatter, while a change to Plotly.NET.ChartSmith_Scatter can't break Plotly.NET.
Position
Below the diagonal: Plotly.NET.ChartSmith_Scatter uses a module listed above it, which is the healthy direction.
Plotly.NET.ChartTemplates uses Plotly.NET, so a change to Plotly.NET can break Plotly.NET.ChartTemplates, while a change to Plotly.NET.ChartTemplates can't break Plotly.NET.
Position
Below the diagonal: Plotly.NET.ChartTemplates uses a module listed above it, which is the healthy direction.
Plotly.NET.ChartTernary_Scatter uses Plotly.NET.StyleParam, so a change to Plotly.NET.StyleParam can break Plotly.NET.ChartTernary_Scatter, while a change to Plotly.NET.ChartTernary_Scatter can't break Plotly.NET.StyleParam.
Position
Below the diagonal: Plotly.NET.ChartTernary_Scatter uses a module listed above it, which is the healthy direction.
Plotly.NET.ChartTernary_Scatter uses Plotly.NET.TraceObjects, so a change to Plotly.NET.TraceObjects can break Plotly.NET.ChartTernary_Scatter, while a change to Plotly.NET.ChartTernary_Scatter can't break Plotly.NET.TraceObjects.
Position
Below the diagonal: Plotly.NET.ChartTernary_Scatter uses a module listed above it, which is the healthy direction.
Plotly.NET.ChartTernary_Scatter uses Plotly.NET, so a change to Plotly.NET can break Plotly.NET.ChartTernary_Scatter, while a change to Plotly.NET.ChartTernary_Scatter can't break Plotly.NET.
Position
Below the diagonal: Plotly.NET.ChartTernary_Scatter uses a module listed above it, which is the healthy direction.
Plotly.NET.ImageExport uses Plotly.NET, so a change to Plotly.NET can break Plotly.NET.ImageExport, while a change to Plotly.NET.ImageExport can't break Plotly.NET.
Position
Below the diagonal: Plotly.NET.ImageExport uses a module listed above it, which is the healthy direction.
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A05:2025 — Injection
12
High / Critical
A07:2025 — Authentication Failures
2
High / Critical
A02:2025 — Security Misconfiguration
2
Medium
Roadmap
Top priorities: Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them; Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it; Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose.
God Classes: FileTooLong: ChartMap/ChartMap_Mapbox.fs
How the grades work
Every finding carries one of four grades. Three say how serious it is. The fourth says this
survey could not settle it — and it is a grade, not a gap.
Critical — 13
A definite problem that already costs you something and drags the score down: a
missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here
tends to cause failures elsewhere.
Serious — 497
Likely wrong, but not failing yet. It degrades
the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to
carry for two years either.
Minor — 13
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 8
Something this survey could not settle
from the outside, and which could be critical or serious. Either a control was required and no
positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves
nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean
result. These are excluded from the score rather than awarded a pass, so the number on the cover neither
rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each
one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 40 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
Every figure here is one of two kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10.
What we checked — 40 dimensions across the health lenses
Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.
How to trust any code-health report — three questions
Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 516 of 523 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the test projects could not be restored because www.powershellgallery.com could not be reached (NU1301: Failed to retrieve information about 'Deedle' from remote source 'https://www.powershellgallery.com/api/v2/FindPackagesById()?id='Deedle'&semVerLevel=2.0.0'. The proxy tunnel request to proxy 'http://egress:3128/' failed with status code '403'.), so no test was built or run on this run. This is OURS — the scan's network path to the registry — and a TRANSIENT condition, NOT a statement about this repository's tests; coverage is excluded from the score rather than counted as a near-zero, and a re-run with the registry reachable measures it.
D10 Test Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 111 test(s) behind this row are the ones the C# collector could read, and this repository also carries at least 83 test source file(s) (.fs) that it cannot: it parses C# syntax and matches C# test attributes, so a vitest/jest/JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. The NuGet registry this repository's packages resolve from could not be reached on this run, so no outdated, vulnerable or deprecated package could be read. The tool said: NU1301: Failed to retrieve information about 'Microsoft.NET.Test.Sdk' from remote source 'https://www.powershellgallery.com/api/v2/FindPackagesById()?id='Microsoft.NET.Test.Sdk'&semVerLevel=2.0.0'. [Plotly.NET.sln] The proxy tunnel request to proxy 'http://egress:3128/' failed with status code '403'." [/tmp/codehealth-iso-54e2b09ddff54bdda7862ff…. This is OUR side and an ENVIRONMENT fault — the collector exists and ran — so the remedy is the scan's network path to www.powershellgallery.com, and a re-run with it reachable measures this repository.
D17 Explicit Debt — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The C# workspace loaded this repository's projects but reported a load failure, and the dead-code reference search is unreliable over a graph that did not load cleanly, so it was skipped. The other debt markers on this row were read; dead symbols were not, and their absence from the score is not a finding that the code has none. First load diagnostic: Failure: Cannot open project 'src/Plotly.NET/Plotly.NET.fsproj' because the file extension '.fsproj' is not associated with a language.
D17 Explicit Debt — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 0 deducted marker(s) and the 0.0/KLoC density on this row were taken over this repository's .NET projects ALONE: .fs (50,996 lines, 85% of production source) went unread, because every marker collector on this path is reached through a C# workspace. D17's marker collectors need a compiler we do not have for that language, so none of its nine marker kinds were read there. The debt in that source is UNMEASURED — its absence from the score above is a gap in this analyzer's language coverage, not a finding that the code carries none.
D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
D22 Internal API Consistency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. The loaded project set declares no packable project and no `.Contracts` project, so there is no intentionally-exposed surface for API consistency to be judged over.
D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
D30 Dependency Vulnerabilities — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Nuget: www.powershellgallery.com could not be reached (NU1301: Failed to retrieve information about 'Fake.Api.Github' from remote source 'https://www.powershellgallery.com/api/v2/FindPackagesById()?id='Fake.Api.Github'&semVerLevel=2.0.0'. The proxy tunnel request to proxy 'http://egress:3128/' failed with status code '403'.). The scanner exists and ran; what failed is the scan's network path to the registry, so nothing was read and nothing here is a statement about the repository. A re-run with the registry reachable measures it.
AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via REDACTED (docs/Dockerfile). docker build failed (exit 1) — -------------------- 2 | 3 | >>> RUN apt-get update \ 4 | >>> && apt-get -y upgrade \ 5 | >>> && apt-get -y install python3 python3-pip python3-dev ipython3 6 | -------------------- ERROR: failed to solve: process "/bin/sh -c apt-get update && apt-get -y upgrade && apt-get -y install python3 python3-pip python3-dev ipython3" did not complete successfully: exit code: 100; runtime evidence skipped.
IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
Package restore incomplete — third-party types were unresolved in part of the solution — NuGet restore did not complete for build/build.fsproj, tests/ConsoleApps/FSharpConsole/FSharpConsole.fsproj, tests/CoreTests/CoreTests/CoreTests.fsproj, tests/ExtensionLibsTests/ImageExportTests/ImageExportTests.fsproj, tests/Common/FSharpTestBase/FSharpTestBase.fsproj and 3 more, so those projects were analysed with framework references only: every check keyed on a third-party type saw an error type there and reported nothing. Findings on those projects are a lower bound; run `dotnet restore` on them and rescan.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
What it measures: How tangled the control flow is — methods with many branches are hard to test and change.
Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.
1 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was Chart.Grid at 18. A further 1 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being ColorKeyword.ofRGB at 139 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: src/Plotly.NET/CommonAbstractions/ColorKeyword.fs (ColorKeyword.ofRGB at 139). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
Bring the 1 body over 15 down to 15 or less in Cyclomatic Complexity — start with Chart.Grid (cyclomatic 18). — Refactoring it lifts Cyclomatic Complexity from 9.7 to about 10.0/10.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
Bring the 2 bodies over 15 down to 15 or less in Cognitive Complexity — start with Chart.Grid (cognitive 16), Chart.setAxis (cognitive 16). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cognitive Complexity from 9.8 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes8.0 / 10Strong✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 23 FileTooLong finding(s) in God Classes — start with StyleParams.fs, Chart.fs, Trace2D.fs. — One of this dimension's main actionable groups (23 warning-level).
Resolve the 4 TooManyMethods finding(s) in God Classes — start with Chart.fs, Scatter.cs, Layout.fs. — One of this dimension's main actionable groups (4 warning-level).
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Copy-pasted code that should be shared instead.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.
433 duplicated block group(s) detected. A further 29 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.
+ 219 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 28 Duplicated block (14 lines × 2) finding(s) in Code Duplication — start with ChartCarpet_Scatter.fs (4), Chart3D_VectorField.fs (3), ChartPolar_Scatter.fs (3). — One of this dimension's main actionable groups (28 warning-level).
Resolve the 17 Duplicated block (15 lines × 2) finding(s) in Code Duplication — start with Chart3D_Volume.fs (4), Chart2D_Finance.fs (2), ChartCarpet_Base.fs. — One of this dimension's main actionable groups (17 warning-level).
Resolve the 11 Duplicated block (17 lines × 2) finding(s) in Code Duplication — start with Chart2D_Finance.fs (3), Chart.fs, Chart2D_Heatmap.fs. — One of this dimension's main actionable groups (11 warning-level).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
D10 · Test Quality10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the tests truly assert behaviour rather than just running the code.
Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.
0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 111 tests. Measured on the C# suite only — at least 83 test source file(s) (.fs) went unread, so its test quality is unmeasured and is not in these counts.
✓ On the Gold path — maintain.
Detailed fixes: d10_recommendation.md.
Do you agree with this assessment?
D11 · Test Reliability10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the tests pass reliably, with no flakiness.
Method: Suite re-run N times within tiered wall-clock budgets (unit to e2e); tests failing non-deterministically across runs flagged; guarded tests retried when #if guards detected.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
0 of 256 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 26 direct `PackageReference`(s), and 208 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
What it measures: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
18 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is src/Plotly.NET/Traces/Trace2D.fs. Counted over 191 of the 244 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Off-boarding risk: anonymized user #1
✓ On the Gold path — maintain.
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
0 deducted debt markers + unmeasured dead symbols across 9165 LoC in the .NET projects (0.0/KLoC) → score 10.0. Dead code not measured: the solution did not load cleanly, so the reference search was skipped. Measured on the .NET source only: .fs (85% of production source) was not read, and carries at least 0 uncounted task marker(s) in 0 file(s).
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.
What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.
Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.
Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.
89 % of calls cross a namespace and 0 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
1 finding(s): 0 critical, 1 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
REDACTED
REDACTED
What to do
Resolve the 1 High secret finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
12 finding(s): 0 critical, 12 high, 0 medium, 0 low. 12 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens.
REDACTED
What to do
No action in Static Analysis (SAST) — all 12 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (12 issue-level, 0 of them charged here).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
1 of 191 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/Plotly.NET.ImageExport/AsyncHelper.fs. Counted over 191 of the 244 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Reported apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 17 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
Other · Architecture — Whether the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.
Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. Deterministic.
Do you agree with this assessment?
AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified
Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.
Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.
Other · Code Health — Unreviewed-generation residue: shipped members still throwing NotImplementedException, and placeholder string literals left in non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.
Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.
A shipped binding's whole body still raises a "not implemented" error — generated scaffolding that was never completed. Implement it or remove the dead surface. (×2) — src/Plotly.NET/CommonAbstractions/Colors.fs:136, src/Plotly.NET/CommonAbstractions/Colors.fs:193
What to do
Finish or delete NotImplementedException stubs and replace placeholder literals before shipping.
Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.
Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.
src/Plotly.NET.ImageExport/README.md names .NET 6, but the projects target .NET 8, 10. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — src/Plotly.NET.ImageExport/README.md:11
What to do
Reconcile the README with reality: src/Plotly.NET.ImageExport/README.md names .NET 6, but the projects target .NET 8, 10.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
No static application security testing detected. For this repository's stack, add `semgrep --config=auto` plus gitleaks for committed secrets (F# is not a CodeQL language and has no language-specific SAST engine) as a CI step. What was searched, so you can tell an absence from a miss: the 1 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:6
`build/build.fsproj` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — build/build.fsproj:22
What to do
Add a SAST step to CI running what this repository's stack ships: `semgrep --config=auto` plus gitleaks for committed secrets (F# is not a CodeQL language and has no language-specific SAST engine) — so a security regression fails the build instead of landing.
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
What to do
Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from each language's code model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
Other · Security — Cryptographic hygiene (weak hash/cipher, password key-derivation). This codebase has no web surface, so transport/header/cookie/CSRF controls are N/A and only crypto is scored. Markup this repository SHIPS is scored for third-party script integrity whether or not the repository serves it itself — a page handed to a consumer runs in that consumer's origin.
Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. On a repository with no .NET source it reads JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Elixir source itself (test, vendored, generated and minified paths not) for the arms that hold whether or not the code serves HTTP: a weak hash or cipher, key material fixed in the source, a TLS client that accepts any certificate, and (JavaScript/TypeScript, Ruby, Scala, Rust and Elixir) an obsolete TLS version; the server controls are not assessed there, and a Dart, Ruby, Scala, Rust or Elixir repository that serves no HTTP of its own is N/A on them. Deterministic.
`https://cdn.jsdelivr.net/npm/mathjax@3.2.0/es5/tex-svg.js` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. — src/Plotly.NET/Globals.fs:86
What to do
Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose.
Other · Code Health — Whether nullable reference types are enabled and not undermined by heavy `!` suppression.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
Do you agree with this assessment?
Reference — by lens
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 3 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
D36 Supply-chain Provenance & Signing — 1 observation(s) recorded · The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X10 Duplicated predicate — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 73 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC1 Text alternatives — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
AC2 Forms & labels — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
AC3 Page structure — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
AC4 Keyboard semantics — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
AC5 ARIA correctness — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
AC6 Visual & motion safety — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
AX1 Captive dependencies — no DI registrations detected
AX2 Stateful singletons — no singleton implementations detected
AX6 Interface segregation — no public interfaces
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — docker build failed (exit 1) — -------------------- 2 | 3 | >>> RUN apt-get update \ 4 | >>> && apt-get -y upgrade \ 5 | >>> && apt-get -y install python3 python3-pip python3-dev ipython3 6 | -------------------- ERROR: failed to solve: process "/bin/sh -c apt-get update && apt-get -y upgrade && apt-get -y install python3 python3-pip python3-dev ipython3" did not complete successfully: exit code: 100; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
C1 Data Protection — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
C2 Access Controls — No access-control surface detected in the analyzed source — no web/app surface to authorize (no HTTP API or web-UI project) and no authorization code at all (no [Authorize]/policies, no imperative guard methods). Access control is therefore N/A here — this is a library/CLI, which is authorized by its CALLER, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
C3 Audit Trail — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
C4 Data Retention — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
C5 Data-Subject Rights — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
D12 Dependency Hygiene — Dependency hygiene not measured — www.powershellgallery.com could not be reached
D18 Solution Shape — D18 scores the shape of a C#/VB .NET solution, but this repository's production source is mostly .fs, which the C#/VB workspace does not load — the projects that loaded are an immaterial minority, so solution shape was not assessed for this repository. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; F#, JavaScript not measured.
D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
D23 Boundary Type-Coupling — single shared-core project — no cross-context coupling to assess
D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .fs source were not judged.
D25 ADR Conformance — no ADRs to check
D30 Dependency Vulnerabilities — Not measured — a package registry could not be reached
D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
D8 Code Coverage — Coverage not measured — www.powershellgallery.com could not be reached
DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 9 value object(s); 5 domain event(s); its domain events are published by services or handlers — no domain entity raises one
ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
IC1 Incompleteness & stubs — IC1 reached only 15% of this repository's production lines — fsharp (50,996 lines), javascript (70 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
P2 Observability — This repo is a library, not a deployed service — it has no process to operate, so production observability (structured logging, tracing/metrics, health checks) is N/A. A library may log via an injected ILogger, but the absence of operational telemetry is not a defect here. If it grows a host (web API, worker), the dimension reactivates.
P7 Outbound HTTP resilience — not applicable — this isn't a service/API/worker
P8 Schema migrations — no EF Core usage detected
P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
PF1 Benchmark discipline — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X12 Unreachable branch — X12 reached only 15% of this repository's production lines — fsharp (50,996 lines), javascript (70 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X16 Unfloored truncation loop — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X2 Cancellation propagation — no async method does work a token could cancel
X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X21 Side-effecting pattern guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X27 Collection changed while being enumerated — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X3 Exception handling — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X32 Type resolved by simple name across every loaded assembly — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X4 Structured logging — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
Duplicated block (14 lines × 2) src/Plotly.NET/ChartAPI/Chart.fs:3397— src/Plotly.NET/ChartAPI/Chart.fs:3397-3410 | src/Plotly.NET/ChartAPI/Chart.fs:3417-3430 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart.fs:3397` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:70— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:70-83 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:547-565 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:70` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (14 lines × 2) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:162— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:162-175 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:616-629 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:162` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:80— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:80-93 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:380-393 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Funnel.fs:439— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Funnel.fs:439-452 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Funnel.fs:544-557 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Funnel.fs:439` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Histogram.fs:694— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Histogram.fs:694-707 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Histogram.fs:944-957 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:87— src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:87-100 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:388-401 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:115— src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:115-128 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:416-429 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:115` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:150— src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:150-163 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:451-464 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:96— src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:96-109 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:1140-1153 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:96` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:110— src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:110-123 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:210-223 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:110` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:196— src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:196-209 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:1217-1230 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:196` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:866— src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:866-879 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:952-965 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:866` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Hierarchy.fs:366— src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Hierarchy.fs:366-379 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Hierarchy.fs:747-760 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Relations.fs:128— src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Relations.fs:128-141 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Relations.fs:183-196 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Relations.fs:128` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Density.fs:78— src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Density.fs:78-91 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Density.fs:153-166 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Density.fs:78` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:64— src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:64-77 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:124-137 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:64` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:334— src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:334-347 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:1056-1069 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:105— src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:105-118 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:605-618 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:105` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:674— src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:674-687 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:955-968 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:674` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:1138— src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:1138-1151 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:1198-1211 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:1138` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:478— src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:478-491 | src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:998-1011 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) src/Plotly.NET/Layout/ObjectAbstractions/Common/Selection.fs:27— src/Plotly.NET/Layout/ObjectAbstractions/Common/Selection.fs:27-40 | src/Plotly.NET/Layout/ObjectAbstractions/Common/Selection.fs:73-86 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) src/Plotly.NET/Layout/ObjectAbstractions/Smith/ImaginaryAxis.fs:69— src/Plotly.NET/Layout/ObjectAbstractions/Smith/ImaginaryAxis.fs:69-82 | src/Plotly.NET/Layout/ObjectAbstractions/Smith/RealAxis.fs:73-86 — before extracting anything, compare `src/Plotly.NET/Layout/ObjectAbstractions/Smith/ImaginaryAxis.fs` and `src/Plotly.NET/Layout/ObjectAbstractions/Smith/RealAxis.fs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 65 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (14 lines × 2) src/Plotly.NET/Traces/ObjectAbstractions/Table.fs:27— src/Plotly.NET/Traces/ObjectAbstractions/Table.fs:27-40 | src/Plotly.NET/Traces/ObjectAbstractions/Table.fs:59-72 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
FileTooLong: CommonAbstractions/StyleParams.fs src/Plotly.NET/CommonAbstractions/StyleParams.fs— FileTooLong — 3129 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 2629 over it, 6.26× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: ChartAPI/Chart.fs src/Plotly.NET/ChartAPI/Chart.fs— FileTooLong — 2066 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1566 over it, 4.13× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Traces/Trace2D.fs src/Plotly.NET/Traces/Trace2D.fs— FileTooLong — 1857 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1357 over it, 3.71× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Chart2D/Chart2D_Scatter.fs src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs— FileTooLong — 1482 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 982 over it, 2.96× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: ChartMap/ChartMap_Geo.fs src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs— FileTooLong — 968 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 468 over it, 1.94× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: ChartCarpet/ChartCarpet_Scatter.fs src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs— FileTooLong — 871 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 371 over it, 1.74× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: ChartPolar/ChartPolar_Scatter.fs src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs— FileTooLong — 851 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 351 over it, 1.70× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Traces/Trace3D.fs src/Plotly.NET/Traces/Trace3D.fs— FileTooLong — 823 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 323 over it, 1.65× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Chart3D/Chart3D_Scatter.fs src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs— FileTooLong — 777 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 277 over it, 1.55× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Common/LinearAxis.fs src/Plotly.NET/Layout/ObjectAbstractions/Common/LinearAxis.fs— FileTooLong — 730 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 230 over it, 1.46× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Traces/TraceDomain.fs src/Plotly.NET/Traces/TraceDomain.fs— FileTooLong — 719 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 219 over it, 1.44× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: ChartMap/ChartMap_Mapbox.fs src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs— FileTooLong — 703 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 203 over it, 1.41× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: ChartTernary/ChartTernary_Scatter.fs src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs— FileTooLong — 674 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 174 over it, 1.35× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: ChartSmith/ChartSmith_Scatter.fs src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs— FileTooLong — 665 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 165 over it, 1.33× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Chart2D/Chart2D_Area.fs src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs— FileTooLong — 637 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 137 over it, 1.27× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Chart2D/Chart2D_Bar.fs src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs— FileTooLong — 616 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 116 over it, 1.23× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Chart2D/Chart2D_Histogram.fs src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Histogram.fs— FileTooLong — 607 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 107 over it, 1.21× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Layout/Layout.fs src/Plotly.NET/Layout/Layout.fs— FileTooLong — 602 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 102 over it, 1.20× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: CommonAbstractions/ColorKeyword.fs src/Plotly.NET/CommonAbstractions/ColorKeyword.fs— FileTooLong — 589 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 89 over it, 1.18× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: ChartDomain/ChartDomain_Pie.fs src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Pie.fs— FileTooLong — 551 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 51 over it, 1.10× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Chart2D/Chart2D_Distribution.fs src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Distribution.fs— FileTooLong — 533 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 33 over it, 1.07× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Templates/ChartTemplates.fs src/Plotly.NET/Templates/ChartTemplates.fs— FileTooLong — 508 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 8 over it, 1.02× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Chart2D/Chart2D_Heatmap.fs src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Heatmap.fs— FileTooLong — 506 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 6 over it, 1.01× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
Duplicated block (15 lines × 2) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:153— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:153-167 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:453-467 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15 lines × 2) src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Volume.fs:51— src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Volume.fs:51-65 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Volume.fs:213-227 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Volume.fs:51` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Volume.fs:88— src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Volume.fs:88-102 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Volume.fs:249-263 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15 lines × 2) src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Volume.fs:119— src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Volume.fs:119-133 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Volume.fs:279-293 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Volume.fs:119` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Volume.fs:156— src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Volume.fs:156-170 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Volume.fs:315-329 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15 lines × 2) src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Base.fs:66— src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Base.fs:66-80 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Base.fs:129-143 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Base.fs:66` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Icicle.fs:147— src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Icicle.fs:147-161 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Icicle.fs:291-305 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Icicle.fs:147` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Density.fs:197— src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Density.fs:197-211 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Density.fs:270-284 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Density.fs:197` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:119— src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:119-133 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:220-234 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:119` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:109— src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:109-123 | src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:211-225 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:109` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) src/Plotly.NET/ChartAPI/GenericChart.fs:289— src/Plotly.NET/ChartAPI/GenericChart.fs:289-303 | src/Plotly.NET/ChartAPI/GenericChart.fs:342-356 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15 lines × 2) src/Plotly.NET/Layout/ObjectAbstractions/Common/Minor.fs:29— src/Plotly.NET/Layout/ObjectAbstractions/Common/Minor.fs:29-43 | src/Plotly.NET/Layout/ObjectAbstractions/Common/Minor.fs:78-92 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15 lines × 2) src/Plotly.NET/Layout/ObjectAbstractions/Smith/ImaginaryAxis.fs:152— src/Plotly.NET/Layout/ObjectAbstractions/Smith/ImaginaryAxis.fs:152-166 | src/Plotly.NET/Layout/ObjectAbstractions/Smith/RealAxis.fs:161-175 — before extracting anything, compare `src/Plotly.NET/Layout/ObjectAbstractions/Smith/ImaginaryAxis.fs` and `src/Plotly.NET/Layout/ObjectAbstractions/Smith/RealAxis.fs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 65 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (15 lines × 2) src/Plotly.NET/Traces/Trace2D.fs:1354— src/Plotly.NET/Traces/Trace2D.fs:1354-1368 | src/Plotly.NET/Traces/Trace2D.fs:1564-1578 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15 lines × 2) src/Plotly.NET/Traces/TraceDomain.fs:100— src/Plotly.NET/Traces/TraceDomain.fs:100-114 | src/Plotly.NET/Traces/TraceDomain.fs:240-254 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15 lines × 2) src/Plotly.NET/Traces/TraceMapbox.fs:290— src/Plotly.NET/Traces/TraceMapbox.fs:290-304 | src/Plotly.NET/Traces/TraceMapbox.fs:423-437 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15 lines × 2) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:296— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:296-310 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:599-613 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (17 lines × 2) src/Plotly.NET/ChartAPI/Chart.fs:1695— src/Plotly.NET/ChartAPI/Chart.fs:1695-1711 | src/Plotly.NET/ChartAPI/Chart.fs:1751-1767 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart.fs:1695` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17 lines × 2) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:43— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:43-59 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:343-359 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:43` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17 lines × 2) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:86— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:86-102 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:237-253 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:86` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17 lines × 2) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:386— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:386-402 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:537-553 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:386` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17 lines × 2) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Heatmap.fs:298— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Heatmap.fs:298-314 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Heatmap.fs:402-418 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (17 lines × 2) src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Hierarchy.fs:740— src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Hierarchy.fs:740-756 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Icicle.fs:396-412 — before extracting anything, compare `src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Hierarchy.fs` and `src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Icicle.fs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 87 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (17 lines × 2) src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Pie.fs:308— src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Pie.fs:308-324 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Pie.fs:568-584 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (17 lines × 2) src/Plotly.NET/Layout/ObjectAbstractions/Common/LayoutImage.fs:13— src/Plotly.NET/Layout/ObjectAbstractions/Common/LayoutImage.fs:13-29 | src/Plotly.NET/Layout/ObjectAbstractions/Common/LayoutImage.fs:50-66 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (17 lines × 2) src/Plotly.NET/Traces/ObjectAbstractions/Error.fs:32— src/Plotly.NET/Traces/ObjectAbstractions/Error.fs:32-48 | src/Plotly.NET/Traces/ObjectAbstractions/Error.fs:87-103 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (17 lines × 2) src/Plotly.NET/Traces/TraceGeo.fs:142— src/Plotly.NET/Traces/TraceGeo.fs:142-158 | src/Plotly.NET/Traces/TraceMapbox.fs:279-295 — before extracting anything, compare `src/Plotly.NET/Traces/TraceGeo.fs` and `src/Plotly.NET/Traces/TraceMapbox.fs` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 175 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (17 lines × 2) src/Plotly.NET/Traces/TraceMapbox.fs:246— src/Plotly.NET/Traces/TraceMapbox.fs:246-262 | src/Plotly.NET/Traces/TraceMapbox.fs:379-395 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:201— src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:201-211 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:504-514 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:201` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:271— src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:271-281 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:580-590 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:271` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Hierarchy.fs:186— src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Hierarchy.fs:186-196 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Hierarchy.fs:562-572 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Hierarchy.fs:186` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:337— src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:337-347 | src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:781-791 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) src/Plotly.NET/Layout/ObjectAbstractions/Smith/ImaginaryAxis.fs:139— src/Plotly.NET/Layout/ObjectAbstractions/Smith/ImaginaryAxis.fs:139-149 | src/Plotly.NET/Layout/ObjectAbstractions/Smith/RealAxis.fs:148-158 — before extracting anything, compare `src/Plotly.NET/Layout/ObjectAbstractions/Smith/ImaginaryAxis.fs` and `src/Plotly.NET/Layout/ObjectAbstractions/Smith/RealAxis.fs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 65 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/Layout/ObjectAbstractions/Smith/ImaginaryAxis.fs:139` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) src/Plotly.NET/Traces/ObjectAbstractions/Pattern.fs:25— src/Plotly.NET/Traces/ObjectAbstractions/Pattern.fs:25-35 | src/Plotly.NET/Traces/ObjectAbstractions/Pattern.fs:62-72 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) src/Plotly.NET/Traces/Trace2D.fs:2109— src/Plotly.NET/Traces/Trace2D.fs:2109-2119 | src/Plotly.NET/Traces/Trace2D.fs:2431-2441 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) src/Plotly.NET/Traces/Trace2D.fs:2176— src/Plotly.NET/Traces/Trace2D.fs:2176-2186 | src/Plotly.NET/Traces/Trace2D.fs:2500-2510 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) src/Plotly.NET/Traces/TraceGeo.fs:116— src/Plotly.NET/Traces/TraceGeo.fs:116-126 | src/Plotly.NET/Traces/TraceMapbox.fs:388-398 — before extracting anything, compare `src/Plotly.NET/Traces/TraceGeo.fs` and `src/Plotly.NET/Traces/TraceMapbox.fs` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 175 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 2) src/Plotly.NET/Traces/TraceMapbox.fs:139— src/Plotly.NET/Traces/TraceMapbox.fs:139-150 | src/Plotly.NET/Traces/TraceMapbox.fs:271-281 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/Traces/TraceMapbox.fs:139` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Distribution.fs:55— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Distribution.fs:55-63 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Distribution.fs:450-458 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Distribution.fs:88— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Distribution.fs:88-96 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Distribution.fs:494-502 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Hierarchy.fs:317— src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Hierarchy.fs:317-325 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Hierarchy.fs:695-703 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Hierarchy.fs:317` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) src/Plotly.NET/Traces/Trace2D.fs:426— src/Plotly.NET/Traces/Trace2D.fs:426-434 | src/Plotly.NET/Traces/TracePolar.fs:253-261 — before extracting anything, compare `src/Plotly.NET/Traces/Trace2D.fs` and `src/Plotly.NET/Traces/TracePolar.fs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 105 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 2) src/Plotly.NET/Traces/Trace2D.fs:1966— src/Plotly.NET/Traces/Trace2D.fs:1966-1974 | src/Plotly.NET/Traces/Trace2D.fs:2499-2507 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) src/Plotly.NET/Traces/TraceGeo.fs:107— src/Plotly.NET/Traces/TraceGeo.fs:107-115 | src/Plotly.NET/Traces/TraceGeo.fs:251-259 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) src/Plotly.NET/Traces/TraceGeo.fs:281— src/Plotly.NET/Traces/TraceGeo.fs:281-289 | src/Plotly.NET/Traces/TraceMapbox.fs:148-156 — before extracting anything, compare `src/Plotly.NET/Traces/TraceGeo.fs` and `src/Plotly.NET/Traces/TraceMapbox.fs` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 175 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 2) src/Plotly.NET/Traces/TracePolar.fs:100— src/Plotly.NET/Traces/TracePolar.fs:100-108 | src/Plotly.NET/Traces/TracePolar.fs:244-252 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) src/Plotly.NET/Traces/TracePolar.fs:155— src/Plotly.NET/Traces/TracePolar.fs:155-163 | src/Plotly.NET/Traces/TracePolar.fs:294-302 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) src/Plotly.NET/Traces/TracePolar.fs:168— src/Plotly.NET/Traces/TracePolar.fs:168-176 | src/Plotly.NET/Traces/TracePolar.fs:309-317 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Plotly.NET/Traces/TracePolar.fs:166` calls `withOptionalSingleOrMultiPropertyBy`, `withOptionalSingleOrMultiProperty` and `src/Plotly.NET/Traces/TracePolar.fs:308` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (12 lines × 2) src/Plotly.NET/ChartAPI/Chart.fs:1245— src/Plotly.NET/ChartAPI/Chart.fs:1245-1256 | src/Plotly.NET/ChartAPI/Chart.fs:1507-1518 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) src/Plotly.NET/ChartAPI/Chart.fs:1595— src/Plotly.NET/ChartAPI/Chart.fs:1595-1606 | src/Plotly.NET/Layout/ObjectAbstractions/3D/Scene.fs:45-56 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Plotly.NET/ChartAPI/Chart.fs:1609` calls `withScene` and `src/Plotly.NET/Layout/ObjectAbstractions/3D/Scene.fs:74` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (12 lines × 2) src/Plotly.NET/ChartAPI/Chart.fs:2507— src/Plotly.NET/ChartAPI/Chart.fs:2507-2518 | src/Plotly.NET/Layout/ObjectAbstractions/Common/LayoutGrid.fs:43-54 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (12 lines × 2) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:278— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:278-289 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:578-589 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:278` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Heatmap.fs:731— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Heatmap.fs:731-742 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Contour.fs:155-166 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (12 lines × 2) src/Plotly.NET/Traces/ObjectAbstractions/Contours.fs:106— src/Plotly.NET/Traces/ObjectAbstractions/Contours.fs:106-117 | src/Plotly.NET/Traces/ObjectAbstractions/Contours.fs:150-161 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/Traces/ObjectAbstractions/Contours.fs:106` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) src/Plotly.NET/Traces/Trace3D.fs:176— src/Plotly.NET/Traces/Trace3D.fs:176-187 | src/Plotly.NET/Traces/Trace3D.fs:339-350 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) src/Plotly.NET/Traces/TraceGeo.fs:164— src/Plotly.NET/Traces/TraceGeo.fs:164-175 | src/Plotly.NET/Traces/TraceMapbox.fs:301-312 — before extracting anything, compare `src/Plotly.NET/Traces/TraceGeo.fs` and `src/Plotly.NET/Traces/TraceMapbox.fs` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 175 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 2) src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:284— src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:284-295 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:593-604 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:284` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (20 lines × 2) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Histogram.fs:698— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Histogram.fs:698-717 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Histogram.fs:839-858 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Histogram.fs:698` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (20 lines × 2) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1562— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1562-1581 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1680-1699 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1562` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (20 lines × 2) src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:222— src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:222-241 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:297-316 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:222` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (20 lines × 2) src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:528— src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:528-547 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:606-625 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:528` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (20 lines × 2) src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:43— src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:43-62 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:103-122 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:43` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (20 lines × 2) src/Plotly.NET/Traces/ObjectAbstractions/Sankey.fs:13— src/Plotly.NET/Traces/ObjectAbstractions/Sankey.fs:13-32 | src/Plotly.NET/Traces/ObjectAbstractions/Sankey.fs:57-76 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (20 lines × 2) src/Plotly.NET/Traces/ObjectAbstractions/Sankey.fs:144— src/Plotly.NET/Traces/ObjectAbstractions/Sankey.fs:144-163 | src/Plotly.NET/Traces/ObjectAbstractions/Sankey.fs:188-207 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (20 lines × 2) src/Plotly.NET.CSharp/ChartAPI/Chart2D/Candlestick.cs:62— src/Plotly.NET.CSharp/ChartAPI/Chart2D/Candlestick.cs:62-81 | src/Plotly.NET.CSharp/ChartAPI/Chart2D/OHLC.cs:62-81 — before extracting anything, compare `src/Plotly.NET.CSharp/ChartAPI/Chart2D/Candlestick.cs` and `src/Plotly.NET.CSharp/ChartAPI/Chart2D/OHLC.cs` as WHOLE FILES: 84% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET.CSharp/ChartAPI/Chart2D/Candlestick.cs:62` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:131— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:131-146 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:431-446 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:131` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:196— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:196-211 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:496-511 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:196` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Contour.fs:106— src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Contour.fs:106-121 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Contour.fs:208-223 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Contour.fs:106` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Pie.fs:114— src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Pie.fs:114-129 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Pie.fs:223-238 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Pie.fs:114` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) src/Plotly.NET/CommonAbstractions/Title.fs:26— src/Plotly.NET/CommonAbstractions/Title.fs:26-41 | src/Plotly.NET/CommonAbstractions/Title.fs:74-89 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (16 lines × 2) src/Plotly.NET/Layout/ObjectAbstractions/Common/NewShape.fs:61— src/Plotly.NET/Layout/ObjectAbstractions/Common/NewShape.fs:61-76 | src/Plotly.NET/Layout/ObjectAbstractions/Common/NewShape.fs:113-128 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (16 lines × 2) src/Plotly.NET/Traces/Trace2D.fs:1267— src/Plotly.NET/Traces/Trace2D.fs:1267-1282 | src/Plotly.NET/Traces/Trace2D.fs:1502-1517 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (16 lines × 2) src/Plotly.NET/Traces/TraceMapbox.fs:119— src/Plotly.NET/Traces/TraceMapbox.fs:119-134 | src/Plotly.NET/Traces/TraceTernary.fs:93-108 — before extracting anything, compare `src/Plotly.NET/Traces/TraceMapbox.fs` and `src/Plotly.NET/Traces/TraceTernary.fs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 112 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 2) src/Plotly.NET/ChartAPI/Chart.fs:1203— src/Plotly.NET/ChartAPI/Chart.fs:1203-1215 | src/Plotly.NET/ChartAPI/Chart.fs:1466-1478 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:158— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:158-170 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:301-313 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:232— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:232-244 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:532-544 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:458— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:458-470 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:604-616 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:111— src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:111-123 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:911-923 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:111` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:230— src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:230-242 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:989-1001 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:230` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) src/Plotly.NET/Layout/ObjectAbstractions/Common/RangeSelector.fs:14— src/Plotly.NET/Layout/ObjectAbstractions/Common/RangeSelector.fs:14-26 | src/Plotly.NET/Layout/ObjectAbstractions/Common/RangeSelector.fs:43-55 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) src/Plotly.NET/Traces/TraceCarpet.fs:199— src/Plotly.NET/Traces/TraceCarpet.fs:199-211 | src/Plotly.NET/Traces/TraceTernary.fs:71-83 — before extracting anything, compare `src/Plotly.NET/Traces/TraceCarpet.fs` and `src/Plotly.NET/Traces/TraceTernary.fs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 89 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 3) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:495— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:495-506 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1250-1261 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:906-917 — before extracting anything, compare `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs` and `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 122 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:495` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 3) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:801— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:801-813 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:917-928 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:661-672 — `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs` and `src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 14 separate duplicated blocks between them, totalling at least 170 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:801` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 3) src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Hierarchy.fs:365— src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Hierarchy.fs:365-376 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Hierarchy.fs:746-757 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Icicle.fs:402-413 — before extracting anything, compare `src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Hierarchy.fs` and `src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Icicle.fs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 87 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 3) src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:404— src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:404-415 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:485-496 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:538-549 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:404` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 3) src/Plotly.NET/Traces/TraceDomain.fs:97— src/Plotly.NET/Traces/TraceDomain.fs:97-108 | src/Plotly.NET/Traces/TraceDomain.fs:237-248 | src/Plotly.NET/Traces/TraceDomain.fs:511-522 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/Traces/TraceDomain.fs:97` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 3) src/Plotly.NET/Traces/TraceDomain.fs:428— src/Plotly.NET/Traces/TraceDomain.fs:428-439 | src/Plotly.NET/Traces/TraceDomain.fs:571-582 | src/Plotly.NET/Traces/TraceDomain.fs:1062-1073 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Plotly.NET/Traces/TraceDomain.fs:583` calls `withOptionalSingleOrMultiPropertyBy` and `src/Plotly.NET/Traces/TraceDomain.fs:440` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (12 lines × 3) src/Plotly.NET/Traces/TracePolar.fs:126— src/Plotly.NET/Traces/TracePolar.fs:126-137 | src/Plotly.NET/Traces/TraceSmith.fs:99-110 | src/Plotly.NET/Traces/TraceTernary.fs:102-113 — before extracting anything, compare `src/Plotly.NET/Traces/TracePolar.fs` and `src/Plotly.NET/Traces/TraceSmith.fs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 92 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 3) src/Plotly.NET/Traces/TracePolar.fs:176— src/Plotly.NET/Traces/TracePolar.fs:176-187 | src/Plotly.NET/Traces/TraceSmith.fs:142-153 | src/Plotly.NET/Traces/TraceTernary.fs:149-160 — before extracting anything, compare `src/Plotly.NET/Traces/TracePolar.fs` and `src/Plotly.NET/Traces/TraceSmith.fs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 92 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (27 lines × 2) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:410— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:410-436 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:524-550 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:410` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (27 lines × 2) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:53— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:53-79 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:205-231 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:53` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (27 lines × 2) src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Density.fs:50— src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Density.fs:50-76 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Density.fs:125-151 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Density.fs:50` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (27 lines × 2) src/Plotly.NET/Layout/ObjectAbstractions/Common/LinearAxis.fs:224— src/Plotly.NET/Layout/ObjectAbstractions/Common/LinearAxis.fs:224-250 | src/Plotly.NET/Layout/ObjectAbstractions/Common/LinearAxis.fs:476-502 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (27 lines × 2) src/Plotly.NET/Layout/ObjectAbstractions/Polar/AngularAxis.fs:126— src/Plotly.NET/Layout/ObjectAbstractions/Polar/AngularAxis.fs:126-152 | src/Plotly.NET/Layout/ObjectAbstractions/Polar/RadialAxis.fs:142-168 — before extracting anything, compare `src/Plotly.NET/Layout/ObjectAbstractions/Polar/AngularAxis.fs` and `src/Plotly.NET/Layout/ObjectAbstractions/Polar/RadialAxis.fs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 88 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (27 lines × 2) src/Plotly.NET/Layout/ObjectAbstractions/Polar/AngularAxis.fs:272— src/Plotly.NET/Layout/ObjectAbstractions/Polar/AngularAxis.fs:272-298 | src/Plotly.NET/Layout/ObjectAbstractions/Polar/RadialAxis.fs:305-331 — before extracting anything, compare `src/Plotly.NET/Layout/ObjectAbstractions/Polar/AngularAxis.fs` and `src/Plotly.NET/Layout/ObjectAbstractions/Polar/RadialAxis.fs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 88 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (27 lines × 2) src/Plotly.NET.CSharp/ChartAPI/Chart2D/Funnel.cs:76— src/Plotly.NET.CSharp/ChartAPI/Chart2D/Funnel.cs:76-102 | src/Plotly.NET.CSharp/ChartAPI/Chart2D/StackedFunnel.cs:77-103 — before extracting anything, compare `src/Plotly.NET.CSharp/ChartAPI/Chart2D/Funnel.cs` and `src/Plotly.NET.CSharp/ChartAPI/Chart2D/StackedFunnel.cs` as WHOLE FILES: 96% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET.CSharp/ChartAPI/Chart2D/Funnel.cs:76` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (23 lines × 2) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:365— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:365-387 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:820-842 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:365` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (23 lines × 2) src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:98— src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:98-120 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:217-239 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:98` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (23 lines × 2) src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:64— src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:64-86 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:127-149 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:64` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (23 lines × 2) src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:365— src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:365-387 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:428-450 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:365` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (23 lines × 2) src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:901— src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:901-923 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:971-993 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:901` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (23 lines × 2) src/Plotly.NET/Layout/ObjectAbstractions/Smith/RealAxis.fs:48— src/Plotly.NET/Layout/ObjectAbstractions/Smith/RealAxis.fs:48-70 | src/Plotly.NET/Layout/ObjectAbstractions/Smith/RealAxis.fs:136-158 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/Layout/ObjectAbstractions/Smith/RealAxis.fs:48` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (23 lines × 2) src/Plotly.NET/Traces/TraceGeo.fs:89— src/Plotly.NET/Traces/TraceGeo.fs:89-111 | src/Plotly.NET/Traces/TraceMapbox.fs:228-250 — before extracting anything, compare `src/Plotly.NET/Traces/TraceGeo.fs` and `src/Plotly.NET/Traces/TraceMapbox.fs` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 175 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/Traces/TraceGeo.fs:89` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (18 lines × 2) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Funnel.fs:72— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Funnel.fs:72-89 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Funnel.fs:177-194 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Funnel.fs:72` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (18 lines × 2) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Splom.fs:143— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Splom.fs:143-160 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Splom.fs:212-229 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Splom.fs:143` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (18 lines × 2) src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Volume.fs:254— src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Volume.fs:254-271 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Volume.fs:320-337 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Volume.fs:254` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (18 lines × 2) src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Hierarchy.fs:130— src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Hierarchy.fs:130-147 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Hierarchy.fs:258-275 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Hierarchy.fs:130` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (18 lines × 2) src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Hierarchy.fs:505— src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Hierarchy.fs:505-522 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Hierarchy.fs:635-652 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Hierarchy.fs:505` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (18 lines × 2) src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:360— src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:360-377 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:1106-1123 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:360` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (18 lines × 2) src/Plotly.NET/Layout/ObjectAbstractions/Common/UpdateMenu.fs:63— src/Plotly.NET/Layout/ObjectAbstractions/Common/UpdateMenu.fs:63-80 | src/Plotly.NET/Layout/ObjectAbstractions/Common/UpdateMenu.fs:103-120 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (25 lines × 2) src/Plotly.NET/ChartAPI/Chart.fs:2622— src/Plotly.NET/ChartAPI/Chart.fs:2622-2646 | src/Plotly.NET/Layout/ObjectAbstractions/Common/Legend.fs:70-94 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Plotly.NET/ChartAPI/Chart.fs:2649` calls `withLegend` and `src/Plotly.NET/Layout/ObjectAbstractions/Common/Legend.fs:125` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (25 lines × 2) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Distribution.fs:59— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Distribution.fs:59-83 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Distribution.fs:348-372 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Distribution.fs:59` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (25 lines × 2) src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Surface.fs:195— src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Surface.fs:195-219 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Surface.fs:263-287 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Surface.fs:195` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (25 lines × 2) src/Plotly.NET/Layout/ObjectAbstractions/Common/Slider/Slider.fs:65— src/Plotly.NET/Layout/ObjectAbstractions/Common/Slider/Slider.fs:65-89 | src/Plotly.NET/Layout/ObjectAbstractions/Common/Slider/Slider.fs:118-142 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (25 lines × 2) src/Plotly.NET/Traces/Trace2D.fs:1754— src/Plotly.NET/Traces/Trace2D.fs:1754-1778 | src/Plotly.NET/Traces/Trace2D.fs:1941-1965 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (25 lines × 2) src/Plotly.NET/Traces/Trace2D.fs:2084— src/Plotly.NET/Traces/Trace2D.fs:2084-2108 | src/Plotly.NET/Traces/Trace2D.fs:2405-2429 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 4) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:50— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:50-63 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:137-150 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:202-215 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:280-293 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:50` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 4) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:350— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:350-363 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:437-450 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:502-515 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:580-593 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:350` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 4) src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:898— src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:898-911 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:976-989 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:1121-1134 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:1181-1194 — `src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs` and `src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 13 separate duplicated blocks between them, totalling at least 180 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:896` calls `showText` and `src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:1179` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (14 lines × 4) src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:59— src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:59-72 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:122-135 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:204-217 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:274-287 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:59` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 4) src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:360— src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:360-373 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:423-436 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:507-520 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:583-596 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:360` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 4) src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:95— src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:95-108 | src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:197-210 | src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:827-840 | src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:906-919 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:95` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 3) src/Plotly.NET/ChartAPI/Chart.fs:3400— src/Plotly.NET/ChartAPI/Chart.fs:3400-3412 | src/Plotly.NET/ChartAPI/Chart.fs:3420-3432 | src/Plotly.NET/ChartAPI/Chart.fs:3486-3498 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (13 lines × 3) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Distribution.fs:193— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Distribution.fs:193-205 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Distribution.fs:282-294 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Distribution.fs:379-391 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (13 lines × 3) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Funnel.fs:395— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Funnel.fs:395-407 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Funnel.fs:500-512 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Funnel.fs:604-616 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Funnel.fs:395` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 3) src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:392— src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:392-407 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:1139-1154 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:1199-1211 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:392` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (13 lines × 3) src/Plotly.NET/Traces/TraceDomain.fs:376— src/Plotly.NET/Traces/TraceDomain.fs:376-388 | src/Plotly.NET/Traces/TraceDomain.fs:519-531 | src/Plotly.NET/Traces/TraceDomain.fs:1012-1024 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
TooManyMethods: Chart src/Plotly.NET/ChartAPI/Chart.fs:14— TooManyMethods — 109 methods. The bar is 30 methods; this is 79 over it, 3.63× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Chart src/Plotly.NET.CSharp/ChartAPI/Chart2D/Scatter.cs— TooManyMethods — 4967 significant lines (blank, comment-only and punctuation-only lines excluded), 98 methods, declared across 86 files: Chart2D/Bar.cs (2), Chart2D/Column.cs (2), Chart2D/Heatmap.cs (2), Chart2D/Histogram2D.cs (2), +82 more file(s). The bar is 30 methods; this is 68 over it, 3.27× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
TooManyMethods: Layout src/Plotly.NET/Layout/Layout.fs:10— TooManyMethods — 54 methods. The bar is 30 methods; this is 24 over it, 1.80× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: GenericChart src/Plotly.NET/ChartAPI/GenericChart.fs:62— TooManyMethods — 33 methods. The bar is 30 methods; this is 3 over it, 1.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Duplicated block (30 lines × 2) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Funnel.fs:399— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Funnel.fs:399-428 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Funnel.fs:504-533 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Funnel.fs:399` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (30 lines × 2) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1958— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1958-1987 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:2149-2178 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1958` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (30 lines × 2) src/Plotly.NET/Layout/ObjectAbstractions/Common/Shape.fs:76— src/Plotly.NET/Layout/ObjectAbstractions/Common/Shape.fs:76-105 | src/Plotly.NET/Layout/ObjectAbstractions/Common/Shape.fs:170-199 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (30 lines × 2) src/Plotly.NET/Layout/ObjectAbstractions/Polar/RadialAxis.fs:67— src/Plotly.NET/Layout/ObjectAbstractions/Polar/RadialAxis.fs:67-96 | src/Plotly.NET/Layout/ObjectAbstractions/Polar/RadialAxis.fs:230-259 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/Layout/ObjectAbstractions/Polar/RadialAxis.fs:67` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (21 lines × 2) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Funnel.fs:620— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Funnel.fs:620-640 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Funnel.fs:706-726 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Funnel.fs:620` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (21 lines × 2) src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:70— src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:70-90 | src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:172-192 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:70` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (21 lines × 2) src/Plotly.NET/Layout/ObjectAbstractions/Common/LinearAxis.fs:252— src/Plotly.NET/Layout/ObjectAbstractions/Common/LinearAxis.fs:252-272 | src/Plotly.NET/Layout/ObjectAbstractions/Common/LinearAxis.fs:503-523 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (21 lines × 2) src/Plotly.NET/Layout/ObjectAbstractions/Smith/ImaginaryAxis.fs:46— src/Plotly.NET/Layout/ObjectAbstractions/Smith/ImaginaryAxis.fs:46-66 | src/Plotly.NET/Layout/ObjectAbstractions/Smith/ImaginaryAxis.fs:129-149 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/Layout/ObjectAbstractions/Smith/ImaginaryAxis.fs:46` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (20 lines × 3) src/Plotly.NET/ChartAPI/Chart.fs:369— src/Plotly.NET/ChartAPI/Chart.fs:369-388 | src/Plotly.NET/CommonAbstractions/Line.fs:59-78 | src/Plotly.NET/Traces/Trace.fs:507-526 — before extracting anything, compare `src/Plotly.NET/ChartAPI/Chart.fs` and `src/Plotly.NET/Traces/Trace.fs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 140 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Plotly.NET/Traces/Trace.fs:529` calls `setLine` and `src/Plotly.NET/CommonAbstractions/Line.fs:104` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (20 lines × 3) src/Plotly.NET/ChartAPI/Chart.fs:2285— src/Plotly.NET/ChartAPI/Chart.fs:2285-2304 | src/Plotly.NET/ChartAPI/Chart.fs:2342-2361 | src/Plotly.NET/ChartAPI/Chart.fs:2399-2418 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart.fs:2285` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (20 lines × 3) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Distribution.fs:622— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Distribution.fs:622-641 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Distribution.fs:729-748 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Distribution.fs:844-863 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (20 lines × 3) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:142— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:142-161 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1191-1210 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1330-1349 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:142` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (18 lines × 3) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Funnel.fs:384— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Funnel.fs:384-401 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Funnel.fs:593-610 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Funnel.fs:680-697 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (18 lines × 3) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Histogram.fs:369— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Histogram.fs:369-386 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Histogram.fs:449-466 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Histogram.fs:527-544 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Histogram.fs:369` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Histogram.fs:471` calls `initHistogram2D` and `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Histogram.fs:546` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (18 lines × 3) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:552— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:552-569 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:636-653 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:714-731 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (18 lines × 3) src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:233— src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:233-250 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:342-359 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:546-563 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:233` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 4) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:80— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:80-94 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:190-204 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:737-751 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:839-853 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:80` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 4) src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:79— src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:79-93 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:180-194 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:570-584 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:836-850 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:79` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 4) src/Plotly.NET/Layout/ObjectAbstractions/Smith/ImaginaryAxis.fs:41— src/Plotly.NET/Layout/ObjectAbstractions/Smith/ImaginaryAxis.fs:41-55 | src/Plotly.NET/Layout/ObjectAbstractions/Smith/ImaginaryAxis.fs:124-138 | src/Plotly.NET/Layout/ObjectAbstractions/Smith/RealAxis.fs:43-57 | src/Plotly.NET/Layout/ObjectAbstractions/Smith/RealAxis.fs:131-145 — before extracting anything, compare `src/Plotly.NET/Layout/ObjectAbstractions/Smith/ImaginaryAxis.fs` and `src/Plotly.NET/Layout/ObjectAbstractions/Smith/RealAxis.fs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 65 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/Layout/ObjectAbstractions/Smith/ImaginaryAxis.fs:41` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 4) src/Plotly.NET/Traces/Trace2D.fs:445— src/Plotly.NET/Traces/Trace2D.fs:445-459 | src/Plotly.NET/Traces/Trace2D.fs:651-665 | src/Plotly.NET/Traces/Trace2D.fs:861-875 | src/Plotly.NET/Traces/Trace2D.fs:1284-1298 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (11 lines × 3) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:381— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:381-391 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1110-1120 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:819-829 — before extracting anything, compare `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs` and `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 122 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:381` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 3) src/Plotly.NET/Layout/ObjectAbstractions/Common/LinearAxis.fs:122— src/Plotly.NET/Layout/ObjectAbstractions/Common/LinearAxis.fs:122-132 | src/Plotly.NET/Layout/ObjectAbstractions/Common/LinearAxis.fs:382-392 | src/Plotly.NET/Layout/ObjectAbstractions/Common/LinearAxis.fs:921-931 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (11 lines × 3) src/Plotly.NET/Traces/TraceDomain.fs:264— src/Plotly.NET/Traces/TraceDomain.fs:264-274 | src/Plotly.NET/Traces/TraceDomain.fs:393-403 | src/Plotly.NET/Traces/TraceDomain.fs:538-548 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (11 lines × 3) src/Plotly.NET/Traces/TraceGeo.fs:161— src/Plotly.NET/Traces/TraceGeo.fs:161-171 | src/Plotly.NET/Traces/TraceMapbox.fs:298-308 | src/Plotly.NET/Traces/TraceMapbox.fs:431-441 — before extracting anything, compare `src/Plotly.NET/Traces/TraceGeo.fs` and `src/Plotly.NET/Traces/TraceMapbox.fs` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 175 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 2) src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Hierarchy.fs:58— src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Hierarchy.fs:58-67 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Hierarchy.fs:432-441 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Hierarchy.fs:58` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) src/Plotly.NET/Layout/ObjectAbstractions/Smith/ImaginaryAxis.fs:167— src/Plotly.NET/Layout/ObjectAbstractions/Smith/ImaginaryAxis.fs:167-176 | src/Plotly.NET/Layout/ObjectAbstractions/Smith/RealAxis.fs:178-187 — before extracting anything, compare `src/Plotly.NET/Layout/ObjectAbstractions/Smith/ImaginaryAxis.fs` and `src/Plotly.NET/Layout/ObjectAbstractions/Smith/RealAxis.fs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 65 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 2) src/Plotly.NET/Traces/Trace2D.fs:679— src/Plotly.NET/Traces/Trace2D.fs:679-688 | src/Plotly.NET/Traces/TraceCarpet.fs:112-121 — before extracting anything, compare `src/Plotly.NET/Traces/Trace2D.fs` and `src/Plotly.NET/Traces/TraceCarpet.fs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 117 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/Traces/Trace2D.fs:679` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) src/Plotly.NET/Traces/Trace2D.fs:2255— src/Plotly.NET/Traces/Trace2D.fs:2255-2264 | src/Plotly.NET/Traces/TraceCarpet.fs:219-228 — before extracting anything, compare `src/Plotly.NET/Traces/Trace2D.fs` and `src/Plotly.NET/Traces/TraceCarpet.fs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 117 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (35 lines × 2) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Funnel.fs:35— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Funnel.fs:35-69 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Funnel.fs:140-174 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Funnel.fs:35` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (35 lines × 2) src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:629— src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:629-663 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:697-731 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:629` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (35 lines × 2) src/Plotly.NET/Traces/Trace2D.fs:2583— src/Plotly.NET/Traces/Trace2D.fs:2583-2617 | src/Plotly.NET/Traces/Trace2D.fs:2737-2771 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (29 lines × 2) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:310— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:310-338 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:765-793 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:310` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (29 lines × 2) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1901— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1901-1929 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:2092-2120 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1901` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (29 lines × 2) src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:1244— src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:1244-1272 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:1311-1339 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:1244` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (28 lines × 2) src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Volume.fs:221— src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Volume.fs:221-248 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Volume.fs:287-314 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Volume.fs:221` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (28 lines × 2) src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:571— src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:571-598 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:637-664 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:571` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (28 lines × 2) src/Plotly.NET.CSharp/ChartAPI/ChartDomain/Doughnut.cs:78— src/Plotly.NET.CSharp/ChartAPI/ChartDomain/Doughnut.cs:78-105 | src/Plotly.NET.CSharp/ChartAPI/ChartDomain/Pie.cs:79-106 — before extracting anything, compare `src/Plotly.NET.CSharp/ChartAPI/ChartDomain/Doughnut.cs` and `src/Plotly.NET.CSharp/ChartAPI/ChartDomain/Pie.cs` as WHOLE FILES: 93% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET.CSharp/ChartAPI/ChartDomain/Doughnut.cs:78` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (26 lines × 2) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:354— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:354-379 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:506-531 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:354` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (26 lines × 2) src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Surface.fs:49— src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Surface.fs:49-74 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Surface.fs:103-128 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Surface.fs:49` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (26 lines × 2) src/Plotly.NET/Traces/Trace2D.fs:1692— src/Plotly.NET/Traces/Trace2D.fs:1692-1717 | src/Plotly.NET/Traces/Trace2D.fs:1878-1903 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (22 lines × 4) src/Plotly.NET/ChartAPI/Chart.fs:343— src/Plotly.NET/ChartAPI/Chart.fs:343-364 | src/Plotly.NET/CommonAbstractions/Line.fs:35-56 | src/Plotly.NET/CommonAbstractions/Line.fs:105-126 | src/Plotly.NET/Traces/Trace.fs:480-501 — before extracting anything, compare `src/Plotly.NET/ChartAPI/Chart.fs` and `src/Plotly.NET/Traces/Trace.fs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 140 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Plotly.NET/Traces/Trace.fs:454` calls `setMarker` and `src/Plotly.NET/CommonAbstractions/Line.fs:79` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (22 lines × 4) src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:87— src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:87-108 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:206-227 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:91-112 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:192-213 — `src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs` and `src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 13 separate duplicated blocks between them, totalling at least 180 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:87` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (22 lines × 4) src/Plotly.NET.CSharp/ChartAPI/Chart2D/Bar.cs:126— src/Plotly.NET.CSharp/ChartAPI/Chart2D/Bar.cs:126-147 | src/Plotly.NET.CSharp/ChartAPI/Chart2D/Column.cs:126-147 | src/Plotly.NET.CSharp/ChartAPI/Chart2D/StackedBar.cs:127-148 | src/Plotly.NET.CSharp/ChartAPI/Chart2D/StackedColumn.cs:127-148 — before extracting anything, compare `src/Plotly.NET.CSharp/ChartAPI/Chart2D/Bar.cs` and `src/Plotly.NET.CSharp/ChartAPI/Chart2D/Column.cs` as WHOLE FILES: 92% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET.CSharp/ChartAPI/Chart2D/Bar.cs:126` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (22 lines × 3) src/Plotly.NET/ChartAPI/Chart.fs:451— src/Plotly.NET/ChartAPI/Chart.fs:451-472 | src/Plotly.NET/ChartAPI/Chart.fs:526-547 | src/Plotly.NET/ChartAPI/Chart.fs:601-622 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart.fs:451` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (22 lines × 3) src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Icicle.fs:77— src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Icicle.fs:77-98 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Icicle.fs:221-242 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Icicle.fs:364-385 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Icicle.fs:77` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (22 lines × 3) src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:892— src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:892-913 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:962-983 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:1152-1173 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:892` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (22 lines × 2) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Heatmap.fs:90— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Heatmap.fs:90-111 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Heatmap.fs:171-192 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Heatmap.fs:90` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (22 lines × 2) src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Density.fs:202— src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Density.fs:202-223 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Density.fs:340-361 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Density.fs:202` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (22 lines × 2) src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:615— src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:615-636 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:883-904 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (19 lines × 3) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Heatmap.fs:93— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Heatmap.fs:93-111 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Heatmap.fs:174-192 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Heatmap.fs:343-361 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Heatmap.fs:93` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (19 lines × 3) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Splom.fs:43— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Splom.fs:43-61 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Splom.fs:122-140 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Splom.fs:190-208 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Splom.fs:43` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (19 lines × 3) src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Contour.fs:58— src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Contour.fs:58-76 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Contour.fs:160-178 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Contour.fs:260-278 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Contour.fs:58` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16–17 lines × 2) src/Plotly.NET/ChartAPI/Chart.fs:1861— src/Plotly.NET/ChartAPI/Chart.fs:1861-1877 | src/Plotly.NET/ChartAPI/Chart.fs:1917-1932 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart.fs:1861` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (16–17 lines × 2) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Heatmap.fs:335— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Heatmap.fs:335-351 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Heatmap.fs:433-448 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (16–17 lines × 2) src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:124— src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:124-140 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:243-258 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:124` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 3) src/Plotly.NET/ChartAPI/Chart.fs:1186— src/Plotly.NET/ChartAPI/Chart.fs:1186-1201 | src/Plotly.NET/ChartAPI/Chart.fs:1321-1336 | src/Plotly.NET/ChartAPI/Chart.fs:1450-1465 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart.fs:1186` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 3) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:524— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:524-539 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:609-624 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:690-705 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:524` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 3) src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Surface.fs:190— src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Surface.fs:190-205 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Surface.fs:258-273 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Surface.fs:353-368 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Surface.fs:190` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 6) src/Plotly.NET/ChartAPI/Chart.fs:432— src/Plotly.NET/ChartAPI/Chart.fs:432-446 | src/Plotly.NET/ChartAPI/Chart.fs:507-521 | src/Plotly.NET/ChartAPI/Chart.fs:582-596 | src/Plotly.NET/Traces/Trace.fs:548-562 | src/Plotly.NET/Traces/Trace.fs:602-616 | src/Plotly.NET/Traces/Trace.fs:656-670 — before extracting anything, compare `src/Plotly.NET/ChartAPI/Chart.fs` and `src/Plotly.NET/Traces/Trace.fs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 140 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (15 lines × 6) src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Hierarchy.fs:439— src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Hierarchy.fs:439-453 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Hierarchy.fs:569-583 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Hierarchy.fs:701-715 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Icicle.fs:68-82 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Icicle.fs:212-226 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Icicle.fs:355-369 — before extracting anything, compare `src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Hierarchy.fs` and `src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Icicle.fs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 87 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (15 lines × 6) src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:625— src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:625-639 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:678-692 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:751-765 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:824-838 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:1416-1430 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:1491-1505 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (14 lines × 3) src/Plotly.NET/ChartAPI/Chart.fs:3031— src/Plotly.NET/ChartAPI/Chart.fs:3031-3044 | src/Plotly.NET/ChartAPI/Chart.fs:3349-3362 | src/Plotly.NET/ChartAPI/Chart.fs:3465-3478 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart.fs:3031` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 3) src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:359— src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:359-372 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:1105-1118 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:1168-1181 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:359` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:373` calls `showText` and `src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:1182` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (14 lines × 3) src/Plotly.NET/Traces/Trace.fs:567— src/Plotly.NET/Traces/Trace.fs:567-580 | src/Plotly.NET/Traces/Trace.fs:621-634 | src/Plotly.NET/Traces/Trace.fs:675-688 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/Traces/Trace.fs:567` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 4) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Distribution.fs:59— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Distribution.fs:59-71 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Distribution.fs:166-178 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Distribution.fs:255-267 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Distribution.fs:348-360 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (13 lines × 4) src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Volume.fs:56— src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Volume.fs:56-68 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Volume.fs:124-136 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Volume.fs:218-230 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Volume.fs:284-296 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (13 lines × 4) src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:111— src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:111-123 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:211-223 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:867-882 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:953-965 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:111` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (12 lines × 4) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:2273— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:2273-2284 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Statistical.fs:359-370 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Statistical.fs:475-486 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Statistical.fs:595-606 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (12 lines × 4) src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:118— src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:118-129 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:419-430 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Volume.fs:120-131 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Volume.fs:280-291 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (12 lines × 4) src/Plotly.NET/Traces/Trace2D.fs:516— src/Plotly.NET/Traces/Trace2D.fs:516-527 | src/Plotly.NET/Traces/Trace2D.fs:715-726 | src/Plotly.NET/Traces/Trace2D.fs:931-942 | src/Plotly.NET/Traces/Trace2D.fs:1371-1382 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (10 lines × 6) src/Plotly.NET/Traces/Trace2D.fs:262— src/Plotly.NET/Traces/Trace2D.fs:262-271 | src/Plotly.NET/Traces/TraceCarpet.fs:248-257 | src/Plotly.NET/Traces/TraceGeo.fs:278-287 | src/Plotly.NET/Traces/TracePolar.fs:145-154 | src/Plotly.NET/Traces/TraceSmith.fs:117-126 | src/Plotly.NET/Traces/TraceTernary.fs:122-131 — before extracting anything, compare `src/Plotly.NET/Traces/Trace2D.fs` and `src/Plotly.NET/Traces/TraceCarpet.fs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 117 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Plotly.NET/Traces/Trace2D.fs:272` calls `withOptionalSingleOrMultiProperty` and `src/Plotly.NET/Traces/TraceCarpet.fs:258` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (10 lines × 6) src/Plotly.NET/Traces/Trace2D.fs:270— src/Plotly.NET/Traces/Trace2D.fs:270-279 | src/Plotly.NET/Traces/Trace2D.fs:490-499 | src/Plotly.NET/Traces/Trace2D.fs:692-701 | src/Plotly.NET/Traces/Trace2D.fs:904-913 | src/Plotly.NET/Traces/Trace2D.fs:1351-1360 | src/Plotly.NET/Traces/Trace2D.fs:1561-1570 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (10 lines × 6) src/Plotly.NET/Traces/Trace3D.fs:361— src/Plotly.NET/Traces/Trace3D.fs:361-370 | src/Plotly.NET/Traces/Trace3D.fs:562-571 | src/Plotly.NET/Traces/Trace3D.fs:744-753 | src/Plotly.NET/Traces/Trace3D.fs:921-930 | src/Plotly.NET/Traces/Trace3D.fs:1095-1104 | src/Plotly.NET/Traces/Trace3D.fs:1276-1285 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (10 lines × 3) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Heatmap.fs:733— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Heatmap.fs:733-742 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Contour.fs:157-166 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Contour.fs:257-266 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (10 lines × 3) src/Plotly.NET/Traces/Trace3D.fs:190— src/Plotly.NET/Traces/Trace3D.fs:190-199 | src/Plotly.NET/Traces/Trace3D.fs:351-360 | src/Plotly.NET/Traces/Trace3D.fs:551-560 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (10 lines × 3) src/Plotly.NET/Traces/TraceDomain.fs:306— src/Plotly.NET/Traces/TraceDomain.fs:306-315 | src/Plotly.NET/Traces/TraceDomain.fs:442-451 | src/Plotly.NET/Traces/TraceDomain.fs:586-595 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Plotly.NET/Traces/TraceDomain.fs:583` calls `withOptionalSingleOrMultiPropertyBy` and `src/Plotly.NET/Traces/TraceDomain.fs:439` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8 lines × 2) src/Plotly.NET/Traces/Trace2D.fs:299— src/Plotly.NET/Traces/Trace2D.fs:299-306 | src/Plotly.NET/Traces/Trace2D.fs:1377-1384 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) src/Plotly.NET/Traces/Trace2D.fs:503— src/Plotly.NET/Traces/Trace2D.fs:503-510 | src/Plotly.NET/Traces/Trace2D.fs:918-925 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Plotly.NET/Traces/Trace2D.fs:917` calls `Measure` and `src/Plotly.NET/Traces/Trace2D.fs:502` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8 lines × 2) src/Plotly.NET/Traces/Trace2D.fs:2293— src/Plotly.NET/Traces/Trace2D.fs:2293-2300 | src/Plotly.NET/Traces/TraceCarpet.fs:266-273 — before extracting anything, compare `src/Plotly.NET/Traces/Trace2D.fs` and `src/Plotly.NET/Traces/TraceCarpet.fs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 117 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Plotly.NET/Traces/TraceCarpet.fs:264` calls `withOptionalSingleOrMultiPropertyBy`, `withOptionalSingleOrMultiProperty` and `src/Plotly.NET/Traces/Trace2D.fs:2292` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (7 lines × 2) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Heatmap.fs:54— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Heatmap.fs:54-60 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Histogram.fs:616-622 — before extracting anything, compare `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Heatmap.fs` and `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Histogram.fs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 55 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 2) src/Plotly.NET/Traces/Trace2D.fs:539— src/Plotly.NET/Traces/Trace2D.fs:539-545 | src/Plotly.NET/Traces/Trace2D.fs:1154-1160 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) src/Plotly.NET/Traces/TraceGeo.fs:154— src/Plotly.NET/Traces/TraceGeo.fs:154-160 | src/Plotly.NET/Traces/TraceGeo.fs:299-305 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication· Edited copies of one member (5 members, 21+ corresponding lines) · ×2
Edited copies of one member (5 members, 21+ corresponding lines) src/Plotly.NET.CSharp/ChartAPI/Chart2D/AnnotatedHeatmap.cs:70— src/Plotly.NET.CSharp/ChartAPI/Chart2D/AnnotatedHeatmap.cs:70-93 | src/Plotly.NET.CSharp/ChartAPI/Chart2D/Heatmap.cs:66-88 | src/Plotly.NET.CSharp/ChartAPI/Chart2D/Heatmap.cs:118-138 | src/Plotly.NET.CSharp/ChartAPI/Chart2D/Histogram2D.cs:63-84 | src/Plotly.NET.CSharp/ChartAPI/Chart2D/Histogram2D.cs:114-135 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 21 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
Edited copies of one member (5 members, 21+ corresponding lines) src/Plotly.NET.CSharp/ChartAPI/Chart3D/Cone.cs:71— src/Plotly.NET.CSharp/ChartAPI/Chart3D/Cone.cs:71-91 | src/Plotly.NET.CSharp/ChartAPI/Chart3D/IsoSurface.cs:70-91 | src/Plotly.NET.CSharp/ChartAPI/Chart3D/Mesh3D.cs:77-99 | src/Plotly.NET.CSharp/ChartAPI/Chart3D/StreamTube.cs:73-93 | src/Plotly.NET.CSharp/ChartAPI/Chart3D/Volume.cs:71-93 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 21 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
Duplicated block (47 lines × 2) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:733— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:733-779 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:835-881 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:733` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (47 lines × 2) src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:817— src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:817-863 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:903-949 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:817` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (39 lines × 2) src/Plotly.NET/ChartAPI/Chart.fs:2948— src/Plotly.NET/ChartAPI/Chart.fs:2948-2986 | src/Plotly.NET/Config/Config.fs:117-155 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (39 lines × 2) src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:882— src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:882-920 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:960-998 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:882` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (37 lines × 3) src/Plotly.NET/ChartAPI/Chart.fs:697— src/Plotly.NET/ChartAPI/Chart.fs:697-733 | src/Plotly.NET/CommonAbstractions/ColorBar.fs:62-98 | src/Plotly.NET/CommonAbstractions/ColorBar.fs:210-246 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (37 lines × 3) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Statistical.fs:350— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Statistical.fs:350-386 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Statistical.fs:466-502 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Statistical.fs:586-622 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Statistical.fs:350` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (37 lines × 2) src/Plotly.NET/ChartAPI/Chart.fs:752— src/Plotly.NET/ChartAPI/Chart.fs:752-788 | src/Plotly.NET/CommonAbstractions/ColorBar.fs:111-147 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (37 lines × 2) src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:878— src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:878-914 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:949-985 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:878` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (34 lines × 2) src/Plotly.NET/Traces/Trace2D.fs:2634— src/Plotly.NET/Traces/Trace2D.fs:2634-2667 | src/Plotly.NET/Traces/Trace2D.fs:2788-2821 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (34 lines × 2) src/Plotly.NET/Traces/Trace3D.fs:656— src/Plotly.NET/Traces/Trace3D.fs:656-689 | src/Plotly.NET/Traces/Trace3D.fs:833-866 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (31 lines × 2) src/Plotly.NET/ChartAPI/Chart.fs:2067— src/Plotly.NET/ChartAPI/Chart.fs:2067-2097 | src/Plotly.NET/Layout/ObjectAbstractions/Map/Geo.fs:81-111 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Plotly.NET/ChartAPI/Chart.fs:2100` calls `withGeo` and `src/Plotly.NET/Layout/ObjectAbstractions/Map/Geo.fs:146` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (31 lines × 2) src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:354— src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:354-384 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:407-437 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:354` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (27 lines × 4) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:39— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:39-65 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:132-158 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:516-542 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:586-612 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:39` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (27 lines × 4) src/Plotly.NET/Layout/ObjectAbstractions/Polar/AngularAxis.fs:78— src/Plotly.NET/Layout/ObjectAbstractions/Polar/AngularAxis.fs:78-104 | src/Plotly.NET/Layout/ObjectAbstractions/Polar/AngularAxis.fs:223-249 | src/Plotly.NET/Layout/ObjectAbstractions/Polar/RadialAxis.fs:88-114 | src/Plotly.NET/Layout/ObjectAbstractions/Polar/RadialAxis.fs:251-277 — before extracting anything, compare `src/Plotly.NET/Layout/ObjectAbstractions/Polar/AngularAxis.fs` and `src/Plotly.NET/Layout/ObjectAbstractions/Polar/RadialAxis.fs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 88 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (27 lines × 3) src/Plotly.NET/ChartAPI/Chart.fs:1217— src/Plotly.NET/ChartAPI/Chart.fs:1217-1243 | src/Plotly.NET/ChartAPI/Chart.fs:1354-1380 | src/Plotly.NET/ChartAPI/Chart.fs:1480-1506 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart.fs:1217` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (27 lines × 3) src/Plotly.NET/Layout/ObjectAbstractions/Common/LinearAxis.fs:134— src/Plotly.NET/Layout/ObjectAbstractions/Common/LinearAxis.fs:134-160 | src/Plotly.NET/Layout/ObjectAbstractions/Common/LinearAxis.fs:393-419 | src/Plotly.NET/Layout/ObjectAbstractions/Common/LinearAxis.fs:933-959 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (25–26 lines × 2) src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Pie.fs:642— src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Pie.fs:642-667 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Pie.fs:824-848 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Pie.fs:642` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (25–26 lines × 2) src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Relations.fs:245— src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Relations.fs:245-270 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Relations.fs:321-345 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Relations.fs:319` calls `fun`, `initParallel` and `src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Relations.fs:243` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (24 lines × 2) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:83— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:83-106 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:193-216 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:83` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (24 lines × 2) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1932— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1932-1955 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:2123-2146 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1932` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (23 lines × 4) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:113— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:113-135 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:340-362 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:567-589 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:795-817 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (23 lines × 4) src/Plotly.NET.CSharp/ChartAPI/Chart2D/Bar.cs:68— src/Plotly.NET.CSharp/ChartAPI/Chart2D/Bar.cs:68-90 | src/Plotly.NET.CSharp/ChartAPI/Chart2D/Column.cs:68-90 | src/Plotly.NET.CSharp/ChartAPI/Chart2D/StackedBar.cs:69-91 | src/Plotly.NET.CSharp/ChartAPI/Chart2D/StackedColumn.cs:69-91 — before extracting anything, compare `src/Plotly.NET.CSharp/ChartAPI/Chart2D/Bar.cs` and `src/Plotly.NET.CSharp/ChartAPI/Chart2D/Column.cs` as WHOLE FILES: 92% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET.CSharp/ChartAPI/Chart2D/Bar.cs:68` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (21–22 lines × 2) src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:608— src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:608-629 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:662-682 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:608` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (21–22 lines × 2) src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:354— src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:354-375 | src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:401-421 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:354` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (21 lines × 4) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Distribution.fs:464— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Distribution.fs:464-484 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Distribution.fs:589-609 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Distribution.fs:696-716 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Distribution.fs:807-827 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Distribution.fs:464` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (21 lines × 4) src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:823— src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:823-843 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:909-929 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:578-598 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:844-864 — `src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs` and `src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 9 separate duplicated blocks between them, totalling at least 122 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:823` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (21 lines × 3) src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:192— src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:192-212 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:301-321 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:506-526 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:192` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (21 lines × 3) src/Plotly.NET/Layout/ObjectAbstractions/Common/LinearAxis.fs:162— src/Plotly.NET/Layout/ObjectAbstractions/Common/LinearAxis.fs:162-182 | src/Plotly.NET/Layout/ObjectAbstractions/Common/LinearAxis.fs:420-440 | src/Plotly.NET/Layout/ObjectAbstractions/Common/LinearAxis.fs:961-981 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (15–21 lines × 2) src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:93— src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:93-113 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:156-170 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:93` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:170` calls `init`, `setScene` and `src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:113` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (15–21 lines × 2) src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:394— src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:394-414 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:457-471 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:394` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:471` calls `init`, `setScene` and `src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:414` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (19 lines × 2) src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:654— src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:654-672 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:923-941 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:654` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (19 lines × 2) src/Plotly.NET/Layout/ObjectAbstractions/Map/MapboxLayer.fs:16— src/Plotly.NET/Layout/ObjectAbstractions/Map/MapboxLayer.fs:16-34 | src/Plotly.NET/Layout/ObjectAbstractions/Map/MapboxLayer.fs:59-77 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14–18 lines × 3) src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Pie.fs:419— src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Pie.fs:419-436 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Pie.fs:484-497 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Pie.fs:578-591 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Pie.fs:419` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (14–18 lines × 3) src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:429— src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:429-442 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:508-525 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:562-575 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:508` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (17 lines × 3) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:726— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:726-742 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:828-844 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:928-944 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:726` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17 lines × 3) src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Relations.fs:226— src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Relations.fs:226-242 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Relations.fs:299-315 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Relations.fs:372-388 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Relations.fs:226` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14–17 lines × 2) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1516— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1516-1532 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1635-1648 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1516` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (14–17 lines × 2) src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:1154— src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:1154-1170 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:1231-1244 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:1154` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (16 lines × 10) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:23— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:23-38 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:206-221 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:288-303 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:420-435 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:500-515 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:661-676 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:743-758 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:875-890 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Bar.fs:48-63 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Bar.fs:130-145 — `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs` and `src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Bar.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 5 separate duplicated blocks between them, totalling at least 79 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (16 lines × 10) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:89— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:89-104 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:220-235 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:329-344 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:433-448 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:788-803 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:904-919 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1019-1034 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1129-1144 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1269-1284 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1408-1423 — all 10 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:89` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14–15 lines × 3) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1142— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1142-1156 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1282-1295 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:930-943 — `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs` and `src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 14 separate duplicated blocks between them, totalling at least 170 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1142` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14–15 lines × 3) src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Relations.fs:45— src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Relations.fs:45-58 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Relations.fs:111-125 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Relations.fs:166-180 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Relations.fs:45` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 6) src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:71— src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:71-84 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:190-203 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:309-322 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:619-632 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:718-731 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:783-796 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:71` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 6) src/Plotly.NET/Traces/Trace3D.fs:334— src/Plotly.NET/Traces/Trace3D.fs:334-347 | src/Plotly.NET/Traces/Trace3D.fs:524-537 | src/Plotly.NET/Traces/Trace3D.fs:709-722 | src/Plotly.NET/Traces/Trace3D.fs:886-899 | src/Plotly.NET/Traces/Trace3D.fs:1066-1079 | src/Plotly.NET/Traces/Trace3D.fs:1247-1260 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (13 lines × 6) src/Plotly.NET/ChartAPI/Chart.fs:451— src/Plotly.NET/ChartAPI/Chart.fs:451-463 | src/Plotly.NET/ChartAPI/Chart.fs:526-538 | src/Plotly.NET/ChartAPI/Chart.fs:601-613 | src/Plotly.NET/Traces/Trace.fs:568-580 | src/Plotly.NET/Traces/Trace.fs:622-634 | src/Plotly.NET/Traces/Trace.fs:676-688 — before extracting anything, compare `src/Plotly.NET/ChartAPI/Chart.fs` and `src/Plotly.NET/Traces/Trace.fs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 140 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 6) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:78— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:78-90 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:188-200 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:408-420 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:522-534 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:735-747 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:837-849 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:78` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 5) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Heatmap.fs:62— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Heatmap.fs:62-74 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Heatmap.fs:145-157 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Heatmap.fs:228-240 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Heatmap.fs:306-318 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Heatmap.fs:410-422 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Heatmap.fs:62` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 5) src/Plotly.NET/Traces/Trace3D.fs:302— src/Plotly.NET/Traces/Trace3D.fs:302-314 | src/Plotly.NET/Traces/Trace3D.fs:683-695 | src/Plotly.NET/Traces/Trace3D.fs:860-872 | src/Plotly.NET/Traces/Trace3D.fs:1032-1044 | src/Plotly.NET/Traces/Trace3D.fs:1213-1225 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (12–13 lines × 3) src/Plotly.NET/ChartAPI/Chart.fs:1577— src/Plotly.NET/ChartAPI/Chart.fs:1577-1588 | src/Plotly.NET/Layout/ObjectAbstractions/3D/Scene.fs:29-41 | src/Plotly.NET/Layout/ObjectAbstractions/3D/Scene.fs:75-87 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart.fs:1577` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (12–13 lines × 3) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Heatmap.fs:89— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Heatmap.fs:89-101 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Heatmap.fs:170-182 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Heatmap.fs:246-257 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (12 lines × 5) src/Plotly.NET/Traces/Trace2D.fs:413— src/Plotly.NET/Traces/Trace2D.fs:413-424 | src/Plotly.NET/Traces/Trace2D.fs:624-635 | src/Plotly.NET/Traces/Trace2D.fs:828-839 | src/Plotly.NET/Traces/Trace2D.fs:1262-1273 | src/Plotly.NET/Traces/Trace2D.fs:1497-1508 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (12 lines × 5) src/Plotly.NET/Traces/Trace3D.fs:357— src/Plotly.NET/Traces/Trace3D.fs:357-368 | src/Plotly.NET/Traces/Trace3D.fs:740-751 | src/Plotly.NET/Traces/Trace3D.fs:917-928 | src/Plotly.NET/Traces/Trace3D.fs:1091-1102 | src/Plotly.NET/Traces/Trace3D.fs:1272-1283 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (11 lines × 6) src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:357— src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:357-367 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:418-428 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:487-497 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:1103-1113 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:1166-1176 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:1245-1255 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:357` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 6) src/Plotly.NET/Traces/Trace3D.fs:305— src/Plotly.NET/Traces/Trace3D.fs:305-315 | src/Plotly.NET/Traces/Trace3D.fs:495-505 | src/Plotly.NET/Traces/Trace3D.fs:686-696 | src/Plotly.NET/Traces/Trace3D.fs:863-873 | src/Plotly.NET/Traces/Trace3D.fs:1035-1045 | src/Plotly.NET/Traces/Trace3D.fs:1216-1226 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (11 lines × 5) src/Plotly.NET/ChartAPI/Chart.fs:3034— src/Plotly.NET/ChartAPI/Chart.fs:3034-3044 | src/Plotly.NET/ChartAPI/Chart.fs:3352-3362 | src/Plotly.NET/ChartAPI/Chart.fs:3468-3478 | src/Plotly.NET/Layout/ObjectAbstractions/Common/LayoutGrid.fs:30-40 | src/Plotly.NET/Layout/ObjectAbstractions/Common/LayoutGrid.fs:76-86 — there are 5 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 5 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart.fs:3034` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 5) src/Plotly.NET/Traces/Trace2D.fs:489— src/Plotly.NET/Traces/Trace2D.fs:489-499 | src/Plotly.NET/Traces/Trace2D.fs:691-701 | src/Plotly.NET/Traces/Trace2D.fs:903-913 | src/Plotly.NET/Traces/Trace2D.fs:1350-1360 | src/Plotly.NET/Traces/Trace2D.fs:1560-1570 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (10 lines × 11) src/Plotly.NET/Traces/Trace2D.fs:215— src/Plotly.NET/Traces/Trace2D.fs:215-224 | src/Plotly.NET/Traces/Trace2D.fs:441-450 | src/Plotly.NET/Traces/Trace2D.fs:647-656 | src/Plotly.NET/Traces/Trace2D.fs:857-866 | src/Plotly.NET/Traces/Trace2D.fs:1055-1064 | src/Plotly.NET/Traces/Trace2D.fs:1280-1289 | src/Plotly.NET/Traces/Trace2D.fs:1515-1524 | src/Plotly.NET/Traces/Trace2D.fs:1695-1704 | src/Plotly.NET/Traces/Trace2D.fs:1881-1890 | src/Plotly.NET/Traces/Trace2D.fs:2092-2101 | src/Plotly.NET/Traces/Trace2D.fs:2413-2422 — all 11 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (10 lines × 11) src/Plotly.NET/Traces/Trace2D.fs:484— src/Plotly.NET/Traces/Trace2D.fs:484-493 | src/Plotly.NET/Traces/Trace2D.fs:686-695 | src/Plotly.NET/Traces/Trace2D.fs:898-907 | src/Plotly.NET/Traces/Trace2D.fs:1103-1112 | src/Plotly.NET/Traces/Trace2D.fs:1555-1564 | src/Plotly.NET/Traces/Trace2D.fs:1740-1749 | src/Plotly.NET/Traces/Trace2D.fs:1929-1938 | src/Plotly.NET/Traces/Trace2D.fs:2134-2143 | src/Plotly.NET/Traces/Trace2D.fs:2459-2468 | src/Plotly.NET/Traces/Trace2D.fs:2632-2641 | src/Plotly.NET/Traces/Trace2D.fs:2786-2795 — all 11 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Plotly.NET/Traces/Trace2D.fs:496` calls `withOptionalSingleOrMultiProperty` and `src/Plotly.NET/Traces/Trace2D.fs:2644` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (10 lines × 4) src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:850— src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:850-859 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:936-945 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:871-880 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:943-952 — `src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs` and `src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 9 separate duplicated blocks between them, totalling at least 122 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:850` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 4) src/Plotly.NET/Traces/Trace2D.fs:2253— src/Plotly.NET/Traces/Trace2D.fs:2253-2262 | src/Plotly.NET/Traces/TraceGeo.fs:105-114 | src/Plotly.NET/Traces/TraceMapbox.fs:244-253 | src/Plotly.NET/Traces/TraceMapbox.fs:377-386 — before extracting anything, compare `src/Plotly.NET/Traces/Trace2D.fs` and `src/Plotly.NET/Traces/TraceGeo.fs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 95 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 6) src/Plotly.NET/Traces/Trace3D.fs:120— src/Plotly.NET/Traces/Trace3D.fs:120-128 | src/Plotly.NET/Traces/Trace3D.fs:460-468 | src/Plotly.NET/Traces/Trace3D.fs:654-662 | src/Plotly.NET/Traces/Trace3D.fs:831-839 | src/Plotly.NET/Traces/Trace3D.fs:1009-1017 | src/Plotly.NET/Traces/Trace3D.fs:1190-1198 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (9 lines × 6) src/Plotly.NET/Traces/TraceDomain.fs:124— src/Plotly.NET/Traces/TraceDomain.fs:124-132 | src/Plotly.NET/Traces/TraceDomain.fs:262-270 | src/Plotly.NET/Traces/TraceDomain.fs:391-399 | src/Plotly.NET/Traces/TraceDomain.fs:536-544 | src/Plotly.NET/Traces/TracePolar.fs:116-124 | src/Plotly.NET/Traces/TracePolar.fs:262-270 — there are 6 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 6 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (9 lines × 5) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:515— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:515-523 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:592-600 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Bar.fs:45-53 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:348-356 | src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:341-349 — before extracting anything, compare `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs` and `src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 160 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:515` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 5) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:682— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:682-690 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Pie.fs:726-734 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:721-729 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:479-487 | src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:454-462 — before extracting anything, compare `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs` and `src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 160 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:682` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 7) src/Plotly.NET/Traces/Trace2D.fs:287— src/Plotly.NET/Traces/Trace2D.fs:287-294 | src/Plotly.NET/Traces/Trace2D.fs:512-519 | src/Plotly.NET/Traces/Trace2D.fs:711-718 | src/Plotly.NET/Traces/Trace2D.fs:927-934 | src/Plotly.NET/Traces/Trace2D.fs:1122-1129 | src/Plotly.NET/Traces/Trace2D.fs:1367-1374 | src/Plotly.NET/Traces/Trace2D.fs:1577-1584 — all 7 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (8 lines × 7) src/Plotly.NET/Traces/Trace2D.fs:412— src/Plotly.NET/Traces/Trace2D.fs:412-419 | src/Plotly.NET/Traces/Trace2D.fs:623-630 | src/Plotly.NET/Traces/Trace2D.fs:827-834 | src/Plotly.NET/Traces/Trace2D.fs:1261-1268 | src/Plotly.NET/Traces/Trace2D.fs:1496-1503 | src/Plotly.NET/Traces/Trace2D.fs:2067-2074 | src/Plotly.NET/Traces/Trace2D.fs:2390-2397 — all 7 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (8 lines × 5) src/Plotly.NET/Traces/Trace2D.fs:2252— src/Plotly.NET/Traces/Trace2D.fs:2252-2259 | src/Plotly.NET/Traces/TraceGeo.fs:104-111 | src/Plotly.NET/Traces/TraceMapbox.fs:243-250 | src/Plotly.NET/Traces/TraceMapbox.fs:376-383 | src/Plotly.NET/Traces/TracePolar.fs:259-266 — before extracting anything, compare `src/Plotly.NET/Traces/Trace2D.fs` and `src/Plotly.NET/Traces/TraceGeo.fs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 95 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 5) src/Plotly.NET/Traces/TraceDomain.fs:172— src/Plotly.NET/Traces/TraceDomain.fs:172-179 | src/Plotly.NET/Traces/TraceDomain.fs:304-311 | src/Plotly.NET/Traces/TraceDomain.fs:440-447 | src/Plotly.NET/Traces/TraceDomain.fs:584-591 | src/Plotly.NET/Traces/TracePolar.fs:167-174 — there are 5 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 5 sites; resolving a subset leaves the remainder to drift apart. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Plotly.NET/Traces/TraceDomain.fs:171` calls `withOptionalSingleOrMultiPropertyBy` and `src/Plotly.NET/Traces/TraceDomain.fs:439` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8 lines × 4) src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Hierarchy.fs:61— src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Hierarchy.fs:61-68 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Hierarchy.fs:319-326 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Hierarchy.fs:435-442 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Hierarchy.fs:697-704 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (8 lines × 4) src/Plotly.NET/Traces/Trace2D.fs:2291— src/Plotly.NET/Traces/Trace2D.fs:2291-2298 | src/Plotly.NET/Traces/TraceGeo.fs:152-159 | src/Plotly.NET/Traces/TraceMapbox.fs:289-296 | src/Plotly.NET/Traces/TraceMapbox.fs:422-429 — before extracting anything, compare `src/Plotly.NET/Traces/Trace2D.fs` and `src/Plotly.NET/Traces/TraceGeo.fs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 95 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 3) src/Plotly.NET.ImageExport/ChartExtensions.fs:98— src/Plotly.NET.ImageExport/ChartExtensions.fs:98-105 | src/Plotly.NET.ImageExport/ChartExtensions.fs:184-191 | src/Plotly.NET.ImageExport/ChartExtensions.fs:268-275 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (8 lines × 3) src/Plotly.NET/Traces/Trace2D.fs:1275— src/Plotly.NET/Traces/Trace2D.fs:1275-1282 | src/Plotly.NET/Traces/Trace2D.fs:1510-1517 | src/Plotly.NET/Traces/Trace2D.fs:2252-2259 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (7 lines × 9) src/Plotly.NET/Traces/Trace2D.fs:287— src/Plotly.NET/Traces/Trace2D.fs:287-293 | src/Plotly.NET/Traces/Trace2D.fs:512-518 | src/Plotly.NET/Traces/Trace2D.fs:711-717 | src/Plotly.NET/Traces/Trace2D.fs:927-933 | src/Plotly.NET/Traces/Trace2D.fs:1122-1128 | src/Plotly.NET/Traces/Trace2D.fs:1367-1373 | src/Plotly.NET/Traces/Trace2D.fs:1577-1583 | src/Plotly.NET/Traces/Trace2D.fs:2162-2168 | src/Plotly.NET/Traces/Trace2D.fs:2485-2491 — all 9 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (7 lines × 9) src/Plotly.NET/Traces/Trace2D.fs:1362— src/Plotly.NET/Traces/Trace2D.fs:1362-1368 | src/Plotly.NET/Traces/Trace2D.fs:1572-1578 | src/Plotly.NET/Traces/Trace2D.fs:2480-2486 | src/Plotly.NET/Traces/Trace3D.fs:349-355 | src/Plotly.NET/Traces/Trace3D.fs:549-555 | src/Plotly.NET/Traces/Trace3D.fs:729-735 | src/Plotly.NET/Traces/Trace3D.fs:906-912 | src/Plotly.NET/Traces/Trace3D.fs:1082-1088 | src/Plotly.NET/Traces/Trace3D.fs:1263-1269 — there are 9 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 9 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (7 lines × 6) src/Plotly.NET.ImageExport/ChartExtensions.fs:55— src/Plotly.NET.ImageExport/ChartExtensions.fs:55-61 | src/Plotly.NET.ImageExport/ChartExtensions.fs:100-106 | src/Plotly.NET.ImageExport/ChartExtensions.fs:141-147 | src/Plotly.NET.ImageExport/ChartExtensions.fs:186-192 | src/Plotly.NET.ImageExport/ChartExtensions.fs:226-232 | src/Plotly.NET.ImageExport/ChartExtensions.fs:270-276 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET.ImageExport/ChartExtensions.fs:55` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 6) src/Plotly.NET/Traces/TraceCarpet.fs:265— src/Plotly.NET/Traces/TraceCarpet.fs:265-271 | src/Plotly.NET/Traces/TraceDomain.fs:1075-1081 | src/Plotly.NET/Traces/TraceGeo.fs:298-304 | src/Plotly.NET/Traces/TraceMapbox.fs:163-169 | src/Plotly.NET/Traces/TraceSmith.fs:134-140 | src/Plotly.NET/Traces/TraceTernary.fs:141-147 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 6 call sites, so a change lands once.
Duplicated block (7 lines × 4) src/Plotly.NET/Traces/Trace2D.fs:282— src/Plotly.NET/Traces/Trace2D.fs:282-288 | src/Plotly.NET/Traces/Trace2D.fs:507-513 | src/Plotly.NET/Traces/Trace2D.fs:706-712 | src/Plotly.NET/Traces/Trace3D.fs:188-194 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (7 lines × 4) src/Plotly.NET/Traces/TraceMapbox.fs:164— src/Plotly.NET/Traces/TraceMapbox.fs:164-170 | src/Plotly.NET/Traces/TraceMapbox.fs:291-297 | src/Plotly.NET/Traces/TraceMapbox.fs:424-430 | src/Plotly.NET/Traces/TraceTernary.fs:142-148 — before extracting anything, compare `src/Plotly.NET/Traces/TraceMapbox.fs` and `src/Plotly.NET/Traces/TraceTernary.fs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 112 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 3) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Distribution.fs:54— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Distribution.fs:54-60 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Distribution.fs:449-455 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Histogram.fs:615-621 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Distribution.fs:54` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 3) src/Plotly.NET/Layout/ObjectAbstractions/Common/LinearAxis.fs:1056— src/Plotly.NET/Layout/ObjectAbstractions/Common/LinearAxis.fs:1056-1062 | src/Plotly.NET/Layout/ObjectAbstractions/Polar/AngularAxis.fs:287-293 | src/Plotly.NET/Layout/ObjectAbstractions/Polar/RadialAxis.fs:320-326 — before extracting anything, compare `src/Plotly.NET/Layout/ObjectAbstractions/Polar/AngularAxis.fs` and `src/Plotly.NET/Layout/ObjectAbstractions/Polar/RadialAxis.fs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 88 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 2) src/Plotly.NET/ChartAPI/Chart.fs:1112— src/Plotly.NET/ChartAPI/Chart.fs:1112-1117 | src/Plotly.NET/ChartAPI/Chart.fs:1125-1130 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) src/Plotly.NET/Templates/ChartTemplates.fs:48— src/Plotly.NET/Templates/ChartTemplates.fs:48-53 | src/Plotly.NET/Templates/ChartTemplates.fs:65-70 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Unfinished stub — raises a "not implemented" error src/Plotly.NET/CommonAbstractions/Colors.fs:136— A shipped binding's whole body still raises a "not implemented" error — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — raises a "not implemented" error src/Plotly.NET/CommonAbstractions/Colors.fs:193— A shipped binding's whole body still raises a "not implemented" error — generated scaffolding that was never completed. Implement it or remove the dead surface.
Chart.Grid (cyclomatic 18) src/Plotly.NET/ChartAPI/Chart.fs:3027— Chart.Grid has cyclomatic complexity 18 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
Chart.Grid (cognitive 16) src/Plotly.NET/ChartAPI/Chart.fs:3027— Chart.Grid has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (10 pts), match/switch 4 (6 pts) (nesting depth added 4). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Chart.setAxis (cognitive 16) src/Plotly.NET/ChartAPI/Chart.fs:1064— Chart.setAxis has cognitive complexity 16 (threshold 15). Drivers by points: match/switch 4 (10 pts), if/else 4 (6 pts) (nesting depth added 8). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D4 · Code Duplication· Near-duplicate member family (7 members, 312 shared lines) · ×1
Near-duplicate member family (7 members, 312 shared lines) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:1— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:1-977 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1-2303 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:1-1329 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:1-1505 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:1-1075 | src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:1-993 | src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:1-1020 — These 7 members are variants of one another: a block of 312 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 7 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 7 times.
D4 · Code Duplication· Near-duplicate member family (5 members, 269 shared lines) · ×1
Near-duplicate member family (5 members, 269 shared lines) src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:1— src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:1-1174 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:1-1329 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:1-1505 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:1-1278 | src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:1-993 — These 5 members are variants of one another: a block of 269 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
D4 · Code Duplication· Near-duplicate member family (3 members, 69 shared lines) · ×1
Near-duplicate member family (3 members, 69 shared lines) src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Hierarchy.fs:1— src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Hierarchy.fs:1-766 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Icicle.fs:1-425 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Pie.fs:1-874 — These 3 members are variants of one another: a block of 69 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 3 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 3 times.
Near-duplicate member pair (108 shared lines) src/Plotly.NET/Layout/ObjectAbstractions/Polar/AngularAxis.fs:1— src/Plotly.NET/Layout/ObjectAbstractions/Polar/AngularAxis.fs:1-301 | src/Plotly.NET/Layout/ObjectAbstractions/Polar/RadialAxis.fs:1-335 — These two members are variants of one another: 108 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
Near-duplicate member pair (97 shared lines) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:1— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:1-919 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Bar.fs:1-256 — These two members are variants of one another: 97 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
Near-duplicate member pair (80 shared lines) src/Plotly.NET/Layout/ObjectAbstractions/Smith/ImaginaryAxis.fs:1— src/Plotly.NET/Layout/ObjectAbstractions/Smith/ImaginaryAxis.fs:1-176 | src/Plotly.NET/Layout/ObjectAbstractions/Smith/RealAxis.fs:1-187 — These two members are variants of one another: 80 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication· Members sharing a duplicated core (10 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (10 members, 50+ identical tokens) src/Plotly.NET/Traces/Trace.fs:1— src/Plotly.NET/Traces/Trace.fs:1-766 | src/Plotly.NET/Traces/Trace2D.fs:1-2944 | src/Plotly.NET/Traces/Trace3D.fs:1-1299 | src/Plotly.NET/Traces/TraceCarpet.fs:1-439 | src/Plotly.NET/Traces/TraceDomain.fs:1-1098 | src/Plotly.NET/Traces/TraceGeo.fs:1-318 | src/Plotly.NET/Traces/TraceMapbox.fs:1-444 | src/Plotly.NET/Traces/TracePolar.fs:1-323 | src/Plotly.NET/Traces/TraceSmith.fs:1-155 | src/Plotly.NET/Traces/TraceTernary.fs:1-163 — These 10 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 10 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 10 times.
D4 · Code Duplication· Edited copies of one member (3 members, 34+ corresponding lines) · ×1
Edited copies of one member (3 members, 34+ corresponding lines) src/Plotly.NET.CSharp/ChartAPI/ChartDomain/Icicle.cs:96— src/Plotly.NET.CSharp/ChartAPI/ChartDomain/Icicle.cs:96-132 | src/Plotly.NET.CSharp/ChartAPI/ChartDomain/Sunburst.cs:89-122 | src/Plotly.NET.CSharp/ChartAPI/ChartDomain/Treemap.cs:93-127 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 34 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 35+ corresponding lines) · ×1
Edited copies of one member (3 members, 35+ corresponding lines) src/Plotly.NET.CSharp/ChartAPI/Chart2D/Histogram.cs:92— src/Plotly.NET.CSharp/ChartAPI/Chart2D/Histogram.cs:92-126 | src/Plotly.NET.CSharp/ChartAPI/Chart2D/Histogram2DContour.cs:99-138 | src/Plotly.NET.CSharp/ChartAPI/Chart2D/Violin.cs:93-128 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 35 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 31+ corresponding lines) · ×1
Edited copies of one member (3 members, 31+ corresponding lines) src/Plotly.NET.CSharp/ChartAPI/Chart2D/Bubble.cs:77— src/Plotly.NET.CSharp/ChartAPI/Chart2D/Bubble.cs:77-107 | src/Plotly.NET.CSharp/ChartAPI/Chart2D/Spline.cs:86-120 | src/Plotly.NET.CSharp/ChartAPI/Chart2D/SplineArea.cs:85-119 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 31 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (53 corresponding lines) · ×1
Edited copy of a member (53 corresponding lines) src/Plotly.NET/Traces/ObjectAbstractions/Icicle.fs:1— src/Plotly.NET/Traces/ObjectAbstractions/Icicle.fs:1-53 | src/Plotly.NET/Traces/ObjectAbstractions/Treemap.fs:1-63 — These two members are one piece of code written twice and then edited apart: 53 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 28+ corresponding lines) · ×1
Edited copies of one member (3 members, 28+ corresponding lines) src/Plotly.NET.CSharp/GenericChartExtensions.cs:158— src/Plotly.NET.CSharp/GenericChartExtensions.cs:158-190 | src/Plotly.NET.CSharp/GenericChartExtensions.cs:269-303 | src/Plotly.NET.CSharp/GenericChartExtensions.cs:463-490 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 28 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (7 members, 26+ corresponding lines) · ×1
Edited copies of one member (7 members, 26+ corresponding lines) src/Plotly.NET.CSharp/ChartAPI/Chart2D/Scatter.cs:87— src/Plotly.NET.CSharp/ChartAPI/Chart2D/Scatter.cs:87-120 | src/Plotly.NET.CSharp/ChartAPI/Chart2D/Scatter.cs:163-196 | src/Plotly.NET.CSharp/ChartAPI/Chart3D/Scatter3D.cs:80-108 | src/Plotly.NET.CSharp/ChartAPI/Chart3D/Scatter3D.cs:147-175 | src/Plotly.NET.CSharp/ChartAPI/ChartMap/ScatterGeo.cs:77-104 | src/Plotly.NET.CSharp/ChartAPI/ChartPolar/ScatterPolar.cs:74-99 | src/Plotly.NET.CSharp/ChartAPI/ChartSmith/ScatterSmith.cs:75-101 — These 7 members are one piece of code written 7 times and then edited apart: every two of them correspond over at least 26 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 7 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (8 members, 26+ corresponding lines) · ×1
Edited copies of one member (8 members, 26+ corresponding lines) src/Plotly.NET.CSharp/ChartAPI/Chart2D/Area.cs:83— src/Plotly.NET.CSharp/ChartAPI/Chart2D/Area.cs:83-116 | src/Plotly.NET.CSharp/ChartAPI/Chart2D/Line.cs:83-116 | src/Plotly.NET.CSharp/ChartAPI/Chart2D/StackedArea.cs:77-107 | src/Plotly.NET.CSharp/ChartAPI/Chart3D/Line3D.cs:78-106 | src/Plotly.NET.CSharp/ChartAPI/ChartCarpet/LineCarpet.cs:73-98 | src/Plotly.NET.CSharp/ChartAPI/ChartMap/LineGeo.cs:75-102 | src/Plotly.NET.CSharp/ChartAPI/ChartPolar/LinePolar.cs:72-97 | src/Plotly.NET.CSharp/ChartAPI/ChartSmith/LineSmith.cs:73-99 — These 8 members are one piece of code written 8 times and then edited apart: every two of them correspond over at least 26 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 8 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (7 members, 25+ corresponding lines) · ×1
Edited copies of one member (7 members, 25+ corresponding lines) src/Plotly.NET.CSharp/ChartAPI/ChartCarpet/BubbleCarpet.cs:75— src/Plotly.NET.CSharp/ChartAPI/ChartCarpet/BubbleCarpet.cs:75-100 | src/Plotly.NET.CSharp/ChartAPI/ChartCarpet/ScatterCarpet.cs:75-100 | src/Plotly.NET.CSharp/ChartAPI/ChartCarpet/SplineCarpet.cs:76-102 | src/Plotly.NET.CSharp/ChartAPI/ChartSmith/BubbleSmith.cs:69-93 | src/Plotly.NET.CSharp/ChartAPI/ChartTernary/BubbleTernary.cs:78-104 | src/Plotly.NET.CSharp/ChartAPI/ChartTernary/LineTernary.cs:75-101 | src/Plotly.NET.CSharp/ChartAPI/ChartTernary/ScatterTernary.cs:77-103 — These 7 members are one piece of code written 7 times and then edited apart: every two of them correspond over at least 25 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 7 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 55+ corresponding lines) · ×1
Edited copies of one member (3 members, 55+ corresponding lines) src/Plotly.NET/Traces/ObjectAbstractions/Caps.fs:1— src/Plotly.NET/Traces/ObjectAbstractions/Caps.fs:1-55 | src/Plotly.NET/Traces/ObjectAbstractions/Projection.fs:1-58 | src/Plotly.NET/Traces/ObjectAbstractions/Slices.fs:1-58 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 55 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (27 corresponding lines) · ×1
Edited copy of a member (27 corresponding lines) src/Plotly.NET.CSharp/ChartAPI/Chart2D/PointDensity.cs:78— src/Plotly.NET.CSharp/ChartAPI/Chart2D/PointDensity.cs:78-106 | src/Plotly.NET.CSharp/ChartAPI/ChartCarpet/ContourCarpet.cs:74-100 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 23+ corresponding lines) · ×1
Edited copies of one member (3 members, 23+ corresponding lines) src/Plotly.NET.CSharp/ChartAPI/ChartMap/LineMapbox.cs:75— src/Plotly.NET.CSharp/ChartAPI/ChartMap/LineMapbox.cs:75-101 | src/Plotly.NET.CSharp/ChartAPI/ChartMap/PointMapbox.cs:67-89 | src/Plotly.NET.CSharp/ChartAPI/ChartMap/ScatterMapbox.cs:81-109 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 23 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (25 corresponding lines) · ×1
Edited copy of a member (25 corresponding lines) src/Plotly.NET.CSharp/ChartAPI/Chart2D/Point.cs:67— src/Plotly.NET.CSharp/ChartAPI/Chart2D/Point.cs:67-91 | src/Plotly.NET.CSharp/ChartAPI/Chart2D/Waterfall.cs:73-99 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 21+ corresponding lines) · ×1
Edited copies of one member (3 members, 21+ corresponding lines) src/Plotly.NET.CSharp/ChartAPI/Chart3D/Bubble3D.cs:68— src/Plotly.NET.CSharp/ChartAPI/Chart3D/Bubble3D.cs:68-91 | src/Plotly.NET.CSharp/ChartAPI/ChartMap/BubbleGeo.cs:65-87 | src/Plotly.NET.CSharp/ChartAPI/ChartPolar/BubblePolar.cs:62-82 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 21 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (20 corresponding lines) · ×1
Edited copy of a member (20 corresponding lines) src/Plotly.NET.CSharp/ChartAPI/ChartPolar/BarPolar.cs:62— src/Plotly.NET.CSharp/ChartAPI/ChartPolar/BarPolar.cs:62-82 | src/Plotly.NET.CSharp/ChartAPI/ChartPolar/PointPolar.cs:60-79 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 19+ corresponding lines) · ×1
Edited copies of one member (3 members, 19+ corresponding lines) src/Plotly.NET.CSharp/ChartAPI/ChartCarpet/PointCarpet.cs:61— src/Plotly.NET.CSharp/ChartAPI/ChartCarpet/PointCarpet.cs:61-80 | src/Plotly.NET.CSharp/ChartAPI/ChartSmith/PointSmith.cs:57-75 | src/Plotly.NET.CSharp/ChartAPI/ChartTernary/PointTernary.cs:63-83 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 19 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (15 corresponding lines) · ×1
Edited copy of a member (15 corresponding lines) src/Plotly.NET.CSharp/ChartAPI/Chart/Grid.cs:47— src/Plotly.NET.CSharp/ChartAPI/Chart/Grid.cs:47-63 | src/Plotly.NET.CSharp/ChartAPI/Chart/SingleStack.cs:43-57 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 16+ corresponding lines) · ×1
Edited copies of one member (3 members, 16+ corresponding lines) src/Plotly.NET.CSharp/ChartAPI/ChartMap/ChoroplethMap.cs:50— src/Plotly.NET.CSharp/ChartAPI/ChartMap/ChoroplethMap.cs:50-65 | src/Plotly.NET.CSharp/ChartAPI/ChartMap/ChoroplethMapbox.cs:58-74 | src/Plotly.NET.CSharp/ChartAPI/ChartMap/DensityMapbox.cs:58-75 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (32 corresponding lines) · ×1
Edited copy of a member (32 corresponding lines) src/Plotly.NET/Layout/ObjectAbstractions/3D/AspectRatio.fs:1— src/Plotly.NET/Layout/ObjectAbstractions/3D/AspectRatio.fs:1-32 | src/Plotly.NET/Traces/ObjectAbstractions/StreamTubeStarts.fs:1-45 — These two members are one piece of code written twice and then edited apart: 32 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 15+ corresponding lines) · ×1
Edited copies of one member (4 members, 15+ corresponding lines) src/Plotly.NET.CSharp/ChartAPI/ChartDomain/ParallelCategories.cs:54— src/Plotly.NET.CSharp/ChartAPI/ChartDomain/ParallelCategories.cs:54-70 | src/Plotly.NET.CSharp/ChartAPI/ChartDomain/ParallelCategories.cs:111-127 | src/Plotly.NET.CSharp/ChartAPI/ChartDomain/ParallelCoord.cs:51-65 | src/Plotly.NET.CSharp/ChartAPI/ChartDomain/ParallelCoord.cs:101-115 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (28 corresponding lines) · ×1
Edited copy of a member (28 corresponding lines) src/Plotly.NET/Layout/ObjectAbstractions/Common/ActiveSelection.fs:1— src/Plotly.NET/Layout/ObjectAbstractions/Common/ActiveSelection.fs:1-28 | src/Plotly.NET/Layout/ObjectAbstractions/Common/ActiveShape.fs:1-28 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (76 lines × 3) src/Plotly.NET/ChartAPI/Chart.fs:899— src/Plotly.NET/ChartAPI/Chart.fs:899-974 | src/Plotly.NET/Layout/Layout.fs:91-166 | src/Plotly.NET/Layout/Layout.fs:323-398 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (74 lines × 2) src/Plotly.NET/ChartAPI/Chart.fs:979— src/Plotly.NET/ChartAPI/Chart.fs:979-1052 | src/Plotly.NET/Layout/Layout.fs:169-242 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (57 lines × 2) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Histogram.fs:183— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Histogram.fs:183-239 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Histogram.fs:274-330 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Histogram.fs:183` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (108 lines × 2) src/Plotly.NET/Traces/Trace3D.fs:1011— src/Plotly.NET/Traces/Trace3D.fs:1011-1118 | src/Plotly.NET/Traces/Trace3D.fs:1192-1299 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/Traces/Trace3D.fs:1011` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (54 lines × 2) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Distribution.fs:165— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Distribution.fs:165-218 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Distribution.fs:254-307 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Distribution.fs:165` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (48 lines × 2) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Splom.fs:271— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Splom.fs:271-318 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Splom.fs:378-425 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Splom.fs:271` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (45 lines × 2) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Distribution.fs:600— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Distribution.fs:600-644 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Distribution.fs:707-751 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Distribution.fs:600` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (41–45 lines × 2) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Funnel.fs:245— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Funnel.fs:245-289 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Funnel.fs:307-347 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Funnel.fs:245` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Funnel.fs:347` calls `mapLayout`, `style` and `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Funnel.fs:289` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (44 lines × 2) src/Plotly.NET/Layout/ObjectAbstractions/Common/Annotation.fs:14— src/Plotly.NET/Layout/ObjectAbstractions/Common/Annotation.fs:14-57 | src/Plotly.NET/Layout/ObjectAbstractions/Common/Annotation.fs:105-148 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (42–43 lines × 2) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1143— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1143-1185 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1283-1324 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1143` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (41–42 lines × 2) src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:571— src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:571-612 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:837-877 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:571` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (41 lines × 3) src/Plotly.NET/ChartAPI/Chart.fs:2903— src/Plotly.NET/ChartAPI/Chart.fs:2903-2943 | src/Plotly.NET/Config/Config.fs:74-114 | src/Plotly.NET/Config/Config.fs:222-262 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (41 lines × 2) src/Plotly.NET/Layout/ObjectAbstractions/Common/LinearAxis.fs:103— src/Plotly.NET/Layout/ObjectAbstractions/Common/LinearAxis.fs:103-143 | src/Plotly.NET/Layout/ObjectAbstractions/Common/LinearAxis.fs:902-942 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/Layout/ObjectAbstractions/Common/LinearAxis.fs:103` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (36–37 lines × 2) src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:401— src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:401-437 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:531-566 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:401` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (36 lines × 4) src/Plotly.NET/ChartAPI/Chart.fs:219— src/Plotly.NET/ChartAPI/Chart.fs:219-254 | src/Plotly.NET/Traces/ObjectAbstractions/Marker.fs:51-86 | src/Plotly.NET/Traces/ObjectAbstractions/Marker.fs:163-198 | src/Plotly.NET/Traces/Trace.fs:377-412 — before extracting anything, compare `src/Plotly.NET/ChartAPI/Chart.fs` and `src/Plotly.NET/Traces/Trace.fs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 140 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (36 lines × 2) src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Contour.fs:67— src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Contour.fs:67-102 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Contour.fs:169-204 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Contour.fs:67` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (35 lines × 3) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1845— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1845-1879 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:2037-2071 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:2228-2262 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1845` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (34 lines × 4) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Heatmap.fs:633— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Heatmap.fs:633-666 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Heatmap.fs:758-791 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Histogram.fs:652-685 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Histogram.fs:795-828 — before extracting anything, compare `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Heatmap.fs` and `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Histogram.fs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 55 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Heatmap.fs:633` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (34 lines × 3) src/Plotly.NET/ChartAPI/Chart.fs:259— src/Plotly.NET/ChartAPI/Chart.fs:259-292 | src/Plotly.NET/Traces/ObjectAbstractions/Marker.fs:89-122 | src/Plotly.NET/Traces/Trace.fs:418-451 — before extracting anything, compare `src/Plotly.NET/ChartAPI/Chart.fs` and `src/Plotly.NET/Traces/Trace.fs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 140 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Plotly.NET/Traces/Trace.fs:454` calls `setMarker` and `src/Plotly.NET/Traces/ObjectAbstractions/Marker.fs:162` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (33–34 lines × 2) src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:623— src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:623-655 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:787-820 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:623` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (33 lines × 4) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Statistical.fs:132— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Statistical.fs:132-164 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Statistical.fs:315-347 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Statistical.fs:430-462 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Statistical.fs:551-583 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Statistical.fs:132` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (33 lines × 2) src/Plotly.NET/Traces/Trace3D.fs:714— src/Plotly.NET/Traces/Trace3D.fs:714-746 | src/Plotly.NET/Traces/Trace3D.fs:891-923 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (31–32 lines × 3) src/Plotly.NET/ChartAPI/Chart.fs:2030— src/Plotly.NET/ChartAPI/Chart.fs:2030-2060 | src/Plotly.NET/Layout/ObjectAbstractions/Map/Geo.fs:46-77 | src/Plotly.NET/Layout/ObjectAbstractions/Map/Geo.fs:147-178 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart.fs:2030` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (32 lines × 2) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Splom.fs:321— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Splom.fs:321-352 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Splom.fs:428-459 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Splom.fs:321` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (31–32 lines × 2) src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:543— src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:543-574 | src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:611-641 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:543` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (28–32 lines × 2) src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:814— src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:814-845 | src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:885-912 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:814` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (31 lines × 3) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Histogram.fs:624— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Histogram.fs:624-654 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Histogram.fs:767-797 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Histogram.fs:910-940 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Histogram.fs:624` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (29 lines × 3) src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Hierarchy.fs:63— src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Hierarchy.fs:63-91 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Hierarchy.fs:191-219 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Hierarchy.fs:321-349 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Hierarchy.fs:63` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12–29 lines × 2) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Heatmap.fs:250— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Heatmap.fs:250-261 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Heatmap.fs:441-469 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Heatmap.fs:441` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (28–29 lines × 2) src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:406— src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:406-434 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:540-567 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:406` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (25–26 lines × 3) src/Plotly.NET/ChartAPI/Chart.fs:2591— src/Plotly.NET/ChartAPI/Chart.fs:2591-2615 | src/Plotly.NET/Layout/ObjectAbstractions/Common/Legend.fs:41-66 | src/Plotly.NET/Layout/ObjectAbstractions/Common/Legend.fs:126-151 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart.fs:2591` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (51 lines × 2) src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:75— src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:75-125 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:195-245 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:75` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (25 lines × 4) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Funnel.fs:22— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Funnel.fs:22-46 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Funnel.fs:127-151 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Funnel.fs:232-256 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Funnel.fs:294-318 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Funnel.fs:22` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (23–24 lines × 10) src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Hierarchy.fs:90— src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Hierarchy.fs:90-113 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Hierarchy.fs:218-241 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Hierarchy.fs:465-488 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Hierarchy.fs:595-618 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Icicle.fs:97-120 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Icicle.fs:241-264 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Pie.fs:81-103 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Pie.fs:190-212 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Pie.fs:650-673 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Pie.fs:832-854 — before extracting anything, compare `src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Hierarchy.fs` and `src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Icicle.fs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 87 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Hierarchy.fs:90` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (23 lines × 8) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1533— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1533-1555 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1651-1673 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:1125-1147 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:1202-1224 | src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:803-825 | src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:874-896 | src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:812-834 | src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:891-913 — `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs` and `src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 13 separate duplicated blocks between them, totalling at least 185 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1533` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17–23 lines × 2) src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Surface.fs:226— src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Surface.fs:226-248 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Surface.fs:295-311 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Surface.fs:226` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Surface.fs:311` calls `init`, `setScene` and `src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Surface.fs:248` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (19–20 lines × 16) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:109— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:109-128 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1159-1177 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1298-1316 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:84-103 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:184-203 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:838-856 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:924-942 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:206-225 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:315-334 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:520-539 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:91-110 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:211-230 | src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:83-102 | src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:185-204 | src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:83-102 | src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:185-204 — `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs` and `src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 13 separate duplicated blocks between them, totalling at least 185 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:109` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (19–20 lines × 4) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:794— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:794-813 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:910-928 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1135-1154 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1275-1293 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:794` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (20 lines × 4) src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:1249— src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:1249-1268 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:1316-1335 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:885-904 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:956-975 — before extracting anything, compare `src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs` and `src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 153 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:1249` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15–20 lines × 2) src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:924— src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:924-943 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:1002-1016 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:924` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:1016` calls `init`, `setScene` and `src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:943` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (13–20 lines × 2) src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Surface.fs:78— src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Surface.fs:78-97 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Surface.fs:132-144 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Surface.fs:78` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Surface.fs:144` calls `init`, `setScene` and `src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Surface.fs:97` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (15–19 lines × 5) src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:438— src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:438-452 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:924-942 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:994-1008 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:1085-1099 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:1183-1197 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:924` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (15–19 lines × 4) src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:342— src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:342-356 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:655-669 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:748-766 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:820-834 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:748` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (18–19 lines × 4) src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:564— src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:564-581 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:630-647 | src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:548-566 | src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:616-633 — `src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs` and `src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 15 separate duplicated blocks between them, totalling at least 219 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:564` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15–19 lines × 2) src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:1275— src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:1275-1293 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:1342-1356 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:1275` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (18 lines × 4) src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Density.fs:55— src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Density.fs:55-72 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Density.fs:130-147 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Density.fs:203-220 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Density.fs:341-358 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Density.fs:55` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14–18 lines × 4) src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:301— src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:301-314 | src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:575-592 | src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:642-655 | src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:729-742 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:575` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (16–18 lines × 3) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Heatmap.fs:65— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Heatmap.fs:65-82 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Heatmap.fs:148-165 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Heatmap.fs:309-324 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Heatmap.fs:65` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (17 lines × 7) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:41— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:41-57 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:134-150 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:518-534 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:588-604 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Histogram.fs:93-109 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Bar.fs:64-80 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Bar.fs:219-235 — `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs` and `src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Bar.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 5 separate duplicated blocks between them, totalling at least 79 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:41` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12–17 lines × 2) src/Plotly.NET/ChartAPI/Chart.fs:3421— src/Plotly.NET/ChartAPI/Chart.fs:3421-3432 | src/Plotly.NET/ChartAPI/Chart.fs:3487-3503 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart.fs:3487` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (16 lines × 50) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:100— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:100-115 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:210-225 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:316-331 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:431-446 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:545-560 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:652-667 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:757-772 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:859-874 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:955-970 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:244-259 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:352-367 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:459-474 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:822-837 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:937-952 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1044-1059 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1434-1449 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1769-1784 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:337-352 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:650-665 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:743-758 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:815-830 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:295-310 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:591-606 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:657-672 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:744-759 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:1040-1055 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:1313-1328 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:433-448 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:919-934 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:989-1004 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:1080-1095 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:1178-1193 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:341-356 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:657-672 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:725-740 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:815-830 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:303-318 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:681-696 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:766-781 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:1046-1061 | src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:296-311 | src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:570-585 | src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:637-652 | src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:724-739 | src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:977-992 | src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:292-307 | src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:577-592 | src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:644-659 | src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:726-741 | src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:1004-1019 — before extracting anything, compare `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs` and `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 122 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (16 lines × 6) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:70— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:70-85 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:180-195 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:290-305 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:400-415 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:514-529 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:625-640 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:70` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 5) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:116— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:116-131 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:343-358 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:570-585 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:798-813 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Bar.fs:203-218 — `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs` and `src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Bar.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 5 separate duplicated blocks between them, totalling at least 79 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (15–16 lines × 5) src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:83— src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:83-98 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:202-217 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:87-102 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:188-203 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:1175-1189 — `src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs` and `src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 13 separate duplicated blocks between them, totalling at least 180 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:83` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (16 lines × 4) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:61— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:61-76 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:213-228 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:361-376 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:513-528 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:61` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12–16 lines × 4) src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:132— src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:132-143 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:252-263 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:919-934 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:990-1002 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:132` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:143` calls `addLayout`, `init`, `setMapbox` and `src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:934` does not — after which the two agree again for 5 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (15–16 lines × 3) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Histogram.fs:398— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Histogram.fs:398-413 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Histogram.fs:476-491 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Histogram.fs:550-564 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (14–15 lines × 52) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:101— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:101-114 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:211-224 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:317-330 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:432-445 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:546-559 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:653-666 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:758-771 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:860-873 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:956-969 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:245-258 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:353-366 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:460-473 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:823-836 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:938-951 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1045-1058 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1435-1448 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1770-1783 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1904-1918 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:2095-2109 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:338-351 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:651-664 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:744-757 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:816-829 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:296-309 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:592-605 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:658-671 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:745-758 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:1041-1054 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:1314-1327 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:434-447 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:920-933 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:990-1003 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:1081-1094 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:1179-1192 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:342-355 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:658-671 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:726-739 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:816-829 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:304-317 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:682-695 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:767-780 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:1047-1060 | src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:297-310 | src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:571-584 | src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:638-651 | src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:725-738 | src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:978-991 | src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:293-306 | src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:578-591 | src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:645-658 | src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:727-740 | src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:1005-1018 — before extracting anything, compare `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs` and `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 122 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (15 lines × 15) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:23— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:23-37 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:116-130 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:206-220 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:288-302 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:343-357 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:420-434 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:500-514 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:570-584 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:661-675 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:743-757 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:798-812 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:875-889 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Bar.fs:48-62 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Bar.fs:130-144 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Bar.fs:203-217 — `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs` and `src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Bar.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 5 separate duplicated blocks between them, totalling at least 79 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (13–15 lines × 13) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:103— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:103-116 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Splom.fs:58-72 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:78-91 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:178-191 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:200-213 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:309-322 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:514-527 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:84-98 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:204-218 | src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:78-90 | src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:180-192 | src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:77-90 | src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:179-192 — `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs` and `src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 13 separate duplicated blocks between them, totalling at least 185 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:103` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (15 lines × 12) src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Surface.fs:57— src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Surface.fs:57-71 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Surface.fs:111-125 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Surface.fs:202-216 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Surface.fs:270-284 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:69-83 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:132-146 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:370-384 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:433-447 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Volume.fs:70-84 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Volume.fs:138-152 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Volume.fs:231-245 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Volume.fs:297-311 — there are 12 copies across 3 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 12 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Surface.fs:57` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12–15 lines × 10) src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:71— src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:71-82 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:171-182 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:816-827 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:902-913 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:1111-1122 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:1188-1199 | src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:70-81 | src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:172-183 | src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:797-811 | src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:877-888 — `src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs` and `src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 15 separate duplicated blocks between them, totalling at least 219 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:71` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:1125` calls `showText` and `src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:85` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (15 lines × 9) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:232— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:232-246 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:313-327 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:367-381 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:446-460 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:687-701 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:768-782 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:822-836 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:901-915 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Bar.fs:154-168 — `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs` and `src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Bar.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 5 separate duplicated blocks between them, totalling at least 79 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (15 lines × 8) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1644— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1644-1658 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:889-903 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:967-981 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:1118-1132 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:1195-1209 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:366-380 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:1112-1126 | src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:884-898 — `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs` and `src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 8 separate duplicated blocks between them, totalling at least 101 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1644` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 7) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:117— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:117-131 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:97-111 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:216-230 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:99-113 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:219-233 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:101-115 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:202-216 — `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs` and `src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 8 separate duplicated blocks between them, totalling at least 101 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:117` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14–15 lines × 4) src/Plotly.NET/Traces/TraceDomain.fs:147— src/Plotly.NET/Traces/TraceDomain.fs:147-160 | src/Plotly.NET/Traces/TraceDomain.fs:280-293 | src/Plotly.NET/Traces/TraceDomain.fs:416-430 | src/Plotly.NET/Traces/TraceDomain.fs:559-573 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/Traces/TraceDomain.fs:147` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 3) src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:497— src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:497-511 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:1080-1094 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:1160-1174 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (14–15 lines × 2) src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Surface.fs:223— src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Surface.fs:223-236 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Surface.fs:375-389 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 19) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:66— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:66-79 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:176-189 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:286-299 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:396-409 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:510-523 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:621-634 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:85-98 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:216-229 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:325-338 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:429-442 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:784-797 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:900-913 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1015-1028 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1125-1138 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1265-1278 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1404-1417 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1510-1523 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1629-1642 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1743-1756 — before extracting anything, compare `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs` and `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 122 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (14 lines × 13) src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:331— src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:331-344 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:491-504 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:1074-1087 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:1154-1167 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:289-302 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:494-507 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:1307-1320 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:427-440 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:1410-1423 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:297-310 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:1260-1273 | src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:290-303 | src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:971-984 — `src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs` and `src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 7 separate duplicated blocks between them, totalling at least 91 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (14 lines × 10) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1535— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1535-1548 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1653-1666 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:1127-1140 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:1204-1217 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:894-907 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:965-978 | src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:805-818 | src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:876-889 | src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:814-827 | src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:893-906 — `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs` and `src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 13 separate duplicated blocks between them, totalling at least 185 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (14 lines × 8) src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:188— src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:188-201 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:297-310 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:409-422 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:502-515 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:888-901 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:958-971 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:1056-1069 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:1148-1161 — all 8 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:188` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 7) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Heatmap.fs:618— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Heatmap.fs:618-631 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Heatmap.fs:743-756 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Histogram.fs:634-647 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Histogram.fs:777-790 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Histogram.fs:920-933 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Splom.fs:275-288 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Splom.fs:382-395 — before extracting anything, compare `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Heatmap.fs` and `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Histogram.fs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 55 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (13–14 lines × 5) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:140— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:140-152 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1189-1201 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1328-1340 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1563-1576 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1681-1694 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (14 lines × 5) src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Pie.fs:314— src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Pie.fs:314-327 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Pie.fs:415-428 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Pie.fs:480-493 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Pie.fs:574-587 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Pie.fs:759-772 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (13–14 lines × 3) src/Plotly.NET/Traces/Trace3D.fs:159— src/Plotly.NET/Traces/Trace3D.fs:159-172 | src/Plotly.NET/Traces/Trace3D.fs:324-336 | src/Plotly.NET/Traces/Trace3D.fs:513-526 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/Traces/Trace3D.fs:159` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13–14 lines × 2) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Funnel.fs:436— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Funnel.fs:436-449 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Funnel.fs:631-643 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (13 lines × 66) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:62— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:62-74 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:172-184 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:282-294 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:392-404 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:506-518 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:617-629 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:722-734 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:824-836 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:924-936 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:81-93 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:212-224 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:321-333 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:425-437 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:780-792 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:896-908 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1011-1023 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1121-1133 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1261-1273 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1400-1412 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1506-1518 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1625-1637 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1739-1751 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:65-77 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:165-177 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:269-281 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:558-570 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:624-636 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:718-730 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:810-822 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:896-908 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:1013-1025 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:1105-1117 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:1182-1194 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:1287-1299 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:184-196 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:293-305 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:405-417 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:498-510 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:884-896 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:954-966 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:1052-1064 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:1144-1156 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:68-80 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:188-200 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:312-324 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:623-635 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:691-703 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:788-800 | src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:63-75 | src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:165-177 | src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:269-281 | src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:536-548 | src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:604-616 | src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:698-710 | src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:785-797 | src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:857-869 | src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:951-963 | src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:64-76 | src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:166-178 | src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:266-278 | src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:542-554 | src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:610-622 | src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:700-712 | src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:791-803 | src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:871-883 | src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:974-986 — before extracting anything, compare `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs` and `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 122 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (12–13 lines × 18) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:106— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:106-118 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1156-1168 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1295-1307 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:81-93 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:181-193 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:203-215 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:312-324 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:517-529 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:1255-1266 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:1322-1333 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:88-100 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:208-220 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:891-902 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:962-973 | src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:80-92 | src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:182-194 | src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:80-92 | src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:182-194 — `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs` and `src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 13 separate duplicated blocks between them, totalling at least 185 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:106` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:1253` calls `showText` and `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:104` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (13 lines × 15) src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:67— src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:67-79 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:186-198 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:305-317 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:615-627 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:714-726 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:779-791 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:73-85 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:174-186 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:277-289 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:564-576 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:648-660 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:740-752 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:830-842 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:917-929 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:1019-1031 — `src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs` and `src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 13 separate duplicated blocks between them, totalling at least 180 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (13 lines × 9) src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Pie.fs:63— src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Pie.fs:63-75 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Pie.fs:172-184 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Pie.fs:282-294 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Pie.fs:380-392 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Pie.fs:448-460 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Pie.fs:543-555 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Pie.fs:634-646 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Pie.fs:732-744 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Pie.fs:816-828 — all 9 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (12–13 lines × 9) src/Plotly.NET/Templates/ChartTemplates.fs:202— src/Plotly.NET/Templates/ChartTemplates.fs:202-213 | src/Plotly.NET/Templates/ChartTemplates.fs:216-228 | src/Plotly.NET/Templates/ChartTemplates.fs:424-436 | src/Plotly.NET/Templates/ChartTemplates.fs:443-455 | src/Plotly.NET/Templates/ChartTemplates.fs:469-481 | src/Plotly.NET/Templates/ChartTemplates.fs:489-501 | src/Plotly.NET/Templates/ChartTemplates.fs:523-535 | src/Plotly.NET/Templates/ChartTemplates.fs:543-555 | src/Plotly.NET/Templates/ChartTemplates.fs:666-678 — all 9 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/Templates/ChartTemplates.fs:202` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (13 lines × 8) src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:601— src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:601-613 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:655-667 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:729-741 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:802-814 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:1238-1250 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:1305-1317 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:1392-1404 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:1469-1481 — all 8 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:601` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 7) src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:397— src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:397-409 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:474-486 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:527-539 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:878-890 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:956-968 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:1056-1068 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:1132-1144 — all 7 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:397` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12–13 lines × 4) src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Volume.fs:92— src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Volume.fs:92-103 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Volume.fs:160-171 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Volume.fs:253-265 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Volume.fs:319-331 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (12–13 lines × 2) src/Plotly.NET/Traces/TraceDomain.fs:653— src/Plotly.NET/Traces/TraceDomain.fs:653-664 | src/Plotly.NET/Traces/TraceDomain.fs:801-813 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/Traces/TraceDomain.fs:653` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10–12 lines × 14) src/Plotly.NET/Traces/Trace2D.fs:680— src/Plotly.NET/Traces/Trace2D.fs:680-690 | src/Plotly.NET/Traces/Trace3D.fs:163-174 | src/Plotly.NET/Traces/Trace3D.fs:328-338 | src/Plotly.NET/Traces/Trace3D.fs:517-528 | src/Plotly.NET/Traces/Trace3D.fs:704-713 | src/Plotly.NET/Traces/Trace3D.fs:881-890 | src/Plotly.NET/Traces/Trace3D.fs:1060-1070 | src/Plotly.NET/Traces/Trace3D.fs:1241-1251 | src/Plotly.NET/Traces/TraceCarpet.fs:243-253 | src/Plotly.NET/Traces/TraceCarpet.fs:388-398 | src/Plotly.NET/Traces/TraceGeo.fs:134-144 | src/Plotly.NET/Traces/TraceGeo.fs:273-283 | src/Plotly.NET/Traces/TraceMapbox.fs:402-411 | src/Plotly.NET/Traces/TraceTernary.fs:117-127 — there are 14 copies across 6 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 14 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/Traces/Trace2D.fs:680` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 9) src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Hierarchy.fs:69— src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Hierarchy.fs:69-80 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Hierarchy.fs:197-208 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Hierarchy.fs:327-338 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Hierarchy.fs:445-456 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Hierarchy.fs:575-586 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Hierarchy.fs:707-718 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Icicle.fs:74-85 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Icicle.fs:218-229 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Icicle.fs:361-372 — before extracting anything, compare `src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Hierarchy.fs` and `src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Icicle.fs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 87 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 7) src/Plotly.NET/Traces/Trace2D.fs:186— src/Plotly.NET/Traces/Trace2D.fs:186-197 | src/Plotly.NET/Traces/TraceCarpet.fs:196-207 | src/Plotly.NET/Traces/TraceGeo.fs:225-236 | src/Plotly.NET/Traces/TraceMapbox.fs:95-106 | src/Plotly.NET/Traces/TracePolar.fs:88-99 | src/Plotly.NET/Traces/TraceSmith.fs:67-78 | src/Plotly.NET/Traces/TraceTernary.fs:68-79 — before extracting anything, compare `src/Plotly.NET/Traces/Trace2D.fs` and `src/Plotly.NET/Traces/TraceCarpet.fs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 117 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/Traces/Trace2D.fs:186` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11–12 lines × 4) src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Density.fs:82— src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Density.fs:82-92 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Density.fs:157-167 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Density.fs:231-242 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Density.fs:369-380 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Density.fs:82` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9–12 lines × 2) src/Plotly.NET/Templates/ChartTemplates.fs:136— src/Plotly.NET/Templates/ChartTemplates.fs:136-144 | src/Plotly.NET/Templates/ChartTemplates.fs:155-166 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (11 lines × 23) src/Plotly.NET/Traces/Trace2D.fs:404— src/Plotly.NET/Traces/Trace2D.fs:404-414 | src/Plotly.NET/Traces/Trace2D.fs:615-625 | src/Plotly.NET/Traces/Trace2D.fs:819-829 | src/Plotly.NET/Traces/Trace2D.fs:1030-1040 | src/Plotly.NET/Traces/Trace2D.fs:1488-1498 | src/Plotly.NET/Traces/Trace2D.fs:1673-1683 | src/Plotly.NET/Traces/Trace2D.fs:1861-1871 | src/Plotly.NET/Traces/Trace2D.fs:2059-2069 | src/Plotly.NET/Traces/Trace2D.fs:2235-2245 | src/Plotly.NET/Traces/Trace2D.fs:2382-2392 | src/Plotly.NET/Traces/Trace2D.fs:2576-2586 | src/Plotly.NET/Traces/Trace2D.fs:2730-2740 | src/Plotly.NET/Traces/Trace2D.fs:2871-2881 | src/Plotly.NET/Traces/Trace3D.fs:273-283 | src/Plotly.NET/Traces/Trace3D.fs:452-462 | src/Plotly.NET/Traces/Trace3D.fs:646-656 | src/Plotly.NET/Traces/Trace3D.fs:823-833 | src/Plotly.NET/Traces/Trace3D.fs:1001-1011 | src/Plotly.NET/Traces/Trace3D.fs:1182-1192 | src/Plotly.NET/Traces/TraceCarpet.fs:76-86 | src/Plotly.NET/Traces/TraceCarpet.fs:337-347 | src/Plotly.NET/Traces/TraceMapbox.fs:358-368 | src/Plotly.NET/Traces/TracePolar.fs:232-242 — there are 23 copies across 5 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 23 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/Traces/Trace2D.fs:404` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10–11 lines × 17) src/Plotly.NET/Traces/Trace2D.fs:258— src/Plotly.NET/Traces/Trace2D.fs:258-267 | src/Plotly.NET/Traces/Trace2D.fs:478-488 | src/Plotly.NET/Traces/Trace2D.fs:892-902 | src/Plotly.NET/Traces/Trace2D.fs:1097-1107 | src/Plotly.NET/Traces/Trace2D.fs:1338-1348 | src/Plotly.NET/Traces/Trace2D.fs:1549-1559 | src/Plotly.NET/Traces/Trace2D.fs:1734-1744 | src/Plotly.NET/Traces/Trace2D.fs:1923-1933 | src/Plotly.NET/Traces/Trace2D.fs:2128-2138 | src/Plotly.NET/Traces/Trace2D.fs:2271-2281 | src/Plotly.NET/Traces/Trace2D.fs:2453-2463 | src/Plotly.NET/Traces/Trace2D.fs:2626-2636 | src/Plotly.NET/Traces/Trace2D.fs:2780-2790 | src/Plotly.NET/Traces/Trace2D.fs:2908-2918 | src/Plotly.NET/Traces/TracePolar.fs:140-150 | src/Plotly.NET/Traces/TracePolar.fs:279-289 | src/Plotly.NET/Traces/TraceSmith.fs:113-122 — before extracting anything, compare `src/Plotly.NET/Traces/Trace2D.fs` and `src/Plotly.NET/Traces/TracePolar.fs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 105 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/Traces/Trace2D.fs:258` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 15) src/Plotly.NET/Traces/Trace2D.fs:206— src/Plotly.NET/Traces/Trace2D.fs:206-216 | src/Plotly.NET/Traces/Trace2D.fs:432-442 | src/Plotly.NET/Traces/Trace2D.fs:638-648 | src/Plotly.NET/Traces/Trace2D.fs:848-858 | src/Plotly.NET/Traces/Trace3D.fs:130-140 | src/Plotly.NET/Traces/TraceCarpet.fs:212-222 | src/Plotly.NET/Traces/TraceDomain.fs:117-127 | src/Plotly.NET/Traces/TraceDomain.fs:255-265 | src/Plotly.NET/Traces/TraceDomain.fs:529-539 | src/Plotly.NET/Traces/TraceDomain.fs:1022-1032 | src/Plotly.NET/Traces/TraceGeo.fs:244-254 | src/Plotly.NET/Traces/TraceMapbox.fs:112-122 | src/Plotly.NET/Traces/TracePolar.fs:109-119 | src/Plotly.NET/Traces/TraceSmith.fs:83-93 | src/Plotly.NET/Traces/TraceTernary.fs:86-96 — there are 15 copies across 9 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 15 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (10–11 lines × 4) src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:352— src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:352-362 | src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:399-408 | src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:349-359 | src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:399-409 — `src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs` and `src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 13 separate duplicated blocks between them, totalling at least 181 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:352` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 13) src/Plotly.NET/Traces/Trace2D.fs:213— src/Plotly.NET/Traces/Trace2D.fs:213-222 | src/Plotly.NET/Traces/Trace2D.fs:439-448 | src/Plotly.NET/Traces/Trace2D.fs:645-654 | src/Plotly.NET/Traces/Trace2D.fs:855-864 | src/Plotly.NET/Traces/Trace2D.fs:1053-1062 | src/Plotly.NET/Traces/Trace2D.fs:1278-1287 | src/Plotly.NET/Traces/Trace2D.fs:1513-1522 | src/Plotly.NET/Traces/Trace2D.fs:2090-2099 | src/Plotly.NET/Traces/Trace2D.fs:2411-2420 | src/Plotly.NET/Traces/Trace2D.fs:2886-2895 | src/Plotly.NET/Traces/Trace3D.fs:137-146 | src/Plotly.NET/Traces/Trace3D.fs:294-303 | src/Plotly.NET/Traces/Trace3D.fs:483-492 — there are 13 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 13 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (10 lines × 8) src/Plotly.NET/Traces/Trace2D.fs:1275— src/Plotly.NET/Traces/Trace2D.fs:1275-1284 | src/Plotly.NET/Traces/Trace2D.fs:1510-1519 | src/Plotly.NET/Traces/Trace3D.fs:291-300 | src/Plotly.NET/Traces/Trace3D.fs:480-489 | src/Plotly.NET/Traces/Trace3D.fs:669-678 | src/Plotly.NET/Traces/Trace3D.fs:846-855 | src/Plotly.NET/Traces/Trace3D.fs:1020-1029 | src/Plotly.NET/Traces/Trace3D.fs:1201-1210 — there are 8 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 8 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (9 lines × 28) src/Plotly.NET/Traces/Trace2D.fs:260— src/Plotly.NET/Traces/Trace2D.fs:260-268 | src/Plotly.NET/Traces/Trace2D.fs:481-489 | src/Plotly.NET/Traces/Trace2D.fs:683-691 | src/Plotly.NET/Traces/Trace2D.fs:895-903 | src/Plotly.NET/Traces/Trace2D.fs:1100-1108 | src/Plotly.NET/Traces/Trace2D.fs:1552-1560 | src/Plotly.NET/Traces/Trace2D.fs:1737-1745 | src/Plotly.NET/Traces/Trace2D.fs:1926-1934 | src/Plotly.NET/Traces/Trace2D.fs:2131-2139 | src/Plotly.NET/Traces/Trace2D.fs:2274-2282 | src/Plotly.NET/Traces/Trace2D.fs:2456-2464 | src/Plotly.NET/Traces/Trace2D.fs:2629-2637 | src/Plotly.NET/Traces/Trace2D.fs:2783-2791 | src/Plotly.NET/Traces/Trace2D.fs:2911-2919 | src/Plotly.NET/Traces/Trace3D.fs:331-339 | src/Plotly.NET/Traces/Trace3D.fs:521-529 | src/Plotly.NET/Traces/Trace3D.fs:706-714 | src/Plotly.NET/Traces/Trace3D.fs:883-891 | src/Plotly.NET/Traces/Trace3D.fs:1063-1071 | src/Plotly.NET/Traces/Trace3D.fs:1244-1252 | src/Plotly.NET/Traces/TraceCarpet.fs:246-254 | src/Plotly.NET/Traces/TraceCarpet.fs:391-399 | src/Plotly.NET/Traces/TraceGeo.fs:276-284 | src/Plotly.NET/Traces/TraceMapbox.fs:404-412 | src/Plotly.NET/Traces/TracePolar.fs:143-151 | src/Plotly.NET/Traces/TracePolar.fs:282-290 | src/Plotly.NET/Traces/TraceSmith.fs:115-123 | src/Plotly.NET/Traces/TraceTernary.fs:120-128 — there are 28 copies across 8 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 28 sites; resolving a subset leaves the remainder to drift apart. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Plotly.NET/Traces/Trace2D.fs:492` calls `withOptionalSingleOrMultiProperty` and `src/Plotly.NET/Traces/Trace2D.fs:2285` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9 lines × 26) src/Plotly.NET/Traces/Trace2D.fs:483— src/Plotly.NET/Traces/Trace2D.fs:483-491 | src/Plotly.NET/Traces/Trace2D.fs:685-693 | src/Plotly.NET/Traces/Trace2D.fs:897-905 | src/Plotly.NET/Traces/Trace2D.fs:1102-1110 | src/Plotly.NET/Traces/Trace2D.fs:1554-1562 | src/Plotly.NET/Traces/Trace2D.fs:1739-1747 | src/Plotly.NET/Traces/Trace2D.fs:1928-1936 | src/Plotly.NET/Traces/Trace2D.fs:2133-2141 | src/Plotly.NET/Traces/Trace2D.fs:2276-2284 | src/Plotly.NET/Traces/Trace2D.fs:2458-2466 | src/Plotly.NET/Traces/Trace2D.fs:2631-2639 | src/Plotly.NET/Traces/Trace2D.fs:2785-2793 | src/Plotly.NET/Traces/Trace2D.fs:2913-2921 | src/Plotly.NET/Traces/Trace3D.fs:333-341 | src/Plotly.NET/Traces/Trace3D.fs:523-531 | src/Plotly.NET/Traces/Trace3D.fs:708-716 | src/Plotly.NET/Traces/Trace3D.fs:885-893 | src/Plotly.NET/Traces/Trace3D.fs:1065-1073 | src/Plotly.NET/Traces/Trace3D.fs:1246-1254 | src/Plotly.NET/Traces/TraceCarpet.fs:393-401 | src/Plotly.NET/Traces/TraceDomain.fs:153-161 | src/Plotly.NET/Traces/TraceDomain.fs:286-294 | src/Plotly.NET/Traces/TraceDomain.fs:423-431 | src/Plotly.NET/Traces/TraceDomain.fs:566-574 | src/Plotly.NET/Traces/TraceMapbox.fs:406-414 | src/Plotly.NET/Traces/TracePolar.fs:284-292 — there are 26 copies across 6 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 26 sites; resolving a subset leaves the remainder to drift apart. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Plotly.NET/Traces/Trace2D.fs:1939` calls `withOptionalSingleOrMultiProperty` and `src/Plotly.NET/Traces/Trace2D.fs:494` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9 lines × 16) src/Plotly.NET/Traces/Trace.fs:730— src/Plotly.NET/Traces/Trace.fs:730-738 | src/Plotly.NET/Traces/Trace2D.fs:209-217 | src/Plotly.NET/Traces/Trace2D.fs:435-443 | src/Plotly.NET/Traces/Trace2D.fs:641-649 | src/Plotly.NET/Traces/Trace2D.fs:851-859 | src/Plotly.NET/Traces/Trace3D.fs:133-141 | src/Plotly.NET/Traces/TraceCarpet.fs:215-223 | src/Plotly.NET/Traces/TraceDomain.fs:120-128 | src/Plotly.NET/Traces/TraceDomain.fs:258-266 | src/Plotly.NET/Traces/TraceDomain.fs:532-540 | src/Plotly.NET/Traces/TraceDomain.fs:1025-1033 | src/Plotly.NET/Traces/TraceGeo.fs:247-255 | src/Plotly.NET/Traces/TraceMapbox.fs:115-123 | src/Plotly.NET/Traces/TracePolar.fs:112-120 | src/Plotly.NET/Traces/TraceSmith.fs:86-94 | src/Plotly.NET/Traces/TraceTernary.fs:89-97 — there are 16 copies across 10 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 16 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (9 lines × 15) src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Hierarchy.fs:73— src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Hierarchy.fs:73-81 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Hierarchy.fs:201-209 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Hierarchy.fs:331-339 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Hierarchy.fs:449-457 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Hierarchy.fs:579-587 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Hierarchy.fs:711-719 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Pie.fs:68-76 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Pie.fs:177-185 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Pie.fs:287-295 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Pie.fs:385-393 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Pie.fs:453-461 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Pie.fs:548-556 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Pie.fs:639-647 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Pie.fs:737-745 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Pie.fs:821-829 — before extracting anything, compare `src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Hierarchy.fs` and `src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Pie.fs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 57 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 10) src/Plotly.NET/Traces/Trace2D.fs:285— src/Plotly.NET/Traces/Trace2D.fs:285-293 | src/Plotly.NET/Traces/Trace2D.fs:510-518 | src/Plotly.NET/Traces/Trace2D.fs:709-717 | src/Plotly.NET/Traces/Trace2D.fs:1120-1128 | src/Plotly.NET/Traces/Trace2D.fs:1365-1373 | src/Plotly.NET/Traces/Trace2D.fs:1575-1583 | src/Plotly.NET/Traces/Trace2D.fs:1757-1765 | src/Plotly.NET/Traces/Trace2D.fs:1944-1952 | src/Plotly.NET/Traces/Trace2D.fs:2160-2168 | src/Plotly.NET/Traces/Trace2D.fs:2483-2491 — all 10 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Plotly.NET/Traces/Trace2D.fs:507` calls `withOptionalSingleOrMultiPropertyBy`, `withOptionalSingleOrMultiProperty` and `src/Plotly.NET/Traces/Trace2D.fs:1363` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8–9 lines × 7) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:602— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:602-610 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:520-528 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Hierarchy.fs:567-574 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Pie.fs:812-819 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:648-656 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:411-419 | src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:390-398 — `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs` and `src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 8 separate duplicated blocks between them, totalling at least 101 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (9 lines × 4) src/Plotly.NET/Traces/TraceMapbox.fs:119— src/Plotly.NET/Traces/TraceMapbox.fs:119-127 | src/Plotly.NET/Traces/TraceMapbox.fs:246-254 | src/Plotly.NET/Traces/TraceMapbox.fs:379-387 | src/Plotly.NET/Traces/TraceTernary.fs:93-101 — before extracting anything, compare `src/Plotly.NET/Traces/TraceMapbox.fs` and `src/Plotly.NET/Traces/TraceTernary.fs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 112 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (8–9 lines × 3) src/Plotly.NET.ImageExport/ChartExtensions.fs:75— src/Plotly.NET.ImageExport/ChartExtensions.fs:75-83 | src/Plotly.NET.ImageExport/ChartExtensions.fs:161-168 | src/Plotly.NET.ImageExport/ChartExtensions.fs:246-253 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (8 lines × 9) src/Plotly.NET/Traces/Trace2D.fs:284— src/Plotly.NET/Traces/Trace2D.fs:284-291 | src/Plotly.NET/Traces/Trace2D.fs:509-516 | src/Plotly.NET/Traces/Trace2D.fs:708-715 | src/Plotly.NET/Traces/Trace2D.fs:1119-1126 | src/Plotly.NET/Traces/Trace2D.fs:1364-1371 | src/Plotly.NET/Traces/Trace2D.fs:1574-1581 | src/Plotly.NET/Traces/Trace2D.fs:2159-2166 | src/Plotly.NET/Traces/Trace2D.fs:2482-2489 | src/Plotly.NET/Traces/Trace2D.fs:2925-2932 — all 9 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Plotly.NET/Traces/Trace2D.fs:282` calls `withOptionalSingleOrMultiPropertyBy`, `withOptionalSingleOrMultiProperty` and `src/Plotly.NET/Traces/Trace2D.fs:1363` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (7–8 lines × 6) src/Plotly.NET.ImageExport/ChartExtensions.fs:34— src/Plotly.NET.ImageExport/ChartExtensions.fs:34-41 | src/Plotly.NET.ImageExport/ChartExtensions.fs:77-84 | src/Plotly.NET.ImageExport/ChartExtensions.fs:120-127 | src/Plotly.NET.ImageExport/ChartExtensions.fs:163-169 | src/Plotly.NET.ImageExport/ChartExtensions.fs:206-212 | src/Plotly.NET.ImageExport/ChartExtensions.fs:248-254 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET.ImageExport/ChartExtensions.fs:34` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 6) src/Plotly.NET/Traces/Trace3D.fs:669— src/Plotly.NET/Traces/Trace3D.fs:669-676 | src/Plotly.NET/Traces/Trace3D.fs:846-853 | src/Plotly.NET/Traces/Trace3D.fs:1020-1027 | src/Plotly.NET/Traces/Trace3D.fs:1201-1208 | src/Plotly.NET/Traces/TraceMapbox.fs:376-383 | src/Plotly.NET/Traces/TracePolar.fs:259-266 — there are 6 copies across 3 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 6 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (7 lines × 8) src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Hierarchy.fs:439— src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Hierarchy.fs:439-445 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Hierarchy.fs:569-575 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Hierarchy.fs:701-707 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Icicle.fs:68-74 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Icicle.fs:212-218 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Icicle.fs:355-361 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Pie.fs:730-736 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Pie.fs:814-820 — before extracting anything, compare `src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Hierarchy.fs` and `src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Icicle.fs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 87 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 15) src/Plotly.NET/Traces/Trace2D.fs:280— src/Plotly.NET/Traces/Trace2D.fs:280-285 | src/Plotly.NET/Traces/Trace2D.fs:505-510 | src/Plotly.NET/Traces/Trace2D.fs:704-709 | src/Plotly.NET/Traces/Trace2D.fs:920-925 | src/Plotly.NET/Traces/Trace3D.fs:186-191 | src/Plotly.NET/Traces/TraceCarpet.fs:262-267 | src/Plotly.NET/Traces/TraceDomain.fs:169-174 | src/Plotly.NET/Traces/TraceDomain.fs:301-306 | src/Plotly.NET/Traces/TraceDomain.fs:581-586 | src/Plotly.NET/Traces/TraceDomain.fs:1072-1077 | src/Plotly.NET/Traces/TraceGeo.fs:295-300 | src/Plotly.NET/Traces/TraceMapbox.fs:160-165 | src/Plotly.NET/Traces/TracePolar.fs:164-169 | src/Plotly.NET/Traces/TraceSmith.fs:131-136 | src/Plotly.NET/Traces/TraceTernary.fs:138-143 — there are 15 copies across 9 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 15 sites; resolving a subset leaves the remainder to drift apart. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Plotly.NET/Traces/Trace2D.fs:917` calls `Measure` and `src/Plotly.NET/Traces/Trace2D.fs:502` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Third-party script without Subresource Integrity src/Plotly.NET/Globals.fs:86— `https://cdn.jsdelivr.net/npm/mathjax@3.2.0/es5/tex-svg.js` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session.
SC1 · Supply-chain hygiene· NuGet dependencies are not locked · ×1
NuGet dependencies are not locked — No packages.lock.json and no central package management — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 18 significant file(s) lose their only recent owner: src/Plotly.NET/Traces/Trace2D.fs, src/Plotly.NET/Traces/Trace3D.fs, src/Plotly.NET/Traces/TraceDomain.fs, src/Plotly.NET/CommonAbstractions/StyleParams.fs, src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs, src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs, src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs, src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs (+10 more). Pair on, review, or document these before any departure.
D28 · Secrets (history)· Rotate the exposed credentials · ×1
REDACTED
D34 · Knowledge Freshness· Orphaned files with no living knowledge · ×1
Orphaned files with no living knowledge — 1 of 191 analysed file(s) have no living knowledge left — their last meaningful change has decayed away, so if one breaks, no one currently understands it (counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 191 of the 244 production source files in this repository met that bar). None is large enough to earn a read-through of its own, so this row stands in for the per-file rows rather than raising one each — most significant first: src/Plotly.NET.ImageExport/AsyncHelper.fs. Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
Orphaned file src/Plotly.NET.ImageExport/AsyncHelper.fs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
M2 · Architecture documentation· No architecture diagram/doc · ×1
No architecture diagram/doc — No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
README/code drift src/Plotly.NET.ImageExport/README.md:11— src/Plotly.NET.ImageExport/README.md names .NET 6, but the projects target .NET 8, 10. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
No SAST REDACTED:6— No static application security testing detected. For this repository's stack, add `semgrep --config=auto` plus gitleaks for committed secrets (F# is not a CodeQL language and has no language-specific SAST engine) as a CI step. What was searched, so you can tell an absence from a miss: the 1 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
No dependency-update automation build/build.fsproj:22— `build/build.fsproj` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`.
Duplicated predicate src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:413— `TextPosition.IsSome || MultiTextPosition.IsSome` appears character-identically in 6 files — src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs, src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs, src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs, src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
Run 01a1d473-0bd4-7513-befa-0aceef07d66c · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 13 · Warnings: 497 · Recommendations: 13 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 13-11-2026 @ 10:27 UTC.
Downloadable artifacts
Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.