Public report — Plotly.NET, published 6 Aug 2026.
Concrete security findings (CVE IDs, secret matches, dependency versions) are hidden in this version;
ask the repo owner for the full report.
405findings with an exact file:lineof 410 — the remainder are repo-wide signals (a dimension-level measurement, not a single line); open any file:line and verify
41/97dimensions across the health lenses7789 LoC · 4 projects — wide & deep
Executive summary
Read through the Production lens — the standard calibration. *Green* means good enough to run in production. The score is absolute and comparable across repos.
plotly/Plotly.NET is sound in substance but carries real gaps (60%). It is not in crisis, but the issues below raise the cost of changing it — friction its consumers ultimately inherit.
It is strongest in Security (100%) — its security and compliance posture is in good shape. Code Health (96%) is solid too.
The area that most needs attention is Readiness (50%) — releases are harder to depend on — versioning, release notes and dependency hygiene are thin, so consumers can't easily tell what changed or trust an upgrade. Maturity (53%) is the next concern — onboarding is slow — key decisions and the architecture aren't written down, so contributors have to reverse-engineer the intent.
Leadership focus, highest impact first: Nothing pauses a release for a human (Deployment & Rollback); Stamp a version in your build/package manifest (e.g. csproj <Version> (Release Hygiene); Record significant decisions one document per decision (Architecture documentation).
For scale: Small (~7,789 production lines); rebuilding it from scratch would take roughly ~0.1 person-years (~1 engineer). Approximate, ±~30%.
Encouragingly, the gaps are in documentation and release process — not in the code's correctness, structure or security, which are strong. They're low-risk to close, and doing so would lift the grade without re-engineering anything that already works.
How the score is built — each lens's share of the headlineWidth is the lens's weight in the worst-heaviest fold (the weakest area pulls hardest); colour is that lens's own band. A lens fixes the score in proportion to its width.
This codebase represents roughly ~0.1 person-years of build effort (about ~€16,000 to rebuild). Its weakest lens is Readiness at 50% — the part of that asset most exposed by the findings below.
How we model this: boilerplate at a scaffolding rate + logic × domain Low (×0.9) — library/CLI × a 0.8× quality factor, at €60–95/h; indicative, ±~30% · size measured directly from source. Indicative only — most sensitive to the hourly rate and the domain tier (both tunable in config).
Top priorities
The highest-leverage moves; the full ranked list is in the Roadmap below.
1
Resolve the 2 redundant comment finding(s) in Comment Value — start with Program.cs (2).
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.
Stamp a version in your build/package manifest (e.g. csproj <Version>, package.json, pyproject.toml, Cargo.toml, or a VERSION file) or tag releases with semver so builds and releases are traceable.
Value concentrated against a weak lens · Medium · Value at risk
This is a Small asset (~0.1 person-years to rebuild), and its weakest lens is Readiness at 50%. The operational and business risk on an asset this size concentrates there — that's where remediation buys the most protection.
→ Direct remediation budget at Readiness first — highest risk-reduction per euro on an asset this size.
Highest-leverage move · Medium · Leverage
Of everything flagged, the best return on effort is: 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. The rest can wait behind it.
Evidence: priority ranking: top of 5 ranked by impact/effort
→ 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.
Architecture — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways — a layering smell or cycle. A clean layered graph has none.
Architecture — module dependency matrix
8 modules, 15 dependencies — 1 dependency cycle, shown as the red cell(s) above the diagonal. Rows and columns are the same modules, ordered so that a module only depends on ones above it. A cell means the row depends on the column, and its number is how many type pairs create that dependency. Read one thing: is anything above the diagonal? A mark there is a dependency cycle. (A cycle is all this shows — an unusual but cycle-free dependency sits below the diagonal like any other.)
First, implement draft releases or manual dispatch gates to prevent bad builds from reaching users, and ensure every release is stamped with a traceable version number. Next, document significant architectural decisions in a dedicated, discoverable location, and add a high-level 'How it works' section to the root README. Finally, resolve the two redundant comment findings in Program.cs to improve code clarity.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 2 redundant comment finding(s) in Comment Value — start with Program.cs (2).
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.
Stamp a version in your build/package manifest (e.g. csproj <Version>, package.json, pyproject.toml, Cargo.toml, or a VERSION file) or tag releases with semver so builds and releases are traceable.
Record significant decisions one document per decision — dated, stating the context, the decision and its consequences — and keep them together wherever your design docs already live (a conventional `docs/adr/` tree with `NNNN-title.md` names is the most discoverable form).
Adopt a consistent root-namespace convention (a shared prefix, e.g. Acme.*); short project-file/directory names are fine as long as the RootNamespace is uniform.
Introduce deliberate module boundaries — by feature (vertical slices) if your team prefers, or by layer (domain/application/infrastructure). Even splitting into a few cohesive projects with a clear dependency direction would help.
Watchdog 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. 38 of 41 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 3 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.6 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
Every figure here is one of three 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; ◐ Advisory — an LLM prose judgement. 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; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.
What we checked — 41 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, 405 of 410 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, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — 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
A clean run — every tool resolved and ran, and every applicable dimension was measured at full confidence. No scanner was unavailable, no analysis timed out or crashed, and nothing fell back to a degraded estimate.
When something does degrade — a missing scanner, a shallow clone, an LLM hiccup — it is named here explicitly and its exact cause recorded in diagnostics.md, never absorbed silently into the score.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does 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 (jscpd) — 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.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
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 — Watchdog runs 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 is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement.
D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
D24 Comment Value: Comment value (WHY vs WHAT) is an LLM judgement over a bounded sample — it is advisory and cannot weigh a comment against the precise code change it was written to explain.
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.
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.
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: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
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.
The LLM boundary
LLM-set scores this run (4): D19, D21, D24, M4 (model: Local LLM). For these, a model reads a bounded sample and sets the numeric score (documentation, ADR quality, naming, comment value, onboarding) — D25 sets the ADR-conformance fraction over sampled code, D22 judges API accuracy over a sample. These are sampled and advisory by design: they vary at the margins between runs and are never a deterministic measurement. Every other score in this report is tool-computed at confidence 1.0.
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.
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.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes7.8 / 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 27 FileTooLong finding(s) in God Classes — start with StyleParams.fs, Chart.fs, Trace2D.fs. — One of this dimension's main actionable groups (27 warning-level).
Resolve the 3 TooManyMethods finding(s) in God Classes — start with Chart.fs, Chart2D.cs, Layout.fs. — One of this dimension's main actionable groups (3 warning-level).
Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
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.
+ 50 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 46 Duplicated block (12 lines × 2) finding(s) in Code Duplication — start with ImaginaryAxis.fs (4), LinearAxis.fs (3), Chart2D_Heatmap.fs (3). — One of this dimension's main actionable groups (46 warning-level).
Resolve the 33 Duplicated block (15 lines × 2) finding(s) in Code Duplication — start with Chart2D_Histogram.fs (3), ChartPolar_Scatter.fs (3), ChartMap_Mapbox.fs (3). — One of this dimension's main actionable groups (33 warning-level).
Resolve the 31 Duplicated block (13 lines × 2) finding(s) in Code Duplication — start with Chart2D_Scatter.fs (4), Chart2D_Area.fs (3), ChartCarpet_Scatter.fs (3). — One of this dimension's main actionable groups (31 warning-level).
Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
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.
D9 · Test Distribution10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the test suite has a healthy mix of unit / integration / end-to-end tests.
Method: Test projects classified (Unit/Integration/BDD/E2E) from compiled metadata; test methods counted exhaustively across projects with placement-agnostic disk fallback. Deterministic.
8 test methods: 8 unit, 0 integration, 0 BDD, 0 e2e.
✓ On the Gold path — maintain.
Detailed fixes: d9_recommendation.md.
Do you agree with this assessment?
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 8 tests.
✓ 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.
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.
16 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.
Off-boarding risk: anonymized user #1
What to do
Resolve the 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
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.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Judged by language model at low temperature (0.0-0.1) on a deterministic doc sample (READMEs plus first 25 architecture docs), with two-pass stability filtering. Advisory, sampled.
The documentation is clear and complete for a .NET charting library. It starts with an excellent README that includes the project logo, build/test badge, NuGet metadata badges, a maintained-by-community banner, and a full table of contents listing What is Plotly.NET?, Installation, Documentation (Quick starts, Samples/tutorials, Full reference), Development (build/run tests/docs), Contributors, License, and FAQ. The test suite README explains the monorepo structure, testing frameworks used, how to run tests from build/cmd or VS Test Explorer, and a detailed folder breakdown plus an example of data initialization with #r references.
The What is Plotly.NET? section mentions a DOI paper but the link points to https://doi.org/10.12688/f1000research.123971.1, which does not exist.README.md
Resolve the 1 The What is Plotly.NET? section mentions a DOI paper but the link points… finding(s) in Documentation Quality — start with README.md. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d19_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether names — types, methods, variables — are clear and consistent.
Method: Judged by language model at low temperature (0.0-0.1) on a deterministic random symbol sample (fixed size, not exhaustive), with disclosed confidence band. Advisory, sampled.
0 naming inconsistencies across 200 sampled symbols.
✓ On the Gold path — maintain.
Detailed fixes: d21_recommendation.md.
Do you agree with this assessment?
D24 · Comment Value / 10Weak◐ Sampled · advisory
What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).
Method: Judged by language model at low temperature (0.0-0.1) on deterministically sampled inline comments with surrounding code; findings verified back to sampled comments by substring match. Advisory, sampled.
Resolve the 2 redundant comment finding(s) in Comment Value — start with Program.cs (2). — One of this dimension's main actionable groups (2 recommendation-level).
Detailed fixes: d24_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: Git-history secret scan via gitleaks detect over full history in an isolated checkout; each match flagged High. Exhaustive; degrades cleanly when tool absent.
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).
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 115 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.
Further orphaned files (smaller)
✓ On the Gold path — maintain.
Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.
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; coupling through a build step, config, or non-source file isn't seen.
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.
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.
What to do
The domain core is a small share of production code — check that business logic isn't leaking into the application/infrastructure layers (a thin domain is the anemic-domain smell).
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.
~7.8k production LoC (419 types) across 1 project(s) / 7 namespace(s) with no recognised architectural style or layering — at this size, deliberate module boundaries would help. No DDD/clean/vertical-slice/CQRS/transaction-script organisation was detected — code is likely organised ad hoc, which makes change and onboarding harder as it grows.
What to do
Introduce deliberate module boundaries — by feature (vertical slices) if your team prefers, or by layer (domain/application/infrastructure). Even splitting into a few cohesive projects with a clear dependency direction would help.
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.
Other · Code Health — Unfinished work detected by code SHAPE, not keywords: members that only throw a "not implemented" exception, methods that take inputs and return a constant, async methods that never await, dead `if (false)` / `#if false` branches, and skeleton types most of whose members are holes. A real, objective slice of technical debt.
Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
135 code files changed in the last 6 months but the README was not touched — it may no longer reflect the system.
What to do
Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
Add a README to the 4 of 4 project(s) that lack one — worth up to 2 pts.
Review the README against recent changes; refresh the parts that drifted.
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 `NNNN-title.md` documents 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/PlantUML/Mermaid diagram or architecture.md — the high-level shape isn't documented.
What to do
Record significant decisions one document per decision — dated, stating the context, the decision and its consequences — and keep them together wherever your design docs already live (a conventional `docs/adr/` tree with `NNNN-title.md` names is the most discoverable form).
Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
Maturity · Maturity — Whether the repo is organised deliberately — src/test separation and consistent project naming.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Only 1/4 projects share a common root namespace — the code's module identity is inconsistent.
What to do
Adopt a consistent root-namespace convention (a shared prefix, e.g. Acme.*); short project-file/directory names are fine as long as the RootNamespace is uniform.
Maturity · Maturity — Whether the README actually describes the code that exists (LLM-judged, advisory).
Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.
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 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 · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.
Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.
What to do
Stamp a version in your build/package manifest (e.g. csproj <Version>, package.json, pyproject.toml, Cargo.toml, or a VERSION file) or tag releases with semver so builds and releases are traceable.
Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.
Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
Other · Code Health — Whether log calls use message templates (queryable) rather than interpolated strings.
Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. Deterministic.
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.
Not included — 56 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.
AC7 A11y enforcement — 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.
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 — no packages were read
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.
D22 Internal API Consistency — No exposed public API
D23 Boundary Type-Coupling — At only 58k LoC the codebase is small despite four projects and no boundaries declared, so explicit bounded-context boundaries are not needed.
D25 ADR Conformance — no ADRs to check
D27 Navigability — No calls could be sampled, so navigability was not assessed — tracing effort is measured over resolved call sites and this target exposed none. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
D30 Dependency Vulnerabilities — the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan for NuGet CVEs — excluded rather than scored; re-run on an SDK that can restore this solution
D32 Data Compliance (PII/GDPR) — No PII/GDPR-handling patterns detected (p/gdpr ruleset) — no data-compliance surface to assess.
D33 JS/npm Dependency Vulnerabilities — No JS/npm manifest or lockfile found outside build output (package.json, package-lock.json, yarn.lock, pnpm-lock.yaml, bun.lockb); no JS dependencies to scan.
D36 Supply-chain Provenance & Signing — The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release).
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.
D38 OSV Dependency Vulnerabilities — No supported non-.NET dependency lockfile found outside build output (npm package-lock/yarn/pnpm/bun, Go go.mod, Rust Cargo.lock, Maven pom.xml, Gradle lockfiles, Python requirements.txt/poetry.lock/Pipfile.lock/pdm.lock, PHP composer.lock, Ruby Gemfile.lock, Elixir mix.lock, Dart pubspec.lock, Swift Package.resolved); nothing for OSV to scan. A NuGet-only repo stays NotApplicable — .NET CVEs are D30's domain.
D39 IL Efficiency — The target did not build, so no IL was available to measure.
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.
D6 Cohesion (LCOM4) — Cohesion (LCOM4) is measured over a C#/VB class graph, and this repository's production source is mostly .fs, which this pass does not read, so cohesion was not assessed for this repository. Not scored — this is a gap in the analyzer, not a finding about this repository.
D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
D8 Code Coverage — Coverage not measured — test suite did not build
DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 6 value object(s); 5 domain event(s)
ED1 Event-Driven — not scored — this repository shows none of the 3 signals this check 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 check looks for
P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, 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.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
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 — no coverage report found on disk — produce a coverage report in a standard format (Cobertura — `dotnet test --collect:"XPlat Code Coverage"` with a `coverlet.collector` PackageReference) into the repo working tree before the scan — a CI step is the usual place, since the artefact is commonly gitignored, or wire coverage collection into CI, to enable this cross-layer check
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 — 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.
PF3 Async & latency hygiene — 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.
S1 Web-Security Posture — No web surface detected in the analyzed source — no HTTP API or web-UI project (no controllers/minimal-API endpoints, no Razor/Blazor views) and no web middleware (HTTPS redirection, HSTS, security headers, cookies). Transport security, security headers, secure cookies, CSRF/input-validation and middleware-order controls are therefore N/A here — this is a library/CLI/worker, not a web app. Crypto hygiene was still checked and found nothing to flag. If this codebase becomes web-facing, the dimension reactivates automatically.
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X2 Cancellation propagation — no async methods found
X6 Hand-rolled structured-format parsing — Reported, not scored — this card publishes what it found rather than grading it. Its content is the findings and the key metric above.
X7 Silent fallback defaults — Reported, not scored — this card publishes what it found rather than grading it. Its content is the findings and the key metric above.
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 (12 lines × 2) src/Plotly.NET/CommonAbstractions/ColorBar.fs:61— src/Plotly.NET/CommonAbstractions/ColorBar.fs:61-72 | src/Plotly.NET/CommonAbstractions/ColorBar.fs:209-220 — 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/CommonAbstractions/ColorBar.fs:61` 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/CommonAbstractions/ColorBar.fs:111— src/Plotly.NET/CommonAbstractions/ColorBar.fs:111-122 | src/Plotly.NET/ChartAPI/Chart.fs:752-763 — 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/CommonAbstractions/Line.fs:58— src/Plotly.NET/CommonAbstractions/Line.fs:58-69 | src/Plotly.NET/Traces/Trace.fs:506-517 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/CommonAbstractions/Line.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 (12 lines × 2) src/Plotly.NET/Layout/ObjectAbstractions/Common/LayoutImage.fs:13— src/Plotly.NET/Layout/ObjectAbstractions/Common/LayoutImage.fs:13-24 | src/Plotly.NET/Layout/ObjectAbstractions/Common/LayoutImage.fs:50-61 — 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/LayoutImage.fs:13` 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/Layout/ObjectAbstractions/Common/RangeSelector.fs:14— src/Plotly.NET/Layout/ObjectAbstractions/Common/RangeSelector.fs:14-25 | src/Plotly.NET/Layout/ObjectAbstractions/Common/RangeSelector.fs:43-54 — 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/RangeSelector.fs:14` 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/Layout/ObjectAbstractions/Common/NewShape.fs:61— src/Plotly.NET/Layout/ObjectAbstractions/Common/NewShape.fs:61-72 | src/Plotly.NET/Layout/ObjectAbstractions/Common/NewShape.fs:113-124 — 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/NewShape.fs:61` 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/Layout/ObjectAbstractions/Common/Shape.fs:76— src/Plotly.NET/Layout/ObjectAbstractions/Common/Shape.fs:76-87 | src/Plotly.NET/Layout/ObjectAbstractions/Common/Shape.fs:170-181 — 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/Shape.fs:76` 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/Layout/ObjectAbstractions/Common/Selection.fs:27— src/Plotly.NET/Layout/ObjectAbstractions/Common/Selection.fs:27-38 | src/Plotly.NET/Layout/ObjectAbstractions/Common/Selection.fs:73-84 — 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/Selection.fs:27` 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/Layout/ObjectAbstractions/Common/Annotation.fs:24— src/Plotly.NET/Layout/ObjectAbstractions/Common/Annotation.fs:24-35 | src/Plotly.NET/Layout/ObjectAbstractions/Common/Annotation.fs:115-126 — 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/Layout/ObjectAbstractions/Common/LayoutGrid.fs:43— src/Plotly.NET/Layout/ObjectAbstractions/Common/LayoutGrid.fs:43-54 | src/Plotly.NET/ChartAPI/Chart.fs:2507-2518 — 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/Layout/ObjectAbstractions/Common/Legend.fs:70— src/Plotly.NET/Layout/ObjectAbstractions/Common/Legend.fs:70-81 | src/Plotly.NET/ChartAPI/Chart.fs:2622-2633 — 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/Layout/ObjectAbstractions/Common/Minor.fs:29— src/Plotly.NET/Layout/ObjectAbstractions/Common/Minor.fs:29-40 | src/Plotly.NET/Layout/ObjectAbstractions/Common/Minor.fs:78-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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/Layout/ObjectAbstractions/Common/Minor.fs:29` 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/Layout/ObjectAbstractions/Common/LinearAxis.fs:160— src/Plotly.NET/Layout/ObjectAbstractions/Common/LinearAxis.fs:160-171 | src/Plotly.NET/Layout/ObjectAbstractions/Common/LinearAxis.fs:959-970 — 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/Layout/ObjectAbstractions/Common/LinearAxis.fs:224— src/Plotly.NET/Layout/ObjectAbstractions/Common/LinearAxis.fs:224-235 | src/Plotly.NET/Layout/ObjectAbstractions/Common/LinearAxis.fs:476-487 — 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/Layout/ObjectAbstractions/Common/LinearAxis.fs:252— src/Plotly.NET/Layout/ObjectAbstractions/Common/LinearAxis.fs:252-263 | src/Plotly.NET/Layout/ObjectAbstractions/Common/LinearAxis.fs:503-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.
Duplicated block (12 lines × 2) src/Plotly.NET/Layout/ObjectAbstractions/Common/UpdateMenu.fs:63— src/Plotly.NET/Layout/ObjectAbstractions/Common/UpdateMenu.fs:63-74 | src/Plotly.NET/Layout/ObjectAbstractions/Common/UpdateMenu.fs:103-114 — 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/UpdateMenu.fs:63` 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/Layout/ObjectAbstractions/Map/Geo.fs:81— src/Plotly.NET/Layout/ObjectAbstractions/Map/Geo.fs:81-92 | src/Plotly.NET/ChartAPI/Chart.fs:2067-2078 — 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/Layout/ObjectAbstractions/3D/Scene.fs:45— src/Plotly.NET/Layout/ObjectAbstractions/3D/Scene.fs:45-56 | src/Plotly.NET/ChartAPI/Chart.fs:1595-1606 — 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/Layout/ObjectAbstractions/Polar/AngularAxis.fs:69— src/Plotly.NET/Layout/ObjectAbstractions/Polar/AngularAxis.fs:69-80 | src/Plotly.NET/Layout/ObjectAbstractions/Polar/AngularAxis.fs:214-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.
Duplicated block (12 lines × 2) src/Plotly.NET/Layout/ObjectAbstractions/Polar/AngularAxis.fs:126— src/Plotly.NET/Layout/ObjectAbstractions/Polar/AngularAxis.fs:126-137 | src/Plotly.NET/Layout/ObjectAbstractions/Polar/RadialAxis.fs:142-153 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (12 lines × 2) src/Plotly.NET/Layout/ObjectAbstractions/Polar/RadialAxis.fs:79— src/Plotly.NET/Layout/ObjectAbstractions/Polar/RadialAxis.fs:79-90 | src/Plotly.NET/Layout/ObjectAbstractions/Polar/RadialAxis.fs:242-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.
Duplicated block (12 lines × 2) src/Plotly.NET/Layout/ObjectAbstractions/Smith/ImaginaryAxis.fs:41— src/Plotly.NET/Layout/ObjectAbstractions/Smith/ImaginaryAxis.fs:41-52 | src/Plotly.NET/Layout/ObjectAbstractions/Smith/RealAxis.fs:43-54 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. 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 (12 lines × 2) src/Plotly.NET/Layout/ObjectAbstractions/Smith/ImaginaryAxis.fs:69— src/Plotly.NET/Layout/ObjectAbstractions/Smith/ImaginaryAxis.fs:69-80 | src/Plotly.NET/Layout/ObjectAbstractions/Smith/RealAxis.fs:73-84 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (12 lines × 2) src/Plotly.NET/Layout/ObjectAbstractions/Smith/ImaginaryAxis.fs:124— src/Plotly.NET/Layout/ObjectAbstractions/Smith/ImaginaryAxis.fs:124-135 | src/Plotly.NET/Layout/ObjectAbstractions/Smith/RealAxis.fs:131-142 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/Layout/ObjectAbstractions/Smith/ImaginaryAxis.fs:124` 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/Layout/ObjectAbstractions/Smith/ImaginaryAxis.fs:139— src/Plotly.NET/Layout/ObjectAbstractions/Smith/ImaginaryAxis.fs:139-150 | src/Plotly.NET/Layout/ObjectAbstractions/Smith/RealAxis.fs:148-159 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. 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 (15 lines × 2) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1565— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1565-1579 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1683-1697 — 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:1565` 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/Chart2D/Chart2D_Scatter.fs:1913— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1913-1927 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:2104-2118 — 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:1913` 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/Chart2D/Chart2D_Bar.fs:128— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:128-142 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:582-596 — 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:128` 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/Chart2D/Chart2D_Bar.fs:324— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:324-338 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:779-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:324` 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/Chart2D/Chart2D_Histogram.fs:377— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Histogram.fs:377-391 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Histogram.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/Chart2D/Chart2D_Histogram.fs:377` 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/Chart2D/Chart2D_Histogram.fs:402— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Histogram.fs:402-416 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Histogram.fs:480-494 — 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:402` 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/Chart2D/Chart2D_Histogram.fs:703— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Histogram.fs:703-717 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Histogram.fs:844-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:703` 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/Chart2D/Chart2D_Distribution.fs:204— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Distribution.fs:204-218 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Distribution.fs:293-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:204` 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/Chart2D/Chart2D_Distribution.fs:630— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Distribution.fs:630-644 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Distribution.fs:737-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:630` 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/Chart2D/Chart2D_Heatmap.fs:90— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Heatmap.fs:90-104 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Heatmap.fs:171-185 — 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 (15 lines × 2) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Heatmap.fs:655— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Heatmap.fs:655-669 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Heatmap.fs:780-794 — 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:655` 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/Chart2D/Chart2D_Finance.fs:86— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:86-100 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:237-251 — 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 (15 lines × 2) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:386— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:386-400 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:537-551 — 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 (15 lines × 2) src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Surface.fs:226— src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Surface.fs:226-240 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Surface.fs:295-309 — 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.
Duplicated block (15 lines × 2) src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:93— src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:93-107 | 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.
Duplicated block (15 lines × 2) src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:394— src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:394-408 | 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.
Duplicated block (15 lines × 2) src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Volume.fs:73— src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Volume.fs:73-87 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Volume.fs:141-155 — 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:73` 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:102— src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:102-116 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:203-217 — 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:102` 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:363— src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:363-377 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:1109-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:363` 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:657— src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:657-671 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:926-940 — 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:657` 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_Mapbox.fs:128— src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:128-142 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:248-262 — 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:128` 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_Mapbox.fs:632— src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:632-646 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:700-714 — 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:632` 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_Mapbox.fs:917— src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:917-931 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:988-1002 — 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:917` 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:78— src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Density.fs:78-92 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Density.fs:153-167 — 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 (15 lines × 2) src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:823— src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:823-837 | src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:902-916 — 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/ChartTernary/ChartTernary_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 (13 lines × 2) src/Plotly.NET/Layout/ObjectAbstractions/Common/Slider/Slider.fs:65— src/Plotly.NET/Layout/ObjectAbstractions/Common/Slider/Slider.fs:65-77 | src/Plotly.NET/Layout/ObjectAbstractions/Common/Slider/Slider.fs:118-130 — 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/Slider/Slider.fs:65` 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/Map/Geo.fs:66— src/Plotly.NET/Layout/ObjectAbstractions/Map/Geo.fs:66-78 | src/Plotly.NET/Layout/ObjectAbstractions/Map/Geo.fs:167-179 — 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/Map/Geo.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 (13 lines × 2) src/Plotly.NET/Traces/Trace2D.fs:471— src/Plotly.NET/Traces/Trace2D.fs:471-483 | src/Plotly.NET/Traces/Trace2D.fs:1090-1102 — 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/Trace2D.fs:471` 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 × 2) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:240— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:240-252 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:348-360 — 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_Scatter.fs:453— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:453-465 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1763-1775 — 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_Scatter.fs:530— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:530-543 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:615-627 — 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:530` 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 × 2) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1427— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1427-1439 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:645-657 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (13 lines × 2) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:110— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:110-122 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:220-232 — 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_Area.fs:295— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:295-307 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:630-642 — 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:295` 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 × 2) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:442— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:442-454 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:556-568 — 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_Funnel.fs:620— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Funnel.fs:620-632 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Funnel.fs:706-718 — 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 (13 lines × 2) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Distribution.fs:73— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Distribution.fs:73-85 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Distribution.fs:362-374 — 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:73` 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 × 2) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:140— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:140-152 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:283-295 — 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:140` 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 × 2) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:196— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:196-208 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:496-508 — 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 (13 lines × 2) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Splom.fs:143— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Splom.fs:143-155 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Splom.fs:212-224 — 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 (13 lines × 2) src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Surface.fs:78— src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Surface.fs:78-91 | 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.
Duplicated block (13 lines × 2) src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:115— src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:115-127 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:416-428 — 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 (13 lines × 2) src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Volume.fs:88— src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Volume.fs:88-100 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Volume.fs:249-261 — 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_Volume.fs:156— src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Volume.fs:156-168 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Volume.fs:315-327 — 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/ChartPolar/ChartPolar_Scatter.fs:674— src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:674-686 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:955-967 — 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 (13 lines × 2) src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Bar.fs:75— src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Bar.fs:75-87 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Bar.fs:230-242 — 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_Bar.fs:75` 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/ChartMap/ChartMap_Geo.fs:412— src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:412-424 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:1059-1071 — 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:412` 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 × 2) src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:608— src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:608-621 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:662-674 — 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 (13 lines × 2) src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:410— src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:410-423 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:544-556 — 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: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 (13 lines × 2) src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Density.fs:230— src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Density.fs:230-242 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Density.fs:368-380 — 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:230` 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/Layout/ObjectAbstractions/Polar/AngularAxis.fs:277— src/Plotly.NET/Layout/ObjectAbstractions/Polar/AngularAxis.fs:277-286 | src/Plotly.NET/Layout/ObjectAbstractions/Polar/RadialAxis.fs:310-319 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (10 lines × 2) src/Plotly.NET/Layout/ObjectAbstractions/Smith/ImaginaryAxis.fs:152— src/Plotly.NET/Layout/ObjectAbstractions/Smith/ImaginaryAxis.fs:152-161 | src/Plotly.NET/Layout/ObjectAbstractions/Smith/RealAxis.fs:161-170 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (10 lines × 2) src/Plotly.NET/Traces/ObjectAbstractions/Table.fs:27— src/Plotly.NET/Traces/ObjectAbstractions/Table.fs:27-36 | src/Plotly.NET/Traces/ObjectAbstractions/Table.fs:59-68 — 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/Table.fs:27` 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/Traces/ObjectAbstractions/Sankey.fs:125— src/Plotly.NET/Traces/ObjectAbstractions/Sankey.fs:125-134 | src/Plotly.NET/Traces/ObjectAbstractions/Sankey.fs:160-169 — 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/Sankey.fs:125` 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/Traces/Trace2D.fs:1271— src/Plotly.NET/Traces/Trace2D.fs:1271-1280 | src/Plotly.NET/Traces/Trace2D.fs:1506-1515 — 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 (10 lines × 2) src/Plotly.NET/Traces/Trace2D.fs:1768— src/Plotly.NET/Traces/Trace2D.fs:1768-1777 | src/Plotly.NET/Traces/Trace2D.fs:1955-1964 — 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 (10 lines × 2) src/Plotly.NET/Traces/Trace2D.fs:1966— src/Plotly.NET/Traces/Trace2D.fs:1966-1975 | src/Plotly.NET/Traces/Trace2D.fs:2499-2508 — 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 (10 lines × 2) src/Plotly.NET/Traces/Trace2D.fs:2176— src/Plotly.NET/Traces/Trace2D.fs:2176-2185 | src/Plotly.NET/Traces/Trace2D.fs:2500-2509 — 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 (10 lines × 2) src/Plotly.NET/Traces/Trace2D.fs:2597— src/Plotly.NET/Traces/Trace2D.fs:2597-2606 | src/Plotly.NET/Traces/Trace2D.fs:2751-2760 — 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 (10 lines × 2) src/Plotly.NET/Traces/Trace3D.fs:176— src/Plotly.NET/Traces/Trace3D.fs:176-185 | src/Plotly.NET/Traces/Trace3D.fs:339-348 — 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 (10 lines × 2) src/Plotly.NET/Traces/Trace3D.fs:671— src/Plotly.NET/Traces/Trace3D.fs:671-680 | src/Plotly.NET/Traces/Trace3D.fs:848-857 — 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 (10 lines × 2) src/Plotly.NET/Traces/TracePolar.fs:100— src/Plotly.NET/Traces/TracePolar.fs:100-109 | src/Plotly.NET/Traces/TracePolar.fs:244-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.
Duplicated block (10 lines × 2) src/Plotly.NET/Traces/TracePolar.fs:176— src/Plotly.NET/Traces/TracePolar.fs:176-185 | src/Plotly.NET/Traces/TraceTernary.fs:149-158 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (10 lines × 2) src/Plotly.NET/Traces/TraceGeo.fs:281— src/Plotly.NET/Traces/TraceGeo.fs:281-290 | src/Plotly.NET/Traces/TraceMapbox.fs:148-157 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (10 lines × 2) src/Plotly.NET/Traces/TraceMapbox.fs:121— src/Plotly.NET/Traces/TraceMapbox.fs:121-130 | src/Plotly.NET/Traces/TraceTernary.fs:95-104 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (10 lines × 2) src/Plotly.NET/Traces/TraceMapbox.fs:167— src/Plotly.NET/Traces/TraceMapbox.fs:167-176 | src/Plotly.NET/Traces/TraceTernary.fs:145-154 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (10 lines × 2) src/Plotly.NET/Traces/TraceMapbox.fs:407— src/Plotly.NET/Traces/TraceMapbox.fs:407-416 | src/Plotly.NET/Traces/TraceCarpet.fs:394-403 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (10 lines × 2) src/Plotly.NET/Traces/TraceTernary.fs:125— src/Plotly.NET/Traces/TraceTernary.fs:125-134 | src/Plotly.NET/Traces/TraceCarpet.fs:251-260 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (10 lines × 2) src/Plotly.NET/Traces/TraceDomain.fs:146— src/Plotly.NET/Traces/TraceDomain.fs:146-155 | src/Plotly.NET/Traces/TraceDomain.fs:415-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/Traces/TraceDomain.fs:146` 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/TraceDomain.fs:424— src/Plotly.NET/Traces/TraceDomain.fs:424-433 | src/Plotly.NET/Traces/TraceDomain.fs:567-576 — 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 (10 lines × 2) src/Plotly.NET/Traces/TraceDomain.fs:653— src/Plotly.NET/Traces/TraceDomain.fs:653-662 | src/Plotly.NET/Traces/TraceDomain.fs:801-811 — 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 lines × 2) src/Plotly.NET/Templates/ChartTemplates.fs:137— src/Plotly.NET/Templates/ChartTemplates.fs:137-146 | src/Plotly.NET/Templates/ChartTemplates.fs:156-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.
Duplicated block (10 lines × 2) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Heatmap.fs:306— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Heatmap.fs:306-315 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Heatmap.fs:410-419 — 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 (10 lines × 2) src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:507— src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:507-516 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:583-592 — 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 (10 lines × 2) src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:534— src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:534-543 | src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:602-611 — 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/Map/MapboxLayer.fs:16— src/Plotly.NET/Layout/ObjectAbstractions/Map/MapboxLayer.fs:16-26 | src/Plotly.NET/Layout/ObjectAbstractions/Map/MapboxLayer.fs:59-69 — 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/Map/MapboxLayer.fs:16` 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/Layout/ObjectAbstractions/Polar/RadialAxis.fs:106— src/Plotly.NET/Layout/ObjectAbstractions/Polar/RadialAxis.fs:106-116 | src/Plotly.NET/Layout/ObjectAbstractions/Polar/RadialAxis.fs:269-279 — 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/RealAxis.fs:48— src/Plotly.NET/Layout/ObjectAbstractions/Smith/RealAxis.fs:48-58 | src/Plotly.NET/Layout/ObjectAbstractions/Smith/RealAxis.fs:136-146 — 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/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/ObjectAbstractions/Contours.fs:106— src/Plotly.NET/Traces/ObjectAbstractions/Contours.fs:106-116 | src/Plotly.NET/Traces/ObjectAbstractions/Contours.fs:150-160 — 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:452— src/Plotly.NET/Traces/Trace2D.fs:452-462 | src/Plotly.NET/Traces/Trace2D.fs:658-668 — 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:679— src/Plotly.NET/Traces/Trace2D.fs:679-689 | src/Plotly.NET/Traces/TraceCarpet.fs:112-122 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. 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 (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:2269— src/Plotly.NET/Traces/Trace2D.fs:2269-2279 | src/Plotly.NET/Traces/Trace2D.fs:2906-2916 — 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/Trace2D.fs:2269` 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/Trace2D.fs:2624— src/Plotly.NET/Traces/Trace2D.fs:2624-2634 | src/Plotly.NET/Traces/Trace2D.fs:2778-2788 — 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/Trace2D.fs:2624` 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/TracePolar.fs:124— src/Plotly.NET/Traces/TracePolar.fs:124-134 | src/Plotly.NET/Traces/TraceSmith.fs:97-107 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (11 lines × 2) src/Plotly.NET/Traces/TraceGeo.fs:131— src/Plotly.NET/Traces/TraceGeo.fs:131-141 | src/Plotly.NET/Traces/TraceGeo.fs:270-280 — 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/TraceGeo.fs:131` 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/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 (11 lines × 2) src/Plotly.NET/Traces/TraceMapbox.fs:253— src/Plotly.NET/Traces/TraceMapbox.fs:253-263 | src/Plotly.NET/Traces/TraceMapbox.fs:386-396 — 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/TraceTernary.fs:105— src/Plotly.NET/Traces/TraceTernary.fs:105-115 | src/Plotly.NET/Traces/TraceSmith.fs:102-112 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. 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 × 2) src/Plotly.NET/ChartAPI/GenericChart.fs:291— src/Plotly.NET/ChartAPI/GenericChart.fs:291-301 | src/Plotly.NET/ChartAPI/GenericChart.fs:344-354 — 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/Chart2D/Chart2D_Bar.fs:299— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:299-309 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:754-764 — 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:299` 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/ChartAPI/Chart2D/Chart2D_Bar.fs:354— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:354-364 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:809-819 — 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: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 (11 lines × 2) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Heatmap.fs:731— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Heatmap.fs:731-741 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Contour.fs:155-165 — 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 (11 lines × 2) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:278— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:278-288 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:578-588 — 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 (11 lines × 2) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:300— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:300-310 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:603-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 (11 lines × 2) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Statistical.fs:429— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Statistical.fs:429-439 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Statistical.fs:550-560 — 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:209— src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:209-219 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:279-289 — 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:209` 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 (11 lines × 2) src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:489— src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:489-499 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:1247-1257 — 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:489` 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 (11 lines × 2) src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Bar.fs:57— src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Bar.fs:57-67 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Bar.fs:139-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/ChartPolar/ChartPolar_Bar.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. 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.
FileTooLong: CommonAbstractions/StyleParams.fs src/Plotly.NET/CommonAbstractions/StyleParams.fs:0— FileTooLong — 3112 significant lines (blank, comment-only and punctuation-only lines excluded). 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:0— FileTooLong — 2066 significant lines (blank, comment-only and punctuation-only lines excluded). 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:0— FileTooLong — 1857 significant lines (blank, comment-only and punctuation-only lines excluded). 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/Chart2D.cs src/Plotly.NET.CSharp/ChartAPI/Chart2D.cs:0— FileTooLong — 1744 significant lines (blank, comment-only and punctuation-only lines excluded). 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:0— FileTooLong — 1482 significant lines (blank, comment-only and punctuation-only lines excluded). 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:0— FileTooLong — 968 significant lines (blank, comment-only and punctuation-only lines excluded). 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:0— FileTooLong — 871 significant lines (blank, comment-only and punctuation-only lines excluded). 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:0— FileTooLong — 851 significant lines (blank, comment-only and punctuation-only lines excluded). 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:0— FileTooLong — 823 significant lines (blank, comment-only and punctuation-only lines excluded). 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:0— FileTooLong — 777 significant lines (blank, comment-only and punctuation-only lines excluded). 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:0— FileTooLong — 730 significant lines (blank, comment-only and punctuation-only lines excluded). 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:0— FileTooLong — 719 significant lines (blank, comment-only and punctuation-only lines excluded). 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:0— FileTooLong — 703 significant lines (blank, comment-only and punctuation-only lines excluded). 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:0— FileTooLong — 674 significant lines (blank, comment-only and punctuation-only lines excluded). 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:0— FileTooLong — 665 significant lines (blank, comment-only and punctuation-only lines excluded). 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:0— FileTooLong — 637 significant lines (blank, comment-only and punctuation-only lines excluded). 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:0— FileTooLong — 616 significant lines (blank, comment-only and punctuation-only lines excluded). 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:0— FileTooLong — 607 significant lines (blank, comment-only and punctuation-only lines excluded). 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:0— FileTooLong — 602 significant lines (blank, comment-only and punctuation-only lines excluded). 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:0— FileTooLong — 589 significant lines (blank, comment-only and punctuation-only lines excluded). 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:0— FileTooLong — 551 significant lines (blank, comment-only and punctuation-only lines excluded). 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/ChartDomain.cs src/Plotly.NET.CSharp/ChartAPI/ChartDomain.cs:0— FileTooLong — 542 significant lines (blank, comment-only and punctuation-only lines excluded). 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/ChartMap.cs src/Plotly.NET.CSharp/ChartAPI/ChartMap.cs:0— FileTooLong — 539 significant lines (blank, comment-only and punctuation-only lines excluded). 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:0— FileTooLong — 533 significant lines (blank, comment-only and punctuation-only lines excluded). 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/Chart3D.cs src/Plotly.NET.CSharp/ChartAPI/Chart3D.cs:0— FileTooLong — 512 significant lines (blank, comment-only and punctuation-only lines excluded). 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 (14 lines × 2) src/Plotly.NET/CommonAbstractions/Title.fs:27— src/Plotly.NET/CommonAbstractions/Title.fs:27-40 | src/Plotly.NET/CommonAbstractions/Title.fs:75-88 — 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/Chart.fs:3398— src/Plotly.NET/ChartAPI/Chart.fs:3398-3411 | src/Plotly.NET/ChartAPI/Chart.fs:3418-3431 — 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_Scatter.fs:1874— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1874-1888 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:2066-2079 — 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:1874` 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_Area.fs:733— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:733-746 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:835-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/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 (14 lines × 2) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Funnel.fs:250— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Funnel.fs:250-263 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Funnel.fs:312-325 — 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:250` 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_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_Bar.fs:36— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:36-49 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:513-526 — 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:36` 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_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_Bar.fs:374— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:374-387 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:829-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:374` 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:232— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:232-245 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:532-545 — 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_Scatter.fs:404— src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:404-418 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:534-547 — 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: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 (14 lines × 2) src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:626— src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:626-639 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:790-804 — 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:626` 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/Chart3D/Chart3D_Scatter.fs:736— src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:736-749 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:737-750 — 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 (14 lines × 2) src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:924— src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:924-938 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:1002-1015 — 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.
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/Chart3D/Chart3D_Volume.fs:51— src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Volume.fs:51-64 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Volume.fs:213-226 — 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 (14 lines × 2) src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:1039— src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:1039-1052 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:1033-1046 — 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 (14 lines × 2) src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:1122— src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:1122-1135 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:1182-1195 — 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:1122` 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/ChartMap/ChartMap_Geo.fs:47— src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:47-60 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:107-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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:47` 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_Geo.fs:1276— src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:1276-1290 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:1343-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:1276` 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/ChartCarpet/ChartCarpet_Contour.fs:108— src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Contour.fs:108-121 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Contour.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_Contour.fs:108` 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/Chart.fs:1245— src/Plotly.NET/ChartAPI/Chart.fs:1245-1260 | src/Plotly.NET/ChartAPI/Chart.fs:1507-1522 — 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:1245` 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/Chart.fs:1861— src/Plotly.NET/ChartAPI/Chart.fs:1861-1876 | 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.
Duplicated block (16 lines × 2) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1544— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1544-1559 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1662-1677 — 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:1544` 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/Chart2D/Chart2D_Funnel.fs:38— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Funnel.fs:38-53 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Funnel.fs:143-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/ChartAPI/Chart2D/Chart2D_Funnel.fs:38` 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/Chart2D/Chart2D_Funnel.fs:74— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Funnel.fs:74-89 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Funnel.fs:179-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:74` 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/Chart2D/Chart2D_Funnel.fs:403— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Funnel.fs:403-418 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Funnel.fs:508-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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Funnel.fs:403` 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/Chart2D/Chart2D_Histogram.fs:196— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Histogram.fs:196-211 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Histogram.fs:287-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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Histogram.fs:196` 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/Chart3D/Chart3D_Scatter.fs:885— src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:885-900 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:963-978 — 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:885` 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/Chart3D/Chart3D_Surface.fs:54— src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Surface.fs:54-69 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Surface.fs:108-123 — 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:54` 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/Chart3D/Chart3D_Surface.fs:198— src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Surface.fs:198-213 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Surface.fs:266-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/ChartAPI/Chart3D/Chart3D_Surface.fs:198` 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/Chart3D/Chart3D_VectorField.fs:67— src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:67-82 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:130-145 — 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: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 (16 lines × 2) src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:222— src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:222-237 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:297-312 — 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 (16 lines × 2) src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:528— src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:528-543 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:606-621 — 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 (16 lines × 2) src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Volume.fs:254— src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Volume.fs:254-269 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Volume.fs:320-335 — 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 (16 lines × 2) src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:80— src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:80-95 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:181-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/ChartPolar/ChartPolar_Scatter.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 (16 lines × 2) src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:1245— src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:1245-1260 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:1312-1327 — 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:1245` 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/ChartMap/ChartMap_Mapbox.fs:100— src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:100-115 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:220-235 — 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:100` 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/ChartMap/ChartMap_Mapbox.fs:898— src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:898-913 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:969-984 — 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:898` 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/ChartCarpet/ChartCarpet_Scatter.fs:359— src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:359-374 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:412-427 — 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: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.
Duplicated block (16 lines × 2) src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:817— src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:817-832 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:903-918 — 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 (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/ChartAPI/ChartDomain/ChartDomain_Hierarchy.fs:132— src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Hierarchy.fs:132-147 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Hierarchy.fs:260-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: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 (16 lines × 2) src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:815— src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:815-830 | src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:886-901 — 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:815` 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/Layout/Layout.fs:391— src/Plotly.NET/Layout/Layout.fs:391-399 | src/Plotly.NET/ChartAPI/Chart.fs:967-975 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/Layout/Layout.fs:391` 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/Traces/ObjectAbstractions/Marker.fs:191— src/Plotly.NET/Traces/ObjectAbstractions/Marker.fs:191-199 | src/Plotly.NET/Traces/Trace.fs:405-413 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/Traces/ObjectAbstractions/Marker.fs:191` 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 (9 lines × 2) src/Plotly.NET/Traces/ObjectAbstractions/Sankey.fs:13— src/Plotly.NET/Traces/ObjectAbstractions/Sankey.fs:13-21 | src/Plotly.NET/Traces/ObjectAbstractions/Sankey.fs:48-56 — 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/Sankey.fs:13` 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:299— src/Plotly.NET/Traces/Trace2D.fs:299-307 | src/Plotly.NET/Traces/Trace2D.fs:1377-1385 — 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 (9 lines × 2) src/Plotly.NET/Traces/TraceMapbox.fs:294— src/Plotly.NET/Traces/TraceMapbox.fs:294-302 | src/Plotly.NET/Traces/TraceMapbox.fs:427-435 — 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/TraceTernary.fs:153— src/Plotly.NET/Traces/TraceTernary.fs:153-161 | src/Plotly.NET/Traces/TraceSmith.fs:146-154 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (9 lines × 2) src/Plotly.NET/Traces/TraceDomain.fs:375— src/Plotly.NET/Traces/TraceDomain.fs:375-383 | src/Plotly.NET/Traces/TraceDomain.fs:1011-1019 — 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/TraceDomain.fs:575— src/Plotly.NET/Traces/TraceDomain.fs:575-583 | src/Plotly.NET/Traces/TraceDomain.fs:1066-1074 — 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/Chart3D/Chart3D_Scatter.fs:466— src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:466-474 | src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:456-464 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:466` 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/ChartAPI/Chart3D/Chart3D_VectorField.fs:271— src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:271-279 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:580-588 — 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 (9 lines × 2) src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:60— src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:60-68 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:180-188 — 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/ChartTernary/ChartTernary_Scatter.fs:56— src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:56-64 | src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:158-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.
Duplicated block (9 lines × 2) src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:345— src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:345-353 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:473-481 — 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 (17 lines × 2) src/Plotly.NET/ChartAPI/Chart.fs:1696— src/Plotly.NET/ChartAPI/Chart.fs:1696-1712 | src/Plotly.NET/ChartAPI/Chart.fs:1752-1768 — 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:1696` 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_Scatter.fs:1937— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1937-1953 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:2128-2144 — 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:1937` 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_Histogram.fs:646— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Histogram.fs:646-662 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Histogram.fs:789-805 — 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:646` 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:67— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Heatmap.fs:67-83 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Heatmap.fs:150-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/Chart2D/Chart2D_Heatmap.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 (17 lines × 2) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Heatmap.fs:627— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Heatmap.fs:627-643 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Heatmap.fs:752-768 — 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:627` 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:59— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:59-75 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:211-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/Chart2D/Chart2D_Finance.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 (17 lines × 2) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:359— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:359-375 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Finance.fs:511-527 — 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: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.
Duplicated block (17 lines × 2) src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:367— src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:367-383 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:430-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/Chart3D/Chart3D_VectorField.fs:367` 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/Chart3D/Chart3D_Volume.fs:228— src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Volume.fs:228-244 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Volume.fs:294-310 — 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:228` 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/ChartPolar/ChartPolar_Scatter.fs:574— src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:574-590 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:840-856 — 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:574` 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/ChartPolar/ChartPolar_Scatter.fs:620— src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:620-636 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:888-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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:620` 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/ChartMap/ChartMap_Mapbox.fs:77— src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:77-93 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:197-213 — 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: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 (17 lines × 2) src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Contour.fs:75— src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Contour.fs:75-91 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Contour.fs:177-193 — 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: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 (17 lines × 2) src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Relations.fs:198— src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Relations.fs:198-215 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Relations.fs:274-290 — 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:198` 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 × 4) src/Plotly.NET/CommonAbstractions/Line.fs:35— src/Plotly.NET/CommonAbstractions/Line.fs:35-46 | src/Plotly.NET/CommonAbstractions/Line.fs:105-116 | src/Plotly.NET/Traces/Trace.fs:480-491 | src/Plotly.NET/ChartAPI/Chart.fs:343-354 — there are 4 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 4 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/CommonAbstractions/Line.fs:35` 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 × 4) src/Plotly.NET/Traces/ObjectAbstractions/Marker.fs:51— src/Plotly.NET/Traces/ObjectAbstractions/Marker.fs:51-62 | src/Plotly.NET/Traces/ObjectAbstractions/Marker.fs:163-174 | src/Plotly.NET/Traces/Trace.fs:377-388 | src/Plotly.NET/ChartAPI/Chart.fs:219-230 — there are 4 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 4 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/ObjectAbstractions/Marker.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 (12 lines × 4) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:818— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:818-829 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:933-944 | src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:573-584 | src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:640-651 — 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/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/Chart2D/Chart2D_Area.fs:326— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:326-337 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:441-452 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:555-566 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:662-673 — 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 (12 lines × 4) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Statistical.fs:147— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Statistical.fs:147-158 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Statistical.fs:330-341 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Statistical.fs:445-456 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Statistical.fs:566-577 — 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 (12 lines × 4) src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:308— src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:308-319 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:686-697 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:771-782 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:1051-1062 — 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 (12 lines × 4) src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:273— src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:273-284 | src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:707-718 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:1294-1305 | src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:958-970 — there are 4 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 4 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/ChartTernary/ChartTernary_Scatter.fs:273` 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 × 4) src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:301— src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:301-312 | src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:575-586 | src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:642-653 | src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:729-740 — 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 (12 lines × 3) src/Plotly.NET/Layout/ObjectAbstractions/Common/Legend.fs:41— src/Plotly.NET/Layout/ObjectAbstractions/Common/Legend.fs:41-52 | src/Plotly.NET/Layout/ObjectAbstractions/Common/Legend.fs:126-137 | src/Plotly.NET/ChartAPI/Chart.fs:2591-2602 — 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/Layout/ObjectAbstractions/Common/Legend.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 (12 lines × 3) src/Plotly.NET/Traces/Trace3D.fs:159— src/Plotly.NET/Traces/Trace3D.fs:159-171 | src/Plotly.NET/Traces/Trace3D.fs:324-335 | src/Plotly.NET/Traces/Trace3D.fs:513-525 — 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 (12 lines × 3) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:438— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:438-450 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1024-1035 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1413-1424 — 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:438` 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/Chart2D/Chart2D_Scatter.fs:548— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:548-559 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:632-643 | src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:416-427 — 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 (12 lines × 3) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1250— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1250-1261 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:495-506 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:906-917 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 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 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1250` 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_Splom.fs:50— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Splom.fs:50-61 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Splom.fs:129-140 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Splom.fs:197-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: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 (12 lines × 3) src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:440— src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:440-451 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:507-518 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:1266-1277 — 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 (12 lines × 3) src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:276— src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:276-287 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:725-736 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:1020-1031 — 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_Scatter.fs:276` 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 — 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 (13 lines × 3) src/Plotly.NET/Layout/Layout.fs:91— src/Plotly.NET/Layout/Layout.fs:91-103 | src/Plotly.NET/Layout/Layout.fs:323-335 | src/Plotly.NET/ChartAPI/Chart.fs:899-911 — 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/Layout/Layout.fs:91` 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/Traces/Trace.fs:554— src/Plotly.NET/Traces/Trace.fs:554-566 | src/Plotly.NET/Traces/Trace.fs:608-620 | src/Plotly.NET/Traces/Trace.fs:662-674 — 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:554` 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/Config/Config.fs:74— src/Plotly.NET/Config/Config.fs:74-86 | src/Plotly.NET/Config/Config.fs:222-234 | src/Plotly.NET/ChartAPI/Chart.fs:2903-2915 — 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/Config/Config.fs:74` 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:437— src/Plotly.NET/ChartAPI/Chart.fs:437-449 | src/Plotly.NET/ChartAPI/Chart.fs:512-524 | src/Plotly.NET/ChartAPI/Chart.fs:587-599 — 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:437` 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/Chart2D/Chart2D_Scatter.fs:1038— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1038-1050 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:310-322 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:949-961 — 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 (13 lines × 3) src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:284— src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:284-296 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:747-759 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:1026-1038 — 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: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 (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/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:760— src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:760-772 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:1074-1086 | src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:718-730 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 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 3 times.
Duplicated block (10 lines × 3) src/Plotly.NET/Traces/Trace3D.fs:139— src/Plotly.NET/Traces/Trace3D.fs:139-148 | src/Plotly.NET/Traces/Trace3D.fs:296-305 | src/Plotly.NET/Traces/Trace3D.fs:485-494 — 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 (10 lines × 3) src/Plotly.NET/Traces/TraceDomain.fs:265— src/Plotly.NET/Traces/TraceDomain.fs:265-274 | src/Plotly.NET/Traces/TraceDomain.fs:394-403 | src/Plotly.NET/Traces/TraceDomain.fs:539-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 (10 lines × 3) src/Plotly.NET/ChartAPI/Chart.fs:3036— src/Plotly.NET/ChartAPI/Chart.fs:3036-3045 | src/Plotly.NET/ChartAPI/Chart.fs:3354-3363 | src/Plotly.NET/ChartAPI/Chart.fs:3470-3480 — 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:3036` 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 × 3) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1390— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1390-1399 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:607-616 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:1009-1018 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 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 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1390` 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 × 3) src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:615— src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:615-624 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:683-692 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:780-789 — 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/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:465— src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:465-475 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:481-491 | src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:463-472 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 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 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:465` 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 (9 lines × 4) src/Plotly.NET/Traces/Trace2D.fs:520— src/Plotly.NET/Traces/Trace2D.fs:520-528 | src/Plotly.NET/Traces/Trace2D.fs:719-727 | src/Plotly.NET/Traces/Trace2D.fs:935-943 | src/Plotly.NET/Traces/Trace2D.fs:1375-1383 — 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 (9 lines × 4) src/Plotly.NET/Traces/TraceDomain.fs:126— src/Plotly.NET/Traces/TraceDomain.fs:126-134 | src/Plotly.NET/Traces/TraceDomain.fs:264-272 | src/Plotly.NET/Traces/TraceDomain.fs:393-401 | src/Plotly.NET/Traces/TraceDomain.fs:538-546 — 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 (9 lines × 4) src/Plotly.NET/Traces/TraceDomain.fs:173— src/Plotly.NET/Traces/TraceDomain.fs:173-181 | src/Plotly.NET/Traces/TraceDomain.fs:305-313 | src/Plotly.NET/Traces/TraceDomain.fs:441-449 | src/Plotly.NET/Traces/TraceDomain.fs:585-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.
Duplicated block (9 lines × 4) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1731— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1731-1739 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:1237-1245 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:1384-1392 | src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:943-951 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 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 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1731` 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 × 4) src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:692— src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:692-701 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:551-559 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:617-625 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:711-719 — 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 (9 lines × 4) src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Pie.fs:166— src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Pie.fs:166-174 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Pie.fs:276-284 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Pie.fs:442-450 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Pie.fs:537-545 — 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 (15 lines × 3) src/Plotly.NET/Traces/Trace.fs:569— src/Plotly.NET/Traces/Trace.fs:569-583 | src/Plotly.NET/Traces/Trace.fs:623-637 | src/Plotly.NET/Traces/Trace.fs:677-691 — 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:569` 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/Chart2D/Chart2D_Scatter.fs:145— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:145-159 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1194-1208 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1333-1347 — 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:145` 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:75— src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:75-89 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:194-208 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:313-327 — 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_Scatter.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. 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 × 3) src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:895— src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:895-909 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:965-979 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:1155-1169 — 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:895` 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/ChartTernary/ChartTernary_Scatter.fs:880— src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:880-894 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:1114-1128 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:1191-1205 — 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/ChartTernary/ChartTernary_Scatter.fs:880` 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 × 4) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:202— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:202-212 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:164-174 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:283-293 | src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:155-165 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 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 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.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.
Duplicated block (11 lines × 4) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:600— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:600-610 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:409-419 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:646-656 | src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:388-398 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 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 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:600` 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 × 4) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1615— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1615-1625 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:1156-1166 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:1295-1305 | src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:847-857 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 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 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1615` 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 × 4) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:217— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:217-227 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:431-441 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:672-682 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:886-896 — 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:217` 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 × 4) src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:350— src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:350-361 | src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:400-411 | src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:353-364 | src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:400-410 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.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 (11 lines × 3) src/Plotly.NET/Layout/ObjectAbstractions/3D/Scene.fs:29— src/Plotly.NET/Layout/ObjectAbstractions/3D/Scene.fs:29-39 | src/Plotly.NET/Layout/ObjectAbstractions/3D/Scene.fs:75-85 | src/Plotly.NET/ChartAPI/Chart.fs:1577-1587 — 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/Layout/ObjectAbstractions/3D/Scene.fs:29` 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/Traces/Trace2D.fs:1920— src/Plotly.NET/Traces/Trace2D.fs:1920-1930 | src/Plotly.NET/Traces/Trace2D.fs:2125-2135 | src/Plotly.NET/Traces/Trace2D.fs:2450-2460 — 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/Trace2D.fs:1920` 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 × 3) src/Plotly.NET/Traces/TraceDomain.fs:97— src/Plotly.NET/Traces/TraceDomain.fs:97-107 | src/Plotly.NET/Traces/TraceDomain.fs:237-247 | src/Plotly.NET/Traces/TraceDomain.fs:511-521 — 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 (11 lines × 3) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1110— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1110-1120 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:381-391 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:819-829 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 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 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1110` 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/ChartAPI/ChartDomain/ChartDomain_Pie.fs:389— src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Pie.fs:389-400 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Pie.fs:457-468 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Pie.fs:552-562 — 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:389` 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 (10 lines × 6) src/Plotly.NET/Traces/Trace2D.fs:211— src/Plotly.NET/Traces/Trace2D.fs:211-220 | src/Plotly.NET/Traces/Trace2D.fs:437-446 | src/Plotly.NET/Traces/Trace2D.fs:643-652 | src/Plotly.NET/Traces/Trace2D.fs:853-862 | src/Plotly.NET/Traces/Trace2D.fs:1051-1060 | src/Plotly.NET/Traces/Trace3D.fs:135-144 — 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 (10 lines × 6) src/Plotly.NET/Traces/Trace3D.fs:334— src/Plotly.NET/Traces/Trace3D.fs:334-343 | src/Plotly.NET/Traces/Trace3D.fs:524-533 | src/Plotly.NET/Traces/Trace3D.fs:709-718 | src/Plotly.NET/Traces/Trace3D.fs:886-895 | src/Plotly.NET/Traces/Trace3D.fs:1066-1075 | src/Plotly.NET/Traces/Trace3D.fs:1247-1256 — 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:362— src/Plotly.NET/Traces/Trace3D.fs:362-371 | src/Plotly.NET/Traces/Trace3D.fs:563-572 | src/Plotly.NET/Traces/Trace3D.fs:745-754 | src/Plotly.NET/Traces/Trace3D.fs:922-931 | src/Plotly.NET/Traces/Trace3D.fs:1096-1105 | src/Plotly.NET/Traces/Trace3D.fs:1277-1286 — 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. 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 (10 lines × 6) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:770— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:770-779 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:52-61 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:712-721 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:554-563 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:874-883 | src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:526-535 — there are 6 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 6 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_Scatter.fs:770` 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 × 6) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1002— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1002-1011 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:273-282 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:915-924 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:731-740 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:1043-1052 | src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:689-698 — there are 6 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 6 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_Scatter.fs:1002` 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/Templates/ChartTemplates.fs:427— src/Plotly.NET/Templates/ChartTemplates.fs:427-439 | src/Plotly.NET/Templates/ChartTemplates.fs:472-485 | src/Plotly.NET/Templates/ChartTemplates.fs:492-505 | src/Plotly.NET/Templates/ChartTemplates.fs:526-539 — 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/Templates/ChartTemplates.fs:427` 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 × 4) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:230— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:230-242 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:444-456 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:685-697 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:899-911 — 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/Chart2D/Chart2D_Distribution.fs:474— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Distribution.fs:474-486 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Distribution.fs:599-611 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Distribution.fs:706-718 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Distribution.fs:817-829 — 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:474` 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 × 4) src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:502— src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:502-514 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:746-758 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:1486-1498 | src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:475-487 — there are 4 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 4 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (10 lines × 4) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:311— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:311-320 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:63-72 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:174-183 | src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:53-62 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 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 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:311` 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/ChartAPI/Chart2D/Chart2D_Scatter.fs:416— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:416-425 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:268-277 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:396-405 | src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:260-269 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 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 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:416` 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/ChartAPI/Chart2D/Chart2D_Scatter.fs:1496— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1496-1505 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:1093-1102 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:1228-1237 | src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:775-784 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 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 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1496` 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/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:871— 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:850-859 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:936-945 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:871` 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/Layout/ObjectAbstractions/Common/LayoutGrid.fs:31— src/Plotly.NET/Layout/ObjectAbstractions/Common/LayoutGrid.fs:31-39 | src/Plotly.NET/Layout/ObjectAbstractions/Common/LayoutGrid.fs:77-85 | src/Plotly.NET/ChartAPI/Chart.fs:3035-3043 | src/Plotly.NET/ChartAPI/Chart.fs:3353-3361 | src/Plotly.NET/ChartAPI/Chart.fs:3469-3477 — 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.
Duplicated block (9 lines × 5) src/Plotly.NET/Traces/Trace2D.fs:2252— src/Plotly.NET/Traces/Trace2D.fs:2252-2260 | src/Plotly.NET/Traces/TracePolar.fs:259-267 | src/Plotly.NET/Traces/TraceGeo.fs:104-112 | src/Plotly.NET/Traces/TraceMapbox.fs:243-251 | src/Plotly.NET/Traces/TraceMapbox.fs:376-384 — there are 5 copies across 4 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. 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 (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/ChartPolar/ChartPolar_Scatter.fs:479-487 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:721-729 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Pie.fs:726-734 | src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:454-462 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 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 5 times. 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 (9 lines × 5) src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Pie.fs:728— src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Pie.fs:728-736 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Pie.fs:812-820 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Hierarchy.fs:437-445 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Hierarchy.fs:567-575 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Hierarchy.fs:699-707 — 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.
TooManyMethods: Chart src/Plotly.NET/ChartAPI/Chart.fs:14— TooManyMethods — 109 methods. 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.cs:0— TooManyMethods — 4447 significant lines (blank, comment-only and punctuation-only lines excluded), 88 methods, declared across 9 files: ChartAPI/Chart2D.cs (31), ChartAPI/ChartDomain.cs (11), ChartAPI/ChartMap.cs (11), ChartAPI/Chart3D.cs (10), +5 more file(s). 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. 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 (15 lines × 4) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:797— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:797-812 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:913-927 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1138-1153 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1278-1292 — 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:797` 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/ChartTernary/ChartTernary_Scatter.fs:71— src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:71-85 | src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:173-187 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:72-86 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:172-186 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_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 (15 lines × 4) src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:550— src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:550-565 | src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:618-632 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:566-580 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:632-646 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:550` 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 × 3) src/Plotly.NET/Traces/Trace2D.fs:628— src/Plotly.NET/Traces/Trace2D.fs:628-636 | src/Plotly.NET/Traces/Trace2D.fs:1266-1274 | src/Plotly.NET/Traces/Trace2D.fs:1501-1509 — 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 (9 lines × 3) src/Plotly.NET/Traces/Trace2D.fs:694— src/Plotly.NET/Traces/Trace2D.fs:694-702 | src/Plotly.NET/Traces/Trace2D.fs:1353-1361 | src/Plotly.NET/Traces/Trace2D.fs:1563-1571 — 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 (9 lines × 3) src/Plotly.NET/Traces/Trace3D.fs:190— src/Plotly.NET/Traces/Trace3D.fs:190-198 | src/Plotly.NET/Traces/Trace3D.fs:351-359 | src/Plotly.NET/Traces/Trace3D.fs:551-559 — 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.ImageExport/ChartExtensions.fs:33— src/Plotly.NET.ImageExport/ChartExtensions.fs:33-41 | src/Plotly.NET.ImageExport/ChartExtensions.fs:119-127 | src/Plotly.NET.ImageExport/ChartExtensions.fs:205-212 — 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.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 × 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 × 2) src/Plotly.NET/ChartAPI/Chart.fs:1112— src/Plotly.NET/ChartAPI/Chart.fs:1112-1119 | src/Plotly.NET/ChartAPI/Chart.fs:1125-1132 — 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:1125` 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 (8 lines × 2) src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:284— src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:284-291 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_VectorField.fs:593-600 — 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 (8 lines × 2) src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Icicle.fs:65— src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Icicle.fs:65-72 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Icicle.fs:352-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.
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/Templates/ChartTemplates.fs:49— src/Plotly.NET/Templates/ChartTemplates.fs:49-55 | src/Plotly.NET/Templates/ChartTemplates.fs:66-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. 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 (7 lines × 2) src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Pie.fs:671— src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Pie.fs:671-678 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Pie.fs:852-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/ChartDomain/ChartDomain_Pie.fs:671` 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 (19 lines × 4) src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Pie.fs:80— src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Pie.fs:80-98 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Pie.fs:189-207 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Hierarchy.fs:89-107 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Hierarchy.fs:217-235 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Pie.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 (19 lines × 4) src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Hierarchy.fs:464— src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Hierarchy.fs:464-482 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Hierarchy.fs:594-612 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Icicle.fs:96-114 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Icicle.fs:240-258 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Hierarchy.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 (19 lines × 2) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Splom.fs:292— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Splom.fs:292-310 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Splom.fs:399-417 — 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:292` 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/ChartAPI/ChartDomain/ChartDomain_Pie.fs:649— src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Pie.fs:649-668 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Pie.fs:831-849 — 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:649` 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 × 5) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:103— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:103-117 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Splom.fs:58-72 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:200-214 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:309-323 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:514-528 — there are 5 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 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/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 × 5) src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:330— src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:330-344 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:1073-1087 | src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:1153-1167 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:288-302 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:1306-1320 — 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.
Duplicated block (14 lines × 4) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:76— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:76-89 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:186-199 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:406-419 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:520-533 — 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:76` 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/ChartDomain/ChartDomain_Hierarchy.fs:110— src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Hierarchy.fs:110-123 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Hierarchy.fs:238-251 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Hierarchy.fs:485-498 | src/Plotly.NET/ChartAPI/ChartDomain/ChartDomain_Hierarchy.fs:615-628 — 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/ChartDomain/ChartDomain_Hierarchy.fs:110` 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 × 3) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1643— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1643-1656 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:365-378 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:1111-1124 — 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_Scatter.fs:1643` 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/Chart2D/Chart2D_Statistical.fs:350— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Statistical.fs:350-363 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Statistical.fs:466-479 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Statistical.fs:586-599 — 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 (8 lines × 6) src/Plotly.NET/Traces/Trace3D.fs:120— src/Plotly.NET/Traces/Trace3D.fs:120-127 | src/Plotly.NET/Traces/Trace3D.fs:460-467 | src/Plotly.NET/Traces/Trace3D.fs:654-661 | src/Plotly.NET/Traces/Trace3D.fs:831-838 | src/Plotly.NET/Traces/Trace3D.fs:1009-1016 | src/Plotly.NET/Traces/Trace3D.fs:1190-1197 — 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 (8 lines × 6) src/Plotly.NET/Traces/TraceGeo.fs:298— src/Plotly.NET/Traces/TraceGeo.fs:298-305 | src/Plotly.NET/Traces/TraceMapbox.fs:163-170 | src/Plotly.NET/Traces/TraceTernary.fs:141-148 | src/Plotly.NET/Traces/TraceCarpet.fs:265-272 | src/Plotly.NET/Traces/TraceDomain.fs:1075-1082 | src/Plotly.NET/Traces/TraceSmith.fs:134-141 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. 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 (7 lines × 3) src/Plotly.NET.ImageExport/ChartExtensions.fs:54— src/Plotly.NET.ImageExport/ChartExtensions.fs:54-60 | src/Plotly.NET.ImageExport/ChartExtensions.fs:140-146 | src/Plotly.NET.ImageExport/ChartExtensions.fs:225-231 — 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 × 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 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 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 3 times.
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 10, match/switch 6 (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 10, if/else 6 (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.
Duplicated block (21 lines × 3) src/Plotly.NET/ChartAPI/Chart.fs:452— src/Plotly.NET/ChartAPI/Chart.fs:452-472 | src/Plotly.NET/ChartAPI/Chart.fs:527-547 | src/Plotly.NET/ChartAPI/Chart.fs:602-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:452` 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:1967— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:1967-1986 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:2158-2177 — 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:1967` 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/Chart.fs:2288— src/Plotly.NET/ChartAPI/Chart.fs:2288-2305 | src/Plotly.NET/ChartAPI/Chart.fs:2345-2362 | src/Plotly.NET/ChartAPI/Chart.fs:2402-2419 — 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:2288` 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:322— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Splom.fs:322-339 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Splom.fs:429-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_Splom.fs:322` 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 × 4) src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Density.fs:58— src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Density.fs:58-74 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Density.fs:133-149 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Density.fs:206-222 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Density.fs:344-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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Density.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 (17 lines × 3) src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:234— src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:234-250 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:343-359 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:547-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:234` 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/ChartMap/ChartMap_Geo.fs:214— src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:214-229 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:323-338 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:528-543 — 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:214` 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 × 8) src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:491— src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:491-504 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:297-310 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:1260-1273 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:427-440 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:1410-1423 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:494-507 | src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:290-303 | src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:971-984 — there are 8 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 8 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (12 lines × 12) src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:297— src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:297-308 | src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:582-593 | src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:649-660 | src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:731-742 | src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:1009-1020 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:300-311 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:596-607 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:662-673 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:749-760 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:1045-1056 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:1318-1329 | src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:982-993 — 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.
Duplicated block (12 lines × 9) src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:370— src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:370-381 | src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:420-431 | src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:484-495 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:377-388 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:430-441 | src/Plotly.NET/ChartAPI/ChartCarpet/ChartCarpet_Scatter.fs:500-511 | src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:371-382 | src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:417-428 | src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:480-491 — there are 9 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 9 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (12 lines × 6) src/Plotly.NET/Traces/Trace3D.fs:305— src/Plotly.NET/Traces/Trace3D.fs:305-316 | src/Plotly.NET/Traces/Trace3D.fs:495-506 | src/Plotly.NET/Traces/Trace3D.fs:686-697 | src/Plotly.NET/Traces/Trace3D.fs:863-874 | src/Plotly.NET/Traces/Trace3D.fs:1035-1046 | src/Plotly.NET/Traces/Trace3D.fs:1216-1227 — 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. 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/ChartAPI/ChartMap/ChartMap_Geo.fs:438— src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:438-449 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:924-935 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:994-1005 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:1085-1096 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:1183-1194 — 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 × 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/TracePolar.fs:232-242 | src/Plotly.NET/Traces/TraceMapbox.fs:358-368 | src/Plotly.NET/Traces/TraceCarpet.fs:76-86 | src/Plotly.NET/Traces/TraceCarpet.fs:337-347 — 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 (11 lines × 9) src/Plotly.NET/Templates/ChartTemplates.fs:202— src/Plotly.NET/Templates/ChartTemplates.fs:202-212 | src/Plotly.NET/Templates/ChartTemplates.fs:216-226 | src/Plotly.NET/Templates/ChartTemplates.fs:424-434 | src/Plotly.NET/Templates/ChartTemplates.fs:443-453 | src/Plotly.NET/Templates/ChartTemplates.fs:469-479 | src/Plotly.NET/Templates/ChartTemplates.fs:489-499 | src/Plotly.NET/Templates/ChartTemplates.fs:523-533 | src/Plotly.NET/Templates/ChartTemplates.fs:543-553 | src/Plotly.NET/Templates/ChartTemplates.fs:666-676 — 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.
Duplicated block (11 lines × 7) src/Plotly.NET/Traces/Trace2D.fs:186— src/Plotly.NET/Traces/Trace2D.fs:186-196 | src/Plotly.NET/Traces/TracePolar.fs:88-98 | src/Plotly.NET/Traces/TraceGeo.fs:225-235 | src/Plotly.NET/Traces/TraceMapbox.fs:95-105 | src/Plotly.NET/Traces/TraceTernary.fs:68-78 | src/Plotly.NET/Traces/TraceCarpet.fs:196-206 | src/Plotly.NET/Traces/TraceSmith.fs:67-77 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. 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 lines × 6) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:886— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Scatter.fs:886-896 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:162-172 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Area.fs:814-824 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Scatter.fs:638-648 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Geo.fs:944-954 | src/Plotly.NET/ChartAPI/ChartSmith/ChartSmith_Scatter.fs:594-604 — there are 6 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 6 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_Scatter.fs:886` 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 × 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 — there are 17 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 17 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: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 (10 lines × 5) src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:204— src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:204-213 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:418-427 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:659-668 | src/Plotly.NET/ChartAPI/Chart2D/Chart2D_Bar.fs:873-882 | src/Plotly.NET/ChartAPI/ChartPolar/ChartPolar_Bar.fs:128-137 — 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/Chart2D/Chart2D_Bar.fs:204` 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 × 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/TracePolar.fs:112-120 | src/Plotly.NET/Traces/TraceGeo.fs:247-255 | src/Plotly.NET/Traces/TraceMapbox.fs:115-123 | src/Plotly.NET/Traces/TraceTernary.fs:89-97 | 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/TraceSmith.fs:86-94 — 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 × 10) src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:305— src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:305-313 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:396-404 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:477-485 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:530-538 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:616-624 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:684-692 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:781-789 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:869-877 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:940-948 | src/Plotly.NET/ChartAPI/ChartMap/ChartMap_Mapbox.fs:1033-1041 — 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.
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 — there are 4 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 4 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (5 lines × 2) src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:1148— src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:1148-1152 | src/Plotly.NET/ChartAPI/ChartTernary/ChartTernary_Scatter.fs:992-996 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Plotly.NET/ChartAPI/Chart3D/Chart3D_Scatter.fs:1148` 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.
Coverage not measured — test suite did not build — Coverage NOT MEASURED: this repository did not build in our analyzer environment (a C#/MSBuild compiler error), so no coverage could be collected. It is excluded from the score rather than counted as a near-zero defect. We did not read WHERE the failing diagnostic is, so this does not claim the fault is in your test code — a repository written for an older SDK band can compile for you and not for us. Run `dotnet build` on this commit; if it succeeds, the gap is ours. Committing the Cobertura/OpenCover/lcov report your CI already produces also lets us measure real coverage without building anything.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 16 significant file(s) lose their only recent owner: src/Plotly.NET/Traces/Trace2D.fs, src/Plotly.NET/ChartAPI/Chart.fs, src/Plotly.NET.CSharp/ChartAPI/Chart2D.cs, src/Plotly.NET/Traces/Trace3D.fs, src/Plotly.NET/Traces/TraceDomain.fs, src/Plotly.NET/Traces/TraceMapbox.fs, src/Plotly.NET/Traces/TraceCarpet.fs, src/Plotly.NET/Traces/TraceGeo.fs (+8 more). Pair on, review, or document these before any departure.
D19 · Documentation Quality· The What is Plotly.NET? section mentions a DOI paper but the link points to https · ×1
The What is Plotly.NET? section mentions a DOI paper but the link points to https://doi.org/10.12688/f1000research.123971.1, which does not exist. README.md— Verify that the linked DOI (https://doi.org/10.12688/f1000research.123971.1) is correct and update the link if it has moved or been replaced.
D34 · Knowledge Freshness· Further orphaned files (smaller) · ×1
Further orphaned files (smaller) — 1 of 115 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 100 lines or more, excluding tests, vendored, generated and example/demo trees, largest first). 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 — largest 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.
Info — 3 finding(s)
D12 · Dependency Hygiene· Dependency hygiene not measured · ×1
Dependency hygiene not measured — no packages were read — This repository's projects (.fs) are MSBuild/NuGet projects and their `<PackageReference>` dependencies are exactly what this dimension assesses — but `dotnet list package` returned no packages for them, so there was nothing to assess. Zero packages read is NOT a clean dependency tree, so this is NOT SCORED. This is a gap in the analysis run (restore or project-load failed for these projects), not a verdict about this repository.
D22 · Internal API Consistency· No exposed public API · ×1
No exposed public API — No intentionally-exposed types (IsPackable or .Contracts) to evaluate.
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.
dotnet: not applicable — the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan for NuGet CVEs — excluded rather than scored; re-run on an SDK that can restore this solution
trivy: not applicable — No JS/npm manifest or lockfile found outside build output (package.json, package-lock.json, yarn.lock, pnpm-lock.yaml, bun.lockb); no JS dependencies to scan.
provenance: not applicable — The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release).
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.
0
—
Run 019fd517-6afb-7ca1-8632-7b18c67b5762 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Warnings: 402 · Recommendations: 5 · Info: 3 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 06-08-2026 @ 03:21 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.