Public report of esentio/Yamo, published 15 November 2026. It has the same score, grades and number of findings as the full report. The details of security findings (where they are in the code, which known vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive report Measured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey → Signed and filed in the standard's public register, 15 November 2026, 03:25 UTC · Survey ID cd_12af87f8d2fc4c6889bd497afdc43c2e

esentio/Yamo

Measured 15 November 2026, 03:24 UTC, at code version 0eba35c

Boundary Type-Coupling is not measured: Bounded contexts not declared.

CAI score 41out of 100 Weak
CriticalWeakAdequateStrongExemplary
Down 1 since the last survey

The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.

A large codebase: 264,009 lines of product code in 21 projects, tests not counted · Estimated rebuild effort: about 1.5 person-years · Weakest lens: Production Readiness, 30

Findings by how serious they are

3 critical 944 serious 391 minor

10 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.

This survey was produced by

Assert small markCanine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
15 November 2026, 03:24 UTC

A measurement, not a certificate. The Code Assurance Index records a number together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that implements it, and today the Canine Code Analyzer is the only one that does.

The score is deterministic, which means the same code always gets the same score. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸

44of 44 dimensions measured by tools.
1327of 1338 findings point to an exact file and line, so you can open each one in the code. The other 11 concern the repository as a whole, such as missing documentation.
44dimensions across 6 lenses, read from 264,009 lines of product code in 21 projects.
Chapters

Executive summary

esentio/Yamo falls short of our standard for a preview release, in part because we found no working pipeline that builds or tests changes to the code. It scores 41 out of 100 and is rated Weak, and all three of its critical findings are security problems in the packages it uses.

Production Readiness, at 30, is the weakest lens and counts most in the score. The best first step for the work it takes is recording design decisions, worth about 3 points. Adding an automated build and test pipeline would lift Production Readiness itself, worth about 7 points. Raising Production Readiness to 62 would lift the score to about 49.

Three known security holes in the packages the code depends on can be used by attackers. Updating the vulnerable packages would close this risk.

The product code is 264,009 lines, about €210,000 to rebuild.

A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.

How the score is built: what each lens counts for The lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
Production Readiness 30 · counts for 46%Security and Compliance 43 · counts for 25%Maturity 43 · counts for 14%Code Health 57 · counts for 8%Performance 86 · counts for 4%Architecture 96 · counts for 2%

If Production Readiness rose from 30 to 62, the lowest score rated Strong, the score would rise from 41 to about 49.

Code composition: what the lines of code are
Business logic 1%Supporting code 4%Tests 95%Generated by tools 0%
New since the last survey: 495 findings

These 495 critical or serious findings weren't in the previous survey, on 29 October 2026. The first 100 are listed here, and the findings file in the download package lists them all.

  • Code Duplication · Edited copy of a member (51 corresponding lines) Source/Source/Yamo/Internal/Query/QueryExecutor.vb
  • Code Duplication · Edited copy of a member (35 corresponding lines) Source/Source/Yamo/Infrastructure/ValueTypeReaderFactory.vb
  • Code Duplication · Edited copy of a member (65 corresponding lines) Source/Source/Yamo/Infrastructure/EntityReaderFactory.vb
  • Code Duplication · Edited copy of a member (20 corresponding lines) Source/Source/Yamo/PredicateBuilder.vb
  • Code Duplication · Edited copy of a member (12 corresponding lines) Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.If.vb
  • Code Duplication · Edited copy of a member (24 corresponding lines) Source/Source/Yamo/PredicateBuilder.vb
  • Code Duplication · Edited copy of a member (28 corresponding lines) Source/Source/Yamo/Internal/SqlExpressionVisitor.vb
  • Code Duplication · Edited copies of one member (3 members, 31+ corresponding lines) Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Having.vb
  • Code Duplication · Edited copy of a member (13 corresponding lines) Source/Source/Yamo/Infrastructure/MemberSetterFactory.vb
  • Code Duplication · Edited copy of a member (24 corresponding lines) Source/Source/Yamo/Expressions/Builders/DeleteSqlExpressionBuilder.vb
  • Code Duplication · Edited copy of a member (15 corresponding lines) Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11.vb
  • Code Duplication · Edited copy of a member (15 corresponding lines) Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10.vb
  • Code Duplication · Edited copies of one member (8 members, 10+ corresponding lines) Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.OrderBy.vb
  • Code Duplication · Edited copy of a member (15 corresponding lines) Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9.vb
  • Code Duplication · Edited copies of one member (8 members, 11+ corresponding lines) Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Join.vb
  • Code Duplication · Edited copies of one member (8 members, 10+ corresponding lines) Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Join.vb
  • Code Duplication · Edited copy of a member (15 corresponding lines) Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8.vb
  • Code Duplication · Edited copy of a member (11 corresponding lines) Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.As.vb
  • Code Duplication · Edited copies of one member (6 members, 10+ corresponding lines) Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Set.vb
  • Code Duplication · Edited copies of one member (4 members, 10+ corresponding lines) Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.ThenBy.vb
  • Code Duplication · Edited copy of a member (10 corresponding lines) Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Exclude.vb
  • Code Duplication · Edited copies of one member (8 members, 9+ corresponding lines) Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Having.And.vb
  • Code Duplication · Edited copies of one member (8 members, 9+ corresponding lines) Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Where.And.vb
  • Code Duplication · Edited copies of one member (4 members, 10+ corresponding lines) Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Join.vb
  • Code Duplication · Edited copies of one member (4 members, 10+ corresponding lines) Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.OrderBy.vb
  • Code Duplication · Edited copy of a member (10 corresponding lines) Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.OrderBy.vb
  • Code Duplication · Edited copies of one member (4 members, 10+ corresponding lines) Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.GroupBy.vb
  • Code Duplication · Edited copies of one member (3 members, 10+ corresponding lines) Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Join.vb
  • Code Duplication · Edited copies of one member (3 members, 10+ corresponding lines) Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Join.vb
  • Code Duplication · Edited copies of one member (3 members, 10+ corresponding lines) Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Join.vb
  • Code Duplication · Edited copies of one member (3 members, 10+ corresponding lines) Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Join.vb
  • Code Duplication · Edited copy of a member (17 corresponding lines) Source/Source/Yamo/Expressions/Builders/DeleteSqlExpressionBuilder.vb
  • Code Duplication · Edited copies of one member (3 members, 9+ corresponding lines) Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.On.vb
  • Code Duplication · Edited copy of a member (12 corresponding lines) Source/Source/Yamo/Internal/Query/QueryExecutor.vb
  • Code Duplication · Edited copies of one member (4 members, 9+ corresponding lines) Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Having.And.vb
  • Code Duplication · Edited copies of one member (3 members, 9+ corresponding lines) Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.OrderBy.vb
  • Code Duplication · Edited copies of one member (4 members, 9+ corresponding lines) Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Where.And.vb
  • Code Duplication · Edited copy of a member (2 corresponding lines) Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24T25.vb
  • Code Duplication · Edited copies of one member (3 members, 8+ corresponding lines) Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Having.vb
  • Code Duplication · Edited copies of one member (4 members, 9+ corresponding lines) Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Include.vb
  • Code Duplication · Edited copies of one member (3 members, 9+ corresponding lines) Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Limit.vb
  • Code Duplication · Edited copies of one member (6 members, 9+ corresponding lines) Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.OrderBy.vb
  • Code Duplication · Edited copies of one member (5 members, 8+ corresponding lines) Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Where.vb
  • Code Duplication · Edited copies of one member (3 members, 10+ corresponding lines) Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Select.vb
  • Code Duplication · Edited copy of a member (2 corresponding lines) Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24.vb
  • Code Duplication · Edited copies of one member (6 members, 9+ corresponding lines) Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Set.vb
  • Code Duplication · Edited copies of one member (6 members, 9+ corresponding lines) Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Set.vb
  • Code Duplication · Edited copies of one member (6 members, 9+ corresponding lines) Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Set.vb
  • Code Duplication · Edited copies of one member (6 members, 9+ corresponding lines) Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Set.vb
  • Code Duplication · Edited copy of a member (2 corresponding lines) Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb
  • Code Duplication · Edited copy of a member (2 corresponding lines) Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb
  • Code Duplication · Edited copies of one member (6 members, 8+ corresponding lines) Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Distinct.vb
  • Code Duplication · Edited copy of a member (2 corresponding lines) Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb
  • Code Duplication · Edited copy of a member (7 corresponding lines) Source/Source/Yamo/PredicateBuilder.vb
  • Code Duplication · Edited copy of a member (2 corresponding lines) Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb
  • Code Duplication · Edited copy of a member (10 corresponding lines) Source/Source/Yamo/Expressions/Builders/SelectSqlExpressionBuilder.vb
  • Code Duplication · Edited copy of a member (2 corresponding lines) Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb
  • Code Duplication · Edited copy of a member (2 corresponding lines) Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24T25.vb
  • Code Duplication · Edited copy of a member (2 corresponding lines) Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18.vb
  • Code Duplication · Edited copy of a member (2 corresponding lines) Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24.vb
  • Code Duplication · Edited copy of a member (2 corresponding lines) Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17.vb
  • Code Duplication · Edited copy of a member (21 corresponding lines) Source/Source/Yamo/Internal/PostProcessorCache.vb
  • Code Duplication · Edited copy of a member (22 corresponding lines) Source/Source/Yamo/Internal/SqlResultReaderCache.vb
  • Code Duplication · Edited copy of a member (2 corresponding lines) Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb
  • Code Duplication · Edited copy of a member (19 corresponding lines) Source/Source/Yamo/Internal/MemberSetterCache.vb
  • Code Duplication · Edited copy of a member (2 corresponding lines) Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16.vb
  • Code Duplication · Edited copy of a member (2 corresponding lines) Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb
  • Code Duplication · Edited copy of a member (3 corresponding lines) Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7.vb
  • Code Duplication · Edited copy of a member (2 corresponding lines) Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15.vb
  • Code Duplication · Edited copy of a member (2 corresponding lines) Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb
  • Code Duplication · Edited copy of a member (2 corresponding lines) Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14.vb
  • Code Duplication · Edited copy of a member (2 corresponding lines) Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb
  • Code Duplication · Edited copy of a member (2 corresponding lines) Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13.vb
  • Code Duplication · Edited copy of a member (2 corresponding lines) Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb
  • Code Duplication · Edited copy of a member (2 corresponding lines) Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12.vb
  • Code Duplication · Edited copy of a member (2 corresponding lines) Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18.vb
  • Code Duplication · Edited copy of a member (17 corresponding lines) Source/Source/Yamo/Internal/EntityReaderCache.vb
  • Code Duplication · Edited copy of a member (2 corresponding lines) Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11.vb
  • Code Duplication · Edited copy of a member (2 corresponding lines) Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17.vb
  • Code Duplication · Edited copy of a member (2 corresponding lines) Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10.vb
  • Code Duplication · Edited copy of a member (6 corresponding lines) Source/Source/Yamo.SqlServer/Sql/Exp.vb
  • Code Duplication · Edited copy of a member (2 corresponding lines) Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16.vb
  • Code Duplication · Edited copy of a member (2 corresponding lines) Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9.vb
  • Code Duplication · Edited copy of a member (2 corresponding lines) Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15.vb
  • Code Duplication · Edited copy of a member (12 corresponding lines) Source/Source/Yamo/Internal/EntityReaderCache.vb
  • Code Duplication · Edited copy of a member (2 corresponding lines) Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8.vb
  • Code Duplication · Edited copy of a member (2 corresponding lines) Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14.vb
  • Code Duplication · Edited copy of a member (12 corresponding lines) Source/Source/Yamo/Internal/EntitySqlStringProviderCache.vb
  • Code Duplication · Edited copy of a member (2 corresponding lines) Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7.vb
  • Code Duplication · Edited copy of a member (2 corresponding lines) Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13.vb
  • Code Duplication · Edited copy of a member (2 corresponding lines) Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8.vb
  • Code Duplication · Edited copy of a member (2 corresponding lines) Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6.vb
  • Code Duplication · Edited copy of a member (2 corresponding lines) Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12.vb
  • Code Duplication · Edited copy of a member (2 corresponding lines) Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7.vb
  • Code Duplication · Edited copy of a member (2 corresponding lines) Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5.vb
  • Code Duplication · Edited copy of a member (2 corresponding lines) Source/Source/Yamo/Infrastructure/EntityAutoFieldsGetterFactory.vb
  • Code Duplication · Edited copy of a member (7 corresponding lines) Source/Source/Yamo/Infrastructure/EntityAutoFieldsGetterFactory.vb
  • Code Duplication · Edited copy of a member (2 corresponding lines) Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11.vb
  • Code Duplication · Edited copy of a member (2 corresponding lines) Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6.vb
  • Code Duplication · Edited copy of a member (2 corresponding lines) Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4.vb

We compare every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.

Rebuild cost: about €210,000 · Estimate
Cost to rebuild€70,000 to €350,000, for 1,169 to 3,708 hours of work, about 1.5 person-years for 1 to 3 engineers
Difficulty of the problemLow, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor×0.7 at a score of 41. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
SizeLarge: 264,009 lines of product code
Comment linesThe estimate prices 263,145 lines. Comment lines count towards the size of 264,009 lines but aren't priced as work.
What it is notNot a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.

How the estimate is made: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty.

Top priorities

The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.

1
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Yamo.CodeGenerator.vbproj.
Raises the score by about 3 points · Low effort · ADR Quality
2
Add a CI workflow that builds and runs the test suite on every push/PR.
Raises the score by about 7 points · Medium effort · CI/CD gates
3
Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault.
Skip if delegated to infra (Postgres TDE, KMS, etc.).
Raises the score by about 5 points · Medium effort · Data Protection

Diagnosis: what the measurements show together

Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.

Where the investment is most exposed · Value at risk
This code would cost about €210,000 to build again, about 1.5 person-years of work. Its weakest lens is Production Readiness, at 30 (Weak). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
If you do one thing first · First action
Resolve the 1 No ADRs found finding(s) in ADR Quality. Of all the actions in this report, it raises the score most for the work it takes: about 3 points for low effort, because it clears the 1 ADR Quality findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 6.9 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 3% to 6% on every change. The history of the code shows how much it changes: about 759 lines over the last 90 days, which is about 3,078 lines a year. At that pace, the extra work comes to an estimated 0.2 to 1.3 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of our own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.

Architecture — module dependency graph

Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.

arch Yamo Yamo Yamo.CodeGenerator CodeGenerator Yamo.Playground.CS CS Yamo.Playground.CS->Yamo Yamo.SqlServer SqlServer Yamo.Playground.CS->Yamo.SqlServer Yamo.Playground.VB VB Yamo.Playground.VB->Yamo Yamo.Playground.VB->Yamo.SqlServer Yamo.SQLite SQLite Yamo.SQLite->Yamo Yamo.SqlServer->Yamo

Architecture: which parts of the code depend on which

The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.

26 modules, with 46 dependencies between them. One loop runs through 7 of the modules, marked above the diagonal.

Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
uses →1 Microsoft.VisualBasic2 Microsoft.VisualBasic.CompilerServices3 Yamo.Benchmarks.My4 Yamo.CodeGenerator5 Yamo.CodeGenerator.Extensions6 Yamo.CodeGenerator.Generator7 Yamo.CodeGenerator.My8 Yamo.Internal.Extensions9 Yamo.Internal.Helpers10 Yamo.Metadata11 Yamo.My12 Yamo.SQLite.My13 Yamo.SqlServer.My14 Yamo.Internal.Query.Metadata15 Yamo.Metadata.Builders16 Yamo.Internal17 Yamo.Internal.Query18 Yamo.Infrastructure19 Yamo.Expressions.Builders20 Yamo.SQLite.Infrastructure21 Yamo.SqlServer.Infrastructure22 Yamo.Expressions23 Yamo24 Yamo.Sql25 Yamo.SQLite.Sql26 Yamo.SqlServer.Sql
1 Microsoft.VisualBasic
2 Microsoft.VisualBasic.CompilerServices
3 Yamo.Benchmarks.My
4 Yamo.CodeGenerator
5 Yamo.CodeGenerator.Extensions
6 Yamo.CodeGenerator.Generator
7 Yamo.CodeGenerator.My
8 Yamo.Internal.Extensions
9 Yamo.Internal.Helpers
10 Yamo.Metadata
11 Yamo.My
12 Yamo.SQLite.My
13 Yamo.SqlServer.My
14 Yamo.Internal.Query.Metadata611
15 Yamo.Metadata.Builders8
16 Yamo.Internal1196443
17 Yamo.Internal.Query220122
18 Yamo.Infrastructure157343
19 Yamo.Expressions.Builders173101112
20 Yamo.SQLite.Infrastructure3
21 Yamo.SqlServer.Infrastructure1
22 Yamo.Expressions8262662
23 Yamo212327
24 Yamo.Sql41
25 Yamo.SQLite.Sql24
26 Yamo.SqlServer.Sql24
Uses a module listed above itPart of a loopThe module itself
1 Microsoft.VisualBasic2 Microsoft.VisualBasic.CompilerServices3 Yamo.Benchmarks.My4 Yamo.CodeGenerator5 Yamo.CodeGenerator.Extensions6 Yamo.CodeGenerator.Generator7 Yamo.CodeGenerator.My8 Yamo.Internal.Extensions9 Yamo.Internal.Helpers10 Yamo.Metadata11 Yamo.My12 Yamo.SQLite.My13 Yamo.SqlServer.My14 Yamo.Internal.Query.Metadata15 Yamo.Metadata.Builders16 Yamo.Internal17 Yamo.Internal.Query18 Yamo.Infrastructure19 Yamo.Expressions.Builders20 Yamo.SQLite.Infrastructure21 Yamo.SqlServer.Infrastructure22 Yamo.Expressions23 Yamo24 Yamo.Sql25 Yamo.SQLite.Sql26 Yamo.SqlServer.SqlMicrosoft.VisualBasic1Microsoft.VisualBasic.CompilerServices2Yamo.Benchmarks.My3Yamo.CodeGenerator4Yamo.CodeGenerator.Extensions5Yamo.CodeGenerator.Generator6Yamo.CodeGenerator.My7Yamo.Internal.Extensions8Yamo.Internal.Helpers9Yamo.Metadata10Yamo.My11Yamo.SQLite.My12Yamo.SqlServer.My13Yamo.Internal.Query.Metadata14Yamo.Metadata.Builders15Yamo.Internal16Yamo.Internal.Query17Yamo.Infrastructure18Yamo.Expressions.Builders19Yamo.SQLite.Infrastructure20Yamo.SqlServer.Infrastructure21Yamo.Expressions22Yamo23Yamo.Sql24Yamo.SQLite.Sql25Yamo.SqlServer.Sql2661181196443220122157343173101112318262662212327412424

At a glance — Code Health · 57% · Adequate · gated by X5 ·

At a glance — Architecture · 96% · Exemplary ·

At a glance — Maturity · 43% · Adequate · gated by D34, M2 ·

At a glance — Readiness · 30% · Weak · gated by D8, P1, P3 ·

At a glance — Security · 43% · Weak · gated by C1 ·

At a glance — Performance · 86% · Exemplary ·

Security & Compliance — OWASP Top-10 mapping

Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).

OWASP categoryFindingsSeverity
A03:2025 — Software Supply Chain Failures4High / Critical

Roadmap

Top priorities: Resolve the 363 Low coverage finding(s) in Code Coverage — start with DbContext.vb, DbContextOptionsBuilder.vb, DeleteSqlExpressionBuilder.vb; Add a CI workflow that builds and runs the test suite on every push/PR; Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault. Skip if delegated to infra (Postgres TDE, KMS, etc.).

Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.

Do thisHelpsEffortDimension
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Yamo.CodeGenerator.vbproj.+3.5 ptsLowADR Quality
Add a CI workflow that builds and runs the test suite on every push/PR.+6.5 ptsMediumCI/CD gates
Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault. Skip if delegated to infra (Postgres TDE, KMS, etc.).+4.7 ptsMediumData Protection
Resolve the 363 Low coverage finding(s) in Code Coverage — start with DbContext.vb, DbContextOptionsBuilder.vb, DeleteSqlExpressionBuilder.vb.+8.1 ptsHighCode Coverage
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.+3.2 ptsMediumArchitecture documentation
Extend structured logging across the projects you operate, and give the library ones a diagnostics seam instead — an `EventSource`/`ActivitySource` the host can subscribe to, or an optional logger on your options object — rather than taking a logging dependency on your consumers' behalf.+3.0 ptsMediumObservability
Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.+2.5 ptsMediumRelease Hygiene
Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.+2.3 ptsMediumNullable reference types

File quality

Per-file score 0–10 — a quality signature. Of 409 files carrying findings, judged against the Preview bar: 0% slop · 24% mixed · 76% near-clean.

FileScoreBandWorst signal
Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb4.8MixedCyclomatic Complexity: JoinedSelectSqlExpression.CanCreateResultForCondition (cyclomatic 216)
Source/Source/Yamo/Internal/EntityReaderCache.vb4.8MixedCode Duplication: Edited copy of a member (17 corresponding lines)
Source/Source/Yamo/Expressions/DeleteSqlExpression.vb4.8MixedCode Duplication: Edited copy of a member (2 corresponding lines)
Source/Source/Yamo/Expressions/SelectSqlExpression.vb4.8MixedCyclomatic Complexity: SelectSqlExpression.CanCreateResultForCondition (cyclomatic 225)
Source/Source/Yamo/Expressions/WithHintsSelectSqlExpression.vb4.9MixedCyclomatic Complexity: WithHintsSelectSqlExpression.CanCreateResultForCondition (cyclomatic 224)
Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2.vb4.9MixedCyclomatic Complexity: SelectSqlExpression.CanCreateResultForCondition (cyclomatic 215)
Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3.vb4.9MixedCyclomatic Complexity: JoinedSelectSqlExpression.CanCreateResultForCondition (cyclomatic 207)
Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3.vb4.9MixedCyclomatic Complexity: SelectSqlExpression.CanCreateResultForCondition (cyclomatic 206)
Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4.vb4.9MixedCyclomatic Complexity: JoinedSelectSqlExpression.CanCreateResultForCondition (cyclomatic 198)
Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4.vb4.9MixedCyclomatic Complexity: SelectSqlExpression.CanCreateResultForCondition (cyclomatic 197)
Source/Source/Yamo/Infrastructure/EntitySqlStringProviderFactory.vb5.5MixedCode Duplication: Near-duplicate member family (4 members, 27 shared lines)
Source/Source/Yamo/Internal/EntitySqlStringProviderCache.vb5.5MixedCode Duplication: Edited copy of a member (12 corresponding lines)
Source/Source/Yamo/Expressions/Builders/SelectSqlExpressionBuilder.vb5.5MixedCyclomatic Complexity: SelectSqlExpressionBuilder.AddJoin (cyclomatic 17)
Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15.vb5.6MixedCyclomatic Complexity: JoinedSelectSqlExpression.CanCreateResultForCondition (cyclomatic 99)
Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7.vb5.6MixedCyclomatic Complexity: JoinedSelectSqlExpression.CanCreateResultForCondition (cyclomatic 171)
Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7.vb5.6MixedCyclomatic Complexity: SelectSqlExpression.CanCreateResultForCondition (cyclomatic 170)
Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12.vb5.6MixedCyclomatic Complexity: JoinedSelectSqlExpression.CanCreateResultForCondition (cyclomatic 126)
Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13.vb5.6MixedCyclomatic Complexity: JoinedSelectSqlExpression.CanCreateResultForCondition (cyclomatic 117)
Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14.vb5.6MixedCyclomatic Complexity: JoinedSelectSqlExpression.CanCreateResultForCondition (cyclomatic 108)
Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb5.6MixedCyclomatic Complexity: JoinedSelectSqlExpression.CanCreateResultForCondition (cyclomatic 63)

How the grades work

Every finding carries one of four grades. Three say how serious it is. The fourth says this survey could not settle it — and it is a grade, not a gap.

Critical — 3

A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.

Serious — 944

Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.

Minor — 391

Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.

Could not be resolved — 10

Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.

Methodology & how to trust this report

This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 44 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 1.0, the weighted average across measured dimensions.

Every figure here is one of two kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10.

What we checked — 44 dimensions across the health lenses
D1D2D3D4D5D6D8D10D11D13D14D15D17D18D19D20D24D26D27D28D29D30D34D35D43D44AX10AX3AX4AX5AX8C1GD1M1M2M3P1P2P3P6PF1PF3X28X5

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
  1. 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, 1327 of 1338 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.)
  2. Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
  3. 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.

MethodBacksVersionEvaluator
Roslyn static analysisComplexity, cohesion, coupling, dead code, API surface, layering5.3.0✓ deterministic
Native secret scannerHardcoded secrets / credentials1.0.0✓ deterministic
Canine Code Analyzer duplication detector (in-process)Code duplication1.0.0✓ deterministic
Coverage (coverlet / dotnet-coverage)Line & branch coverage10.0.400✓ deterministic
NuGet / dotnetOutdated, vulnerable & deprecated dependencies10.0.400✓ deterministic
git / LibGit2SharpChurn hotspots, knowledge concentration, history2.43.0 · 0.31.0✓ deterministic
gitleaks · semgrep · trivySecrets in history, SAST, CVEs, IaC & container, PII / GDPR1.86.0 · 0.69.3✓ deterministic

Every finding is locatable in findings.md. Run 01a1dd3c-64e1-7b99-89a0-cf8d7413444e.

The exact command behind every deep-scan dimension — tool, version, invocation and retained raw output — is in Appendix B — Reproduction & audit trail.

Run transparency — what happened this run

What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.

  • D10 Test Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 5 test(s) behind this row are the ones the C# collector could read, and this repository also carries at least 211 test source file(s) (.vb) that it cannot: it parses C# syntax and matches C# test attributes, so a vitest/jest/JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
  • D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `dotnet list package` did not return usable output (restore or query failed); no outdated/vulnerable/deprecated data to assess. The tool said: `dotnet list package` exited 1 with no output.
  • D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-contributor repository — bus factor is not applicable (1 contributor(s) across 268 commit(s) sampled, automation and bot accounts excluded). Concentration needs a team to concentrate: with one contributor there is nobody to spread the knowledge to, so there is nothing here for the owner to act on.
  • D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
  • D22 Internal API Consistency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. The loaded project set declares no packable project and no `.Contracts` project, so there is no intentionally-exposed surface for API consistency to be judged over.
  • D23 Boundary Type-Coupling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Large codebase (264,009 production LoC in the .NET projects) with no declared bounded contexts — cross-boundary type coupling is unassessed Bounded contexts cannot be inferred from a codebase that is not physically organised by them (D-321), so with none declared there are no boundaries for the coupling pass to measure across. You can widen what we reach: name this codebase's bounded contexts (≥2 module groups, e.g. per subsystem) so cross-boundary type coupling can be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
  • D28 Secrets (history) — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. D28's config-credential rule (WD-SECRET-0002) parses each committed `.json` config as a document and reads credential-named values; `Source/Source/Yamo.CodeGenerator/appsettings.json` did not parse (JSON5, a template, several concatenated documents), so a credential bound there is UNMEASURED by that rule. gitleaks still scanned the same files as text.
  • AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • X27 Collection changed while being enumerated — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • X3 Exception handling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.

Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.

Limitations & what we did not check

We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.

Per-dimension blind spots

For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.

  • D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
  • D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
  • D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
  • D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
  • D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
  • D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
  • D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
  • D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
  • D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
  • D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
  • D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
  • D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
  • 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.
  • D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
  • D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
  • D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
  • D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
  • D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
  • D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
  • D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
  • D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
  • D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
  • D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
  • D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
  • D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
  • D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
  • AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
  • 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.

Dimensions

D1 · Cyclomatic Complexity5.2 / 10Adequate✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 5.2 / 10 · rule-coverage 100% · ceiling Prevented

53 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was SelectSqlExpression.CanCreateResultForCondition at 225. A further 6 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 Types.GetDbTypeForClrType at 40 — they are counted neither in the figure above nor in this dimension's score. 6 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: Source/Source/Yamo/Internal/Helpers/Types.vb (Types.GetDbTypeForClrType at 40), Source/Source/Yamo/Infrastructure/EntityReaderFactory.vb (EntityReaderFactory.GetDbDataReaderGetMethodForType at 29), Source/Source/Yamo/Infrastructure/ValueTypeReaderFactory.vb (ValueTypeReaderFactory.CreateReader at 29), Source/Source/Yamo/Internal/Helpers/Common.vb (Common.GetEntityIndexFromJoinMemberName at 26), Source/Source/Yamo/Internal/Query/AutoModeSqlResultReaderDataCollection.vb (AutoModeSqlResultReaderDataCollection.GetChainKey at 26), and 1 more not listed here. They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.

SelectSqlExpression.CanCreateResultForCondition (cyclomatic 225)Source/Source/Yamo/Expressions/SelectSqlExpression.vb:739
WithHintsSelectSqlExpression.CanCreateResultForCondition (cyclomatic 224)Source/Source/Yamo/Expressions/WithHintsSelectSqlExpression.vb:660
JoinedSelectSqlExpression.CanCreateResultForCondition (cyclomatic 216)Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb:98
SelectSqlExpression.CanCreateResultForCondition (cyclomatic 215)Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2.vb:935
JoinedSelectSqlExpression.CanCreateResultForCondition (cyclomatic 207)Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3.vb:119

+ 48 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Bring the 53 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with SelectSqlExpression.CanCreateResultForCondition (cyclomatic 225), WithHintsSelectSqlExpression.CanCreateResultForCondition (cyclomatic 224), JoinedSelectSqlExpression.CanCreateResultForCondition (cyclomatic 216). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 53 together lifts Cyclomatic Complexity from 5.2 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.

Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.

D2 · Cognitive Complexity5.2 / 10Adequate✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 5.2 / 10 · rule-coverage 100% · ceiling Prevented

74 method(s) exceeded the cognitive complexity threshold of 15; the worst was SelectSqlExpression.CanCreateResultForCondition at 224.

SelectSqlExpression.CanCreateResultForCondition (cognitive 224)Source/Source/Yamo/Expressions/SelectSqlExpression.vb:739
WithHintsSelectSqlExpression.CanCreateResultForCondition (cognitive 223)Source/Source/Yamo/Expressions/WithHintsSelectSqlExpression.vb:660
JoinedSelectSqlExpression.CanCreateResultForCondition (cognitive 215)Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb:98
SelectSqlExpression.CanCreateResultForCondition (cognitive 214)Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2.vb:935
JoinedSelectSqlExpression.CanCreateResultForCondition (cognitive 206)Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3.vb:119

+ 69 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Bring the 74 bodies over 15 down to 15 or less in Cognitive Complexity — start with SelectSqlExpression.CanCreateResultForCondition (cognitive 224), WithHintsSelectSqlExpression.CanCreateResultForCondition (cognitive 223), JoinedSelectSqlExpression.CanCreateResultForCondition (cognitive 215). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 74 together lifts Cognitive Complexity from 5.2 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.

Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.

D3 · God Classes8.2 / 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.

Maturity: Documented → Verified → Prevented · effective 8.2 / 10 · rule-coverage 100% · ceiling Prevented

116 god class(es) detected.

FileTooLong: Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24T25.vb · ×67Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24T25.vb
MethodTooLong: SelectSqlExpression.CanCreateResultForCondition · ×31Source/Source/Yamo/Expressions/SelectSqlExpression.vb:739
TooManyMethods: SelectedSelectSqlExpression · ×16Source/Source/Yamo/Expressions/SelectedSelectSqlExpression.vb
ClassTooLong: Join · ×2Source/Source/Yamo/JoinOfT1T2.vb

What to do

  1. Resolve the 67 FileTooLong finding(s) in God Classes — start with SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24T25.vb, SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24.vb, SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb. — One of this dimension's main actionable groups (67 warning-level).
  2. Resolve the 31 MethodTooLong finding(s) in God Classes — start with SelectSqlExpression.vb, WithHintsSelectSqlExpression.vb, JoinedSelectSqlExpressionOfT1T2.vb. — One of this dimension's main actionable groups (31 warning-level).
  3. Resolve the 16 TooManyMethods finding(s) in God Classes — start with SelectedSelectSqlExpression.vb, SelectSqlExpression.vb, FilteredSelectSqlExpression.vb. — One of this dimension's main actionable groups (16 warning-level).

Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.

D4 · Code Duplication8.7 / 10Strong✓ Tool-verified

What it measures: How much of the production code is copy-pasted: the share of production lines inside a reported copy (every copy of a duplicated block or of an edited member, each line once), 10 at none and 0 at a quarter of the lines.

Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), scored on the share of production lines inside a reported copy (each line once; 10 at none, 0 at a quarter). Deterministic.

Maturity: Documented → Verified → Prevented · effective 8.7 / 10 · rule-coverage 100% · ceiling Verified

150 duplicated block group(s) detected. 3.2 % of the production lines (8,358 of 264,009) are in a reported copy. A further 391 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 13 of the 541 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.

Edited copy of a member (2 corresponding lines) · ×56Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24T25.vb:74
Duplicated block (13 lines × 2) · ×23Source/Source/Yamo/Infrastructure/SqlResultReaderFactory.vb:193
Duplicated block (7 lines × 2) · ×11Source/Source/Yamo/Infrastructure/EntitySqlStringProviderFactory.vb:227
Duplicated block (12 lines × 2) · ×10Source/Source/Yamo.CodeGenerator/Generator/JoinSelectSqlExpressionCodeGenerator.vb:18
Duplicated block (5 lines × 3) · ×10Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8.vb:931

+ 111 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Resolve the 56 Edited copy of a member (2 corresponding lines) finding(s) in Code Duplication — start with SelectSqlExpression.vb (5), FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8.vb (2), FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7.vb (2). — One of this dimension's main actionable groups (56 warning-level).
  2. Resolve the 23 Duplicated block (13 lines × 2) finding(s) in Code Duplication — start with SqlResultReaderFactory.vb, SqlExpressionVisitor.vb, GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8.vb. — One of this dimension's main actionable groups (23 warning-level).
  3. Resolve the 11 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with EntityReaderFactory.vb (2), EntitySqlStringProviderFactory.vb, SqlExpressionVisitor.vb. — One of this dimension's main actionable groups (11 warning-level).

Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.

D5 · Coupling9.6 / 10Stronggated by 1 serious finding✓ 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.

Maturity: Documented → Verified → Prevented · effective 9.6 / 10 · rule-coverage 100% · ceiling Prevented

21 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).

Off the main sequence: Yamo(netstandard2.0)Source/Source/Yamo/Yamo.vbproj:1

What to do

  1. Resolve the 1 Off the main sequence finding(s) in Coupling — start with Yamo.vbproj. — One of this dimension's main actionable groups (1 warning-level).

Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.

D6 · Cohesion (LCOM4)8.4 / 10Strong✓ Tool-verified

What it measures: Whether a class's methods are focused on a single responsibility.

Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.

Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.

Maturity: Documented → Verified → Prevented · effective 8.4 / 10 · rule-coverage 100% · ceiling Verified

20 of 151 classes have LCOM4 above 3.

Low cohesion: MemberCallerCache (LCOM4 6) · ×5Source/Source/Yamo/Internal/MemberCallerCache.vb:11

What to do

  1. Resolve the 5 Low cohesion finding(s) in Cohesion (LCOM4) — start with MemberCallerCache.vb, EntitySqlStringProviderCache.vb, DeleteSqlExpression.vb. — One of this dimension's main actionable groups (5 warning-level).

Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.

D8 · Code Coverage1.0 / 10Critical✓ Tool-verified

What it measures: How much of the code is actually exercised by tests.

Method: Coverage from the analyzer's own run of the suite, computed per-file with structured exclusions for generated, trivial, and glue code. A coverage report found in the repository is never read. When the suite can't be built/run in-image, coverage is reported NOT-MEASURED (excluded from the score) with the precondition to make it measurable — never a LoC-ratio proxy folded in as if measured. Deterministic.

Maturity: Documented → Verified → Prevented · effective 1.0 / 10 · rule-coverage 100% · ceiling Verified

Line coverage 1.5% — 363 file(s) below 50% · 286 method(s) over the CRAP-30 risk line.

Low coverage: Source/Source/Yamo/DbContext.vb · ×363Source/Source/Yamo/DbContext.vb:1
No test project references Yamo.CodeGeneratorSource/Source/Yamo.CodeGenerator/Yamo.CodeGenerator.vbproj
CRAP 50850: SelectSqlExpression.CanCreateResultForConditionSource/Source/Yamo/Expressions/SelectSqlExpression.vb:739
CRAP 50400: WithHintsSelectSqlExpression.CanCreateResultForConditionSource/Source/Yamo/Expressions/WithHintsSelectSqlExpression.vb:660
CRAP 46872: JoinedSelectSqlExpression.CanCreateResultForConditionSource/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb:98

+ 5 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Resolve the 363 Low coverage finding(s) in Code Coverage — start with DbContext.vb, DbContextOptionsBuilder.vb, DeleteSqlExpressionBuilder.vb. — One of this dimension's main actionable groups (363 warning-level).
  2. Resolve the 1 No test project references Yamo.CodeGenerator finding(s) in Code Coverage — start with Yamo.CodeGenerator.vbproj. — One of this dimension's main actionable groups (1 warning-level).
  3. Resolve the 1 CRAP 50850 finding(s) in Code Coverage — start with SelectSqlExpression.vb. — One of this dimension's main actionable groups (1 warning-level).

Detailed fixes: d8_recommendation.md · top locations in Appendix A, every location in findings.md.

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 5 tests. Measured on the C# suite only — at least 211 test source file(s) (.vb) went unread, so its test quality is unmeasured and is not in these counts.

✓ On the Gold path — maintain.

Detailed fixes: d10_recommendation.md.

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Verified

0 flaky across 1 measured tier(s). other: measured (0 flaky).

✓ On the Gold path — maintain.

Detailed fixes: d11_recommendation.md.

D13 · Secret Scanning10.0 / 10Exemplary○ Nothing flagged

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

Secret scan ran and found no leaked secrets.

✓ On the Gold path — maintain.

Detailed fixes: d13_recommendation.md.

D14 · License Compliance10.0 / 10Exemplary○ Nothing flagged

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Verified

0 of 219 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 16 direct `PackageReference`(s), and 181 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

D15 · Churn × Complexity Hotspots10.0 / 10Exemplary✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

No churn × complexity hotspots in the window.

✓ On the Gold path — maintain.

Detailed fixes: d15_recommendation.md.

D17 · Explicit Debt10.0 / 10Stronggated by 21 serious findings✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

20 deducted debt markers + 1 dead symbols across 264009 LoC in the .NET projects (0.0/KLoC) → score 10.0.

TodoComment · ×15Source/Samples/Yamo.Playground.CS/Program.cs:408
CommentedOutCode · ×5Source/Samples/Yamo.Playground.CS/Program.cs:23
Dead code: MyContext1Source/Samples/Yamo.Playground.CS/MyContext.cs:161

What to do

  1. Resolve the 15 TodoComment finding(s) in Explicit Debt — start with CustomSelectTests.vb (3), Program.cs, SqlExpressionBase.vb. — One of this dimension's main actionable groups (15 warning-level).
  2. Resolve the 5 CommentedOutCode finding(s) in Explicit Debt — start with Program.cs (5). — One of this dimension's main actionable groups (5 warning-level).
  3. Resolve the 1 Dead code finding(s) in Explicit Debt — start with MyContext.cs. — One of this dimension's main actionable groups (1 warning-level).

Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.

D18 · Solution Shape10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether the solution is laid out in a sensible, conventional structure.

Method: Solution structure: project count, decomposition, shell-project detection, build success (confirmed failures cap the score); traced to actual .sln files and binaries. Deterministic.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

21 projects, 1998 source files, 292023 hand-written lines of code (264009 production / 28014 test — the split is derived per file: test is what its project, its own path, or a compile-guarded region marks as test, and a file carrying no test signal counts as production), plus 55 generated (machine-written code — designer, scaffolded and tool-emitted files — excluded from quality), 26 inter-project edges.

✓ On the Gold path — maintain.

Detailed fixes: d18_recommendation.md.

D19 · Documentation Quality10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether the project's documentation is clear, complete, and useful.

Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

1 of 1 documentation facets pass in full. 1 document(s) read across 1 unit(s).

✓ On the Gold path — maintain.

Detailed fixes: d19_recommendation.md.

D20 · ADR Quality0.0 / 10Critical✓ Tool-verified

What it measures: Whether architecture decisions are recorded well (context, decision, consequences).

Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Documented

No architecture decision records were found.

No ADRs foundSource/Source/Yamo.CodeGenerator/Yamo.CodeGenerator.vbproj:4

What to do

  1. Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Yamo.CodeGenerator.vbproj. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d20_recommendation.md · top locations in Appendix A, every location in findings.md.

D24 · Comment Value9.6 9.5 / 10Exemplary✓ Tool-verified

What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).

Method: Every inline C# comment compared word by word with the identifiers, literals and constructs of the code it annotates (taken from the syntax); a comment whose words that code already contains is redundant, as are closing-brace labels and generator template text. Comments giving a reason or a reference are kept; other scripts and languages are not judged. Deterministic, exhaustive, advisory.

Maturity: Documented → Verified → Prevented · effective 9.5 / 10 · rule-coverage 99% · ceiling Documented

2 of 493 judged comments only repeat the code they sit on (0.4 %). 5 comment(s) in another language or script were not judged.

redundant comment · ×2Source/Test/Yamo.Test.VB/Tests/ExpressionTests.vb:478
doc comments repeat the names · ×4Source/Source/Yamo/DbContextOptionsBuilder.vb:45

✓ On the Gold path — maintain.

Detailed fixes: d24_recommendation.md · top locations in Appendix A, every location in findings.md.

D26 · Project Cohesion8.3 / 10Strong✓ Tool-verified

What it measures: Whether each project is a focused, coherent unit rather than an oversized grab-bag.

Method: Project size overshoot penalties (LoC / public-type count / namespace count, 2-of-3 flag) weighted by log magnitude. Exhaustive across projects, deterministic.

Maturity: Documented → Verified → Prevented · effective 8.3 / 10 · rule-coverage 100% · ceiling Documented

1 of 12 projects flagged as possibly oversized/incoherent.

Projects may be oversized for their cohesionSource/Source/Yamo/Yamo.vbproj:1

What to do

  1. Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with Yamo.vbproj. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.

D27 · Navigability7.6 / 10Strong✓ Tool-verified

What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.

Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.

Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.

Maturity: Documented → Verified → Prevented · effective 7.6 / 10 · rule-coverage 100% · ceiling Documented

46 % of calls cross a namespace and 2 % go through an interface, but 71 % of collaborators are co-located — so following a call takes several hops. Baseline: large — vertical-slice locality expected.

Detailed fixes: d27_recommendation.md.

D28 · Secrets (history)10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.

Method: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

gitleaks scanned the full history AND the current working tree and found no secrets.

✓ On the Gold path — maintain.

Detailed fixes: d28_recommendation.md.

D29 · Static Analysis (SAST)10.0 / 10Exemplary○ Nothing flagged

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).

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

semgrep found no security issues.

✓ On the Gold path — maintain.

Detailed fixes: d29_recommendation.md.

D30 · Dependency Vulnerabilities8.6 / 10Adequategated by 3 critical findings✓ Tool-verified

What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.

Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.

Maturity: Documented → Verified → Prevented · effective 8.6 / 10 · rule-coverage 100% · ceiling Documented

4 finding(s): 0 critical, 3 high, 1 medium, 0 low.

REDACTED
REDACTED

What to do

  1. Resolve the 3 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 issue-level).
  2. Resolve the 1 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).

Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.

D34 · Knowledge Freshness0.0 / 10Critical✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Documented

372 of 372 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24T25.vb. Counted over 372 of the 474 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned file · ×369Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb:1
Most significant orphaned file · ×3Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24T25.vb:1
Dormant codebase

What to do

  1. Resolve the 369 Orphaned file finding(s) in Knowledge Freshness — start with DateTime.vb (2), SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb, SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb. — One of this dimension's main actionable groups (369 recommendation-level).
  2. Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24T25.vb, SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24.vb, SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb. — One of this dimension's main actionable groups (3 recommendation-level).
  3. Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.

D35 · Change Coupling10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.

Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.

Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

No strong hidden change-coupling between production files.

✓ On the Gold path — maintain.

Detailed fixes: d35_recommendation.md.

D43 · Malicious Dependencies10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Reported apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.

Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

No dependency in any ecosystem this repository declares is published as malicious.

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

D44 · Platform End-of-Life10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.

Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 12 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.

✓ On the Gold path — maintain.

Detailed fixes: d44_recommendation.md.

Frontend & cross-cutting dimensions

R = React/JS · M = Maturity · P = Readiness.

AX10 · Code composition10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does.

Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.

Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.

AX3 · Project dependency cycles10.0 / 10Exemplary✓ Tool-verified

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.

AX4 · Dependency direction10.0 / 10Exemplary✓ Tool-verified

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.

AX5 · Architecture & structure10.0 / 10Exemplary✓ Tool-verified

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.

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.

C1 · Data Protection0.0 / 10Critical✓ Tool-verified

Other · Security — Whether sensitive data is encrypted at rest and in transit and keys are vaulted.

Method: Roslyn plus filesystem scan: encryption presence (EF ColumnEncryption, key-vault references, HTTPS enforcement) and key-derivation KDF detection. Deterministic.

  • No data-protection or encryption usage (ASP.NET Data Protection, AES, column encryption, PBKDF2) was found — sensitive data at rest may be unprotected. If TDE/KMS/vault is delegated to infrastructure, ignore.

What to do

  • Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault. Skip if delegated to infra (Postgres TDE, KMS, etc.).
  • Enforce HTTPS (UseHttpsRedirection / RequireHttpsMetadata) so data in transit is always encrypted.
GD1 · Unfinished & placeholder code10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Unreviewed-generation residue: shipped members still throwing NotImplementedException, and placeholder string literals left in non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.

Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.

  • A placeholder string ("Lorem ipsum dolor sit amet.") is still in shipped code — typical of generated boilerplate that was never filled in. — Source/Samples/Yamo.Playground.CS/Program.cs:294
  • A placeholder string ("Lorem ipsum") is still in shipped code — typical of generated boilerplate that was never filled in. — Source/Samples/Yamo.Playground.CS/Program.cs:872

What to do

  • Finish or delete NotImplementedException stubs and replace placeholder literals before shipping.
M1 · Documentation (README)6.7 / 10Strong✓ Tool-verified

Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.

Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.

What to do

  • Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation0.0 / 10Critical✓ Tool-verified

Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.

Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.

  • No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
  • No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.

What to do

  • Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
  • Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure10.0 / 10Exemplary✓ Tool-verified

Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.

Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.

P1 · CI/CD gates0.0 / 10Critical✓ Tool-verified

Readiness · Readiness — Whether an automated pipeline builds and tests every change.

Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.

  • No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.

What to do

  • Add a CI workflow that builds and runs the test suite on every push/PR.
P2 · Observability4.4 / 10Adequate✓ Tool-verified

Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.

Method: Filesystem/Roslyn scan: structured-logging frameworks (Serilog, NLog), OpenTelemetry, and health-check endpoint patterns. Exhaustive, deterministic.

  • Only 1/7 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 7, 4 ship a process this repository operates; the rest are libraries their consumer hosts, where the logging decision belongs to the host.

What to do

  • Extend structured logging across the projects you operate, and give the library ones a diagnostics seam instead — an `EventSource`/`ActivitySource` the host can subscribe to, or an optional logger on your options object — rather than taking a logging dependency on your consumers' behalf.
P3 · Security & performance tooling1.0 / 10Critical✓ Tool-verified

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 a Roslyn security analyzer package referenced from the project (the analyzer packages do analyse VB.NET), plus gitleaks for committed secrets — CodeQL has no VB.NET extractor, so its csharp pack would extract nothing from this tree and then report it clean — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
  • `REDACTED` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — REDACTED:51

What to do

  • Run what this repository's stack ships: a Roslyn security analyzer package referenced from the project (the analyzer packages do analyse VB.NET), plus gitleaks for committed secrets — CodeQL has no VB.NET extractor, so its csharp pack would extract nothing from this tree and then report it clean — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add 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.
P6 · Release Hygiene5.0 / 10Adequate✓ Tool-verified

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.

  • No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)

What to do

  • Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
PF1 · Benchmark discipline7.5 / 10Strong✓ Tool-verified

Readiness · Performance — Whether the code protects its performance with benchmarks — a benchmark suite, allocation/memory measurement, and (ideally) a CI gate. Presence is credited as a bonus, never a deduction.

Method: Repo + source scan: BenchmarkDotNet referenced (csproj/source), [Benchmark]/[MemoryDiagnoser] attribute counts, and a benchmark step in CI; off .NET, the same ladder over Go testing.B, Rust criterion/#[bench]/divan, JMH/kotlinx-benchmark, pytest-benchmark/asv/pyperf, tinybench/mitata/vitest bench/benchmark.js and Swift package-benchmark — scored as a bonus ladder (absence is neutral, never a deduction). Deterministic, presence detection.

  • A BenchmarkDotNet suite exists but no [MemoryDiagnoser] — allocations (the main way hot code pressures the GC) aren't being measured.

What to do

  • Add [MemoryDiagnoser] to the benchmarks so allocation regressions are visible, not just time.
PF3 · Async & latency hygiene10.0 / 10Exemplary✓ Tool-verified

Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.

Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from each language's code model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.

X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.

Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.

X5 · Nullable reference types2.0 / 10Critical✓ Tool-verified

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.

  • 0/1 NRT-eligible project(s) enable <Nullable>enable</Nullable> (projects targeting a pre-C#-8 framework are excluded — NRTs aren't available there). NRTs catch a whole class of null-deref bugs at compile time.

What to do

  • Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.

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.

LensScoreRatingImpact
Code Health57%Adequate — gated by X5Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture96%ExemplaryStrongest area.
Maturity43%Adequate — gated by D34, M2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness30%Weak — gated by D8, P1, P3Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security43%Weak — gated by C1Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance86%ExemplarySolid.
Unscored — 1 check(s) recorded observations but carry no score

These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.

  • SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Not evidenced — 5 control(s) we could not find positive evidence for

These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.

  • C3 Audit Trail — Repo shows no audit-logging mechanism (IAuditable, an immutable audit log, an EF SaveChanges interceptor) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
  • C4 Data Retention — Repo shows no data-retention / TTL / cleanup mechanism for personal data — absence of evidence is not evidence of a working control. Define retention periods and a purge/cleanup job (or TTL) in code, or document where retention is enforced, so this dimension can be scored.
  • C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
  • P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
  • P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 67 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 web markup found — accessibility is not applicable to this repository.
  • AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
  • AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
  • AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
  • AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
  • AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
  • AX1 Captive dependencies — no DI registrations detected
  • AX2 Stateful singletons — no singleton implementations detected
  • AX6 Interface segregation — AX6 reached only 1% of this repository's production lines — vbnet (261,612 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • 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
  • AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
  • AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • 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.
  • D12 Dependency Hygiene — Dependency hygiene not measured
  • D16 Bus Factor — single-contributor repository — bus factor is not applicable
  • D21 Naming Consistency — Naming consistency does not read Visual Basic yet; not measured.
  • D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
  • D23 Boundary Type-Coupling — Cross-context type coupling could not be assessed — this codebase's bounded contexts are neither declared nor inferable.
  • D25 ADR Conformance — no ADRs to check
  • D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
  • D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
  • D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
  • D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
  • D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
  • D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
  • D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
  • D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
  • DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
  • ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
  • ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
  • ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
  • IC1 Incompleteness & stubs — reported, not scored — this repository's C# declares no analysable method bodies (a constants, record or DTO assembly), and this score is a density of unfinished work per method, which has no denominator here. The file-level signals below were still collected and are shown in full
  • M4 Documentation accuracy — Not applicable: the 1 current-state document(s) make no claim of a kind M4 checks.
  • P12 CI test-gate honesty — no CI workflow found
  • P7 Outbound HTTP resilience — not applicable — this isn't a service/API/worker
  • P8 Schema migrations — no EF Core usage detected
  • P9 Domain vs controller coverage — coverage data present for 489 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
  • PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
  • 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.
  • X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X12 Unreachable branch — X12 reached only 1% of this repository's production lines — vbnet (261,612 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X16 Unfloored truncation loop — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X2 Cancellation propagation — no async method does work a token could cancel
  • X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X21 Side-effecting pattern guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X27 Collection changed while being enumerated — X27 reached only 1% of this repository's production lines — vbnet (261,612 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X3 Exception handling — X3 reached only 1% of this repository's production lines — vbnet (261,612 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X32 Type resolved by simple name across every loaded assembly — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X4 Structured logging — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.

Critical — 3 finding(s)
D30 · Dependency Vulnerabilities · High CVE · ×3
  • REDACTED
  • REDACTED
  • REDACTED
Serious — 944 finding(s)
D8 · Code Coverage · Low coverage · ×363
  • Low coverage: Source/Source/Yamo/DbContext.vb Source/Source/Yamo/DbContext.vb:1 — 29.5% line coverage (36/122).
  • Low coverage: Source/Source/Yamo/DbContextOptionsBuilder.vb Source/Source/Yamo/DbContextOptionsBuilder.vb:1 — 46.7% line coverage (7/15).
  • Low coverage: Source/Source/Yamo/Expressions/Builders/DeleteSqlExpressionBuilder.vb Source/Source/Yamo/Expressions/Builders/DeleteSqlExpressionBuilder.vb:1 — 0.0% line coverage (0/113).
  • Low coverage: Source/Source/Yamo/Expressions/Builders/InsertSqlExpressionBuilder.vb Source/Source/Yamo/Expressions/Builders/InsertSqlExpressionBuilder.vb:1 — 0.0% line coverage (0/23).
  • Low coverage: Source/Source/Yamo/Expressions/Builders/SelectSqlExpressionBuilder.vb Source/Source/Yamo/Expressions/Builders/SelectSqlExpressionBuilder.vb:1 — 4.1% line coverage (27/664).
  • Low coverage: Source/Source/Yamo/Expressions/Builders/SqlExpressionBuilder.vb Source/Source/Yamo/Expressions/Builders/SqlExpressionBuilder.vb:1 — 0.0% line coverage (0/12).
  • Low coverage: Source/Source/Yamo/Expressions/Builders/SqlExpressionBuilderBase.vb Source/Source/Yamo/Expressions/Builders/SqlExpressionBuilderBase.vb:1 — 14.9% line coverage (13/87).
  • Low coverage: Source/Source/Yamo/Expressions/Builders/UpdateSqlExpressionBuilder.vb Source/Source/Yamo/Expressions/Builders/UpdateSqlExpressionBuilder.vb:1 — 0.0% line coverage (0/104).
  • Low coverage: Source/Source/Yamo/Expressions/CustomDistinctSelectSqlExpression.vb Source/Source/Yamo/Expressions/CustomDistinctSelectSqlExpression.vb:1 — 0.0% line coverage (0/91).
  • Low coverage: Source/Source/Yamo/Expressions/CustomSelectSqlExpression.vb Source/Source/Yamo/Expressions/CustomSelectSqlExpression.vb:1 — 0.0% line coverage (0/97).
  • Low coverage: Source/Source/Yamo/Expressions/CustomSetSelectSqlExpression.vb Source/Source/Yamo/Expressions/CustomSetSelectSqlExpression.vb:1 — 0.0% line coverage (0/92).
  • Low coverage: Source/Source/Yamo/Expressions/DeleteSqlExpression.vb Source/Source/Yamo/Expressions/DeleteSqlExpression.vb:1 — 0.0% line coverage (0/34).
  • Low coverage: Source/Source/Yamo/Expressions/DeleteSqlExpressionBase.vb Source/Source/Yamo/Expressions/DeleteSqlExpressionBase.vb:1 — 0.0% line coverage (0/5).
  • Low coverage: Source/Source/Yamo/Expressions/DistinctSelectSqlExpression.vb Source/Source/Yamo/Expressions/DistinctSelectSqlExpression.vb:1 — 0.0% line coverage (0/91).
  • Low coverage: Source/Source/Yamo/Expressions/FilteredDeleteSqlExpression.vb Source/Source/Yamo/Expressions/FilteredDeleteSqlExpression.vb:1 — 0.0% line coverage (0/7).
  • Low coverage: Source/Source/Yamo/Expressions/FilteredSelectSqlExpression.vb Source/Source/Yamo/Expressions/FilteredSelectSqlExpression.vb:1 — 0.0% line coverage (0/116).
  • Low coverage: Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2.vb Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2.vb:1 — 0.0% line coverage (0/176).
  • Low coverage: Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3.vb Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3.vb:1 — 0.0% line coverage (0/200).
  • Low coverage: Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4.vb Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4.vb:1 — 0.0% line coverage (0/218).
  • Low coverage: Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5.vb Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5.vb:1 — 0.0% line coverage (0/242).
  • Low coverage: Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6.vb Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6.vb:1 — 0.0% line coverage (0/266).
  • Low coverage: Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7.vb Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7.vb:1 — 0.0% line coverage (0/290).
  • Low coverage: Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8.vb Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8.vb:1 — 0.0% line coverage (0/308).
  • Low coverage: Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9.vb Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9.vb:1 — 0.0% line coverage (0/332).
  • Low coverage: Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10.vb Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10.vb:1 — 0.0% line coverage (0/356).
  • + 338 more in this group — see findings.md.
D3 · God Classes · FileTooLong · ×67
  • FileTooLong: Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24T25.vb Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24T25.vb — FileTooLong — 2232 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1732 over it, 4.46× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24.vb Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24.vb — FileTooLong — 2076 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1576 over it, 4.15× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb — FileTooLong — 1926 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1426 over it, 3.85× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb — FileTooLong — 1782 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1282 over it, 3.56× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb — FileTooLong — 1644 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1144 over it, 3.29× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb — FileTooLong — 1512 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1012 over it, 3.02× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb — FileTooLong — 1386 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 886 over it, 2.77× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18.vb Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18.vb — FileTooLong — 1266 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 766 over it, 2.53× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17.vb Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17.vb — FileTooLong — 1152 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 652 over it, 2.30× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: Internal/SqlExpressionVisitor.vb Source/Source/Yamo/Internal/SqlExpressionVisitor.vb — FileTooLong — 1061 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 561 over it, 2.12× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16.vb Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16.vb — FileTooLong — 1044 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 544 over it, 2.09× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15.vb Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15.vb — FileTooLong — 942 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 442 over it, 1.88× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14.vb Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14.vb — FileTooLong — 846 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 346 over it, 1.69× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24.vb Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24.vb — FileTooLong — 821 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 321 over it, 1.64× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb — FileTooLong — 806 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 306 over it, 1.61× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb — FileTooLong — 791 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 291 over it, 1.58× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb — FileTooLong — 776 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 276 over it, 1.55× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb — FileTooLong — 761 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 261 over it, 1.52× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13.vb Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13.vb — FileTooLong — 756 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 256 over it, 1.51× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb — FileTooLong — 746 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 246 over it, 1.49× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24T25.vb Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24T25.vb — FileTooLong — 738 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 238 over it, 1.48× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18.vb Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18.vb — FileTooLong — 731 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 231 over it, 1.46× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24T25.vb Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24T25.vb — FileTooLong — 726 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 226 over it, 1.45× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17.vb Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17.vb — FileTooLong — 716 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 216 over it, 1.43× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: Builders/SelectSqlExpressionBuilder.vb Source/Source/Yamo/Expressions/Builders/SelectSqlExpressionBuilder.vb — FileTooLong — 703 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 203 over it, 1.41× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • + 42 more in this group — see findings.md.
D4 · Code Duplication · Edited copy of a member (2 corresponding lines) · ×56
  • Edited copy of a member (2 corresponding lines) Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24T25.vb:74 — Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24T25.vb:74-75 | Source/Source/Yamo/Expressions/JoinWithHintsSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24T25.vb:64-65 — These two members are one piece of code written twice and then edited apart: 2 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (2 corresponding lines) Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24.vb:73 — Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24.vb:73-74 | Source/Source/Yamo/Expressions/JoinWithHintsSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24.vb:63-64 — These two members are one piece of code written twice and then edited apart: 2 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (2 corresponding lines) Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb:72 — Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb:72-73 | Source/Source/Yamo/Expressions/JoinWithHintsSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb:62-63 — These two members are one piece of code written twice and then edited apart: 2 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (2 corresponding lines) Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb:71 — Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb:71-72 | Source/Source/Yamo/Expressions/JoinWithHintsSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb:61-62 — These two members are one piece of code written twice and then edited apart: 2 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (2 corresponding lines) Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb:70 — Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb:70-71 | Source/Source/Yamo/Expressions/JoinWithHintsSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb:60-61 — These two members are one piece of code written twice and then edited apart: 2 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (2 corresponding lines) Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb:69 — Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb:69-70 | Source/Source/Yamo/Expressions/JoinWithHintsSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb:59-60 — These two members are one piece of code written twice and then edited apart: 2 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (2 corresponding lines) Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:68 — Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:68-69 | Source/Source/Yamo/Expressions/JoinWithHintsSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:58-59 — These two members are one piece of code written twice and then edited apart: 2 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (2 corresponding lines) Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24T25.vb:533 — Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24T25.vb:533-534 | Source/Source/Yamo/Expressions/OrderedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24T25.vb:559-560 — These two members are one piece of code written twice and then edited apart: 2 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (2 corresponding lines) Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18.vb:67 — Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18.vb:67-68 | Source/Source/Yamo/Expressions/JoinWithHintsSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18.vb:57-58 — These two members are one piece of code written twice and then edited apart: 2 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (2 corresponding lines) Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24.vb:514 — Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24.vb:514-515 | Source/Source/Yamo/Expressions/OrderedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24.vb:539-540 — These two members are one piece of code written twice and then edited apart: 2 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (2 corresponding lines) Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17.vb:66 — Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17.vb:66-67 | Source/Source/Yamo/Expressions/JoinWithHintsSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17.vb:56-57 — These two members are one piece of code written twice and then edited apart: 2 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (2 corresponding lines) Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb:495 — Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb:495-496 | Source/Source/Yamo/Expressions/OrderedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb:519-520 — These two members are one piece of code written twice and then edited apart: 2 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (2 corresponding lines) Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16.vb:65 — Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16.vb:65-66 | Source/Source/Yamo/Expressions/JoinWithHintsSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16.vb:55-56 — These two members are one piece of code written twice and then edited apart: 2 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (2 corresponding lines) Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb:476 — Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb:476-477 | Source/Source/Yamo/Expressions/OrderedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb:499-500 — These two members are one piece of code written twice and then edited apart: 2 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (2 corresponding lines) Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15.vb:64 — Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15.vb:64-65 | Source/Source/Yamo/Expressions/JoinWithHintsSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15.vb:54-55 — These two members are one piece of code written twice and then edited apart: 2 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (2 corresponding lines) Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb:457 — Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb:457-458 | Source/Source/Yamo/Expressions/OrderedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb:479-480 — These two members are one piece of code written twice and then edited apart: 2 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (2 corresponding lines) Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14.vb:63 — Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14.vb:63-64 | Source/Source/Yamo/Expressions/JoinWithHintsSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14.vb:53-54 — These two members are one piece of code written twice and then edited apart: 2 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (2 corresponding lines) Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb:438 — Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb:438-439 | Source/Source/Yamo/Expressions/OrderedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb:459-460 — These two members are one piece of code written twice and then edited apart: 2 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (2 corresponding lines) Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13.vb:62 — Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13.vb:62-63 | Source/Source/Yamo/Expressions/JoinWithHintsSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13.vb:52-53 — These two members are one piece of code written twice and then edited apart: 2 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (2 corresponding lines) Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:419 — Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:419-420 | Source/Source/Yamo/Expressions/OrderedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:439-440 — These two members are one piece of code written twice and then edited apart: 2 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (2 corresponding lines) Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12.vb:61 — Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12.vb:61-62 | Source/Source/Yamo/Expressions/JoinWithHintsSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12.vb:51-52 — These two members are one piece of code written twice and then edited apart: 2 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (2 corresponding lines) Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18.vb:400 — Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18.vb:400-401 | Source/Source/Yamo/Expressions/OrderedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18.vb:419-420 — These two members are one piece of code written twice and then edited apart: 2 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (2 corresponding lines) Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11.vb:60 — Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11.vb:60-61 | Source/Source/Yamo/Expressions/JoinWithHintsSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11.vb:50-51 — These two members are one piece of code written twice and then edited apart: 2 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (2 corresponding lines) Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17.vb:381 — Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17.vb:381-382 | Source/Source/Yamo/Expressions/OrderedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17.vb:399-400 — These two members are one piece of code written twice and then edited apart: 2 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (2 corresponding lines) Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10.vb:59 — Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10.vb:59-60 | Source/Source/Yamo/Expressions/JoinWithHintsSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10.vb:49-50 — These two members are one piece of code written twice and then edited apart: 2 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • + 31 more in this group — see findings.md.
D3 · God Classes · MethodTooLong · ×31
  • MethodTooLong: SelectSqlExpression.CanCreateResultForCondition Source/Source/Yamo/Expressions/SelectSqlExpression.vb:739 — MethodTooLong — CanCreateResultForCondition runs 232 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 132 over it, 2.32× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: WithHintsSelectSqlExpression.CanCreateResultForCondition Source/Source/Yamo/Expressions/WithHintsSelectSqlExpression.vb:660 — MethodTooLong — CanCreateResultForCondition runs 231 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 131 over it, 2.31× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: JoinedSelectSqlExpression.CanCreateResultForCondition Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb:98 — MethodTooLong — CanCreateResultForCondition runs 223 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 123 over it, 2.23× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: SelectSqlExpression.CanCreateResultForCondition Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2.vb:935 — MethodTooLong — CanCreateResultForCondition runs 222 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 122 over it, 2.22× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: JoinedSelectSqlExpression.CanCreateResultForCondition Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3.vb:119 — MethodTooLong — CanCreateResultForCondition runs 214 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 114 over it, 2.14× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: SelectSqlExpression.CanCreateResultForCondition Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3.vb:1013 — MethodTooLong — CanCreateResultForCondition runs 213 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 113 over it, 2.13× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: JoinedSelectSqlExpression.CanCreateResultForCondition Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4.vb:130 — MethodTooLong — CanCreateResultForCondition runs 205 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 105 over it, 2.05× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: SelectSqlExpression.CanCreateResultForCondition Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4.vb:1113 — MethodTooLong — CanCreateResultForCondition runs 204 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 104 over it, 2.04× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: JoinedSelectSqlExpression.CanCreateResultForCondition Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5.vb:141 — MethodTooLong — CanCreateResultForCondition runs 196 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 96 over it, 1.96× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: SelectSqlExpression.CanCreateResultForCondition Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5.vb:1231 — MethodTooLong — CanCreateResultForCondition runs 195 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 95 over it, 1.95× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: JoinedSelectSqlExpression.CanCreateResultForCondition Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6.vb:152 — MethodTooLong — CanCreateResultForCondition runs 187 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 87 over it, 1.87× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: SelectSqlExpression.CanCreateResultForCondition Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6.vb:1349 — MethodTooLong — CanCreateResultForCondition runs 186 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 86 over it, 1.86× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: JoinedSelectSqlExpression.CanCreateResultForCondition Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7.vb:163 — MethodTooLong — CanCreateResultForCondition runs 178 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 78 over it, 1.78× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: SelectSqlExpression.CanCreateResultForCondition Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7.vb:1187 — MethodTooLong — CanCreateResultForCondition runs 177 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 77 over it, 1.77× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: JoinedSelectSqlExpression.CanCreateResultForCondition Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8.vb:174 — MethodTooLong — CanCreateResultForCondition runs 169 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 69 over it, 1.69× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: SelectSqlExpression.CanCreateResultForCondition Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8.vb:1244 — MethodTooLong — CanCreateResultForCondition runs 168 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 68 over it, 1.68× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: JoinedSelectSqlExpression.CanCreateResultForCondition Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9.vb:185 — MethodTooLong — CanCreateResultForCondition runs 160 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 60 over it, 1.60× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: SelectSqlExpression.CanCreateResultForCondition Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9.vb:1322 — MethodTooLong — CanCreateResultForCondition runs 159 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 59 over it, 1.59× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: JoinedSelectSqlExpression.CanCreateResultForCondition Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10.vb:196 — MethodTooLong — CanCreateResultForCondition runs 151 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 51 over it, 1.51× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: SelectSqlExpression.CanCreateResultForCondition Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10.vb:1400 — MethodTooLong — CanCreateResultForCondition runs 150 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 50 over it, 1.50× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: JoinedSelectSqlExpression.CanCreateResultForCondition Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11.vb:207 — MethodTooLong — CanCreateResultForCondition runs 142 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 42 over it, 1.42× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: SelectSqlExpression.CanCreateResultForCondition Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11.vb:1478 — MethodTooLong — CanCreateResultForCondition runs 141 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 41 over it, 1.41× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: JoinedSelectSqlExpression.CanCreateResultForCondition Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12.vb:218 — MethodTooLong — CanCreateResultForCondition runs 133 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 33 over it, 1.33× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: SelectSqlExpression.CanCreateResultForCondition Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12.vb:1556 — MethodTooLong — CanCreateResultForCondition runs 132 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 32 over it, 1.32× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: JoinedSelectSqlExpression.CanCreateResultForCondition Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13.vb:229 — MethodTooLong — CanCreateResultForCondition runs 124 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 24 over it, 1.24× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • + 6 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (13 lines × 2) · ×23
  • Duplicated block (13 lines × 2) Source/Source/Yamo/Infrastructure/SqlResultReaderFactory.vb:193 — Source/Source/Yamo/Infrastructure/SqlResultReaderFactory.vb:193-205 | Source/Source/Yamo/Infrastructure/SqlResultReaderFactory.vb:232-244 — both copies are in the same file, so extract the 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) Source/Source/Yamo/Internal/SqlExpressionVisitor.vb:1862 — Source/Source/Yamo/Internal/SqlExpressionVisitor.vb:1862-1874 | Source/Source/Yamo/Internal/SqlExpressionVisitor.vb:1913-1925 — both copies are in the same file, so extract the 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) Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8.vb:815 — Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8.vb:815-827 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8.vb:807-819 — before extracting anything, compare `Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8.vb` and `Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8.vb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (13 lines × 2) Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9.vb:883 — Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9.vb:883-895 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9.vb:875-887 — before extracting anything, compare `Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9.vb` and `Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9.vb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (13 lines × 2) Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10.vb:951 — Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10.vb:951-963 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10.vb:943-955 — before extracting anything, compare `Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10.vb` and `Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10.vb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (13 lines × 2) Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11.vb:1019 — Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11.vb:1019-1031 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11.vb:1011-1023 — before extracting anything, compare `Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11.vb` and `Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11.vb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (13 lines × 2) Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12.vb:1087 — Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12.vb:1087-1099 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12.vb:1079-1091 — before extracting anything, compare `Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12.vb` and `Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12.vb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (13 lines × 2) Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13.vb:1155 — Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13.vb:1155-1167 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13.vb:1147-1159 — before extracting anything, compare `Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13.vb` and `Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13.vb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (13 lines × 2) Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14.vb:1223 — Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14.vb:1223-1235 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14.vb:1215-1227 — before extracting anything, compare `Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14.vb` and `Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14.vb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (13 lines × 2) Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15.vb:1291 — Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15.vb:1291-1303 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15.vb:1283-1295 — before extracting anything, compare `Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15.vb` and `Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15.vb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (13 lines × 2) Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16.vb:1359 — Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16.vb:1359-1371 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16.vb:1351-1363 — before extracting anything, compare `Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16.vb` and `Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16.vb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (13 lines × 2) Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17.vb:1427 — Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17.vb:1427-1439 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17.vb:1419-1431 — before extracting anything, compare `Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17.vb` and `Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17.vb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (13 lines × 2) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7.vb:164 — Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7.vb:164-176 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6.vb:1350-1362 — before extracting anything, compare `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7.vb` and `Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6.vb` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 111 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (13 lines × 2) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8.vb:175 — Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8.vb:175-187 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7.vb:1188-1200 — before extracting anything, compare `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8.vb` and `Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7.vb` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 123 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (13 lines × 2) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9.vb:186 — Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9.vb:186-198 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8.vb:1245-1257 — before extracting anything, compare `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9.vb` and `Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8.vb` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 123 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (13 lines × 2) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10.vb:197 — Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10.vb:197-209 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9.vb:1323-1335 — before extracting anything, compare `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10.vb` and `Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9.vb` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 118 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (13 lines × 2) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11.vb:208 — Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11.vb:208-220 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10.vb:1401-1413 — before extracting anything, compare `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11.vb` and `Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10.vb` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 103 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (13 lines × 2) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12.vb:219 — Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12.vb:219-231 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11.vb:1479-1491 — before extracting anything, compare `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12.vb` and `Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11.vb` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 103 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (13 lines × 2) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13.vb:230 — Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13.vb:230-242 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12.vb:1557-1569 — before extracting anything, compare `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13.vb` and `Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12.vb` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 103 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (13 lines × 2) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14.vb:241 — Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14.vb:241-253 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13.vb:1635-1647 — before extracting anything, compare `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14.vb` and `Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13.vb` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 103 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (13 lines × 2) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15.vb:252 — Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15.vb:252-264 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14.vb:1713-1725 — before extracting anything, compare `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15.vb` and `Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14.vb` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 103 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (13 lines × 2) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16.vb:263 — Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16.vb:263-275 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15.vb:1791-1803 — before extracting anything, compare `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16.vb` and `Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15.vb` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 115 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (13 lines × 2) Source/Source/Yamo/Expressions/UpdateSqlExpression.vb:109 — Source/Source/Yamo/Expressions/UpdateSqlExpression.vb:109-121 | Source/Source/Yamo/Expressions/WithHintsUpdateSqlExpression.vb:100-112 — before extracting anything, compare `Source/Source/Yamo/Expressions/UpdateSqlExpression.vb` and `Source/Source/Yamo/Expressions/WithHintsUpdateSqlExpression.vb` as WHOLE FILES: 87% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D3 · God Classes · TooManyMethods · ×16
  • TooManyMethods: SelectedSelectSqlExpression Source/Source/Yamo/Expressions/SelectedSelectSqlExpression.vb — TooManyMethods — 22612 significant lines (blank, comment-only and punctuation-only lines excluded), 7221 methods. The bar is 30 methods; this is 7191 over it, 240.70× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: SelectSqlExpression Source/Source/Yamo/Expressions/SelectSqlExpression.vb — TooManyMethods — 16447 significant lines (blank, comment-only and punctuation-only lines excluded), 4075 methods. The bar is 30 methods; this is 4045 over it, 135.83× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: FilteredSelectSqlExpression Source/Source/Yamo/Expressions/FilteredSelectSqlExpression.vb — TooManyMethods — 10824 significant lines (blank, comment-only and punctuation-only lines excluded), 3258 methods. The bar is 30 methods; this is 3228 over it, 108.60× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: GroupedSelectSqlExpression Source/Source/Yamo/Expressions/GroupedSelectSqlExpression.vb — TooManyMethods — 9584 significant lines (blank, comment-only and punctuation-only lines excluded), 2878 methods. The bar is 30 methods; this is 2848 over it, 95.93× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: HavingSelectSqlExpression Source/Source/Yamo/Expressions/HavingSelectSqlExpression.vb — TooManyMethods — 9509 significant lines (blank, comment-only and punctuation-only lines excluded), 2853 methods. The bar is 30 methods; this is 2823 over it, 95.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: OrderedSelectSqlExpression Source/Source/Yamo/Expressions/OrderedSelectSqlExpression.vb — TooManyMethods — 7178 significant lines (blank, comment-only and punctuation-only lines excluded), 2101 methods. The bar is 30 methods; this is 2071 over it, 70.03× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: LimitedSelectSqlExpression Source/Source/Yamo/Expressions/LimitedSelectSqlExpression.vb — TooManyMethods — 1715 significant lines (blank, comment-only and punctuation-only lines excluded), 480 methods. The bar is 30 methods; this is 450 over it, 16.00× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: JoinedSelectSqlExpression Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb — TooManyMethods — 4749 significant lines (blank, comment-only and punctuation-only lines excluded), 443 methods. The bar is 30 methods; this is 413 over it, 14.77× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: CodeGenerator Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.As.vb — TooManyMethods — 2489 significant lines (blank, comment-only and punctuation-only lines excluded), 215 methods. The bar is 30 methods; this is 185 over it, 7.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: JoinSelectSqlExpression Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2.vb — TooManyMethods — 1218 significant lines (blank, comment-only and punctuation-only lines excluded), 190 methods. The bar is 30 methods; this is 160 over it, 6.33× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: JoinWithHintsSelectSqlExpression Source/Source/Yamo/Expressions/JoinWithHintsSelectSqlExpressionOfT1T2.vb — TooManyMethods — 546 significant lines (blank, comment-only and punctuation-only lines excluded), 118 methods. The bar is 30 methods; this is 88 over it, 3.93× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: WithHintsSelectSqlExpression Source/Source/Yamo/Expressions/WithHintsSelectSqlExpression.vb — TooManyMethods — 457 significant lines (blank, comment-only and punctuation-only lines excluded), 60 methods. The bar is 30 methods; this is 30 over it, 2.00× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: SqlExpressionVisitor Source/Source/Yamo/Internal/SqlExpressionVisitor.vb — TooManyMethods — 1049 significant lines (blank, comment-only and punctuation-only lines excluded), 58 methods. The bar is 30 methods; this is 28 over it, 1.93× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: SelectSqlExpressionBuilder Source/Source/Yamo/Expressions/Builders/SelectSqlExpressionBuilder.vb — TooManyMethods — 693 significant lines (blank, comment-only and punctuation-only lines excluded), 50 methods. The bar is 30 methods; this is 20 over it, 1.67× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: DbContext Source/Source/Yamo/DbContext.vb — TooManyMethods — 135 significant lines (blank, comment-only and punctuation-only lines excluded), 32 methods. The bar is 30 methods; this is 2 over it, 1.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: ValueTypeReaderFactory Source/Source/Yamo/Infrastructure/ValueTypeReaderFactory.vb — TooManyMethods — 300 significant lines (blank, comment-only and punctuation-only lines excluded), 31 methods. The bar is 30 methods; this is 1 over it, 1.03× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D17 · Explicit Debt · TodoComment · ×15
  • TodoComment Source/Samples/Yamo.Playground.CS/Program.cs:408 — // TODO: to many brackets in ON clause (update readme.md when fixed). — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment Source/Source/Yamo/Expressions/SqlExpressionBase.vb:11 — ' TODO: SIP - move here from children? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `' REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment Source/Source/Yamo/Internal/Helpers/Types.vb:198 — ' TODO: SIP - this won't work if model entity is a structure! — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `' REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment Source/Source/Yamo/Internal/NodeInfo.vb:12 — ' TODO: SIP - is really IsCompare, IsCoalesce, IsConditional, ... necessary? Would't it be better to check it when needed (during boolean expansion)?. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `' REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment Source/Source/Yamo/Internal/Query/IncludedSqlResultReaderData.vb:11 — ' TODO: SIP - structure instead? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `' REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment Source/Source/Yamo/Internal/Query/Metadata/SqlEntityIncludedResult.vb:11 — ' TODO: SIP - structure instead? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `' REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment Source/Source/Yamo/Internal/Query/Metadata/SqlEntityRelationship.vb:12 — ' TODO: SIP - structure instead? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `' REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment Source/Source/Yamo/Internal/Query/QueryExecutor.vb:18 — ' TODO: SIP - rewrite as static class (one allocation less...)? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `' REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment Source/Source/Yamo/Internal/SqlExpressionVisitor.vb:392 — ' TODO: SIP - investigate how indexers behave and whether they can cause a problem here — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `' REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment Source/Test/Yamo.Test.VB/Tests/ExpressionTests.vb:1507 — ' TODO: SIP - fix: "nullable.HasValue = True" — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `' REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment Source/Test/Yamo.Test/Tests/CustomSelectTests.vb:1459 — ' TODO: SIP - is it worth to add support for negation in selects? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `' REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment Source/Test/Yamo.Test/Tests/CustomSelectTests.vb:1475 — ' TODO: SIP - is it worth to add support for conversion to non-null value for scenarios like this? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `' REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment Source/Test/Yamo.Test/Tests/CustomSelectTests.vb:1486 — ' TODO: SIP - is it worth to add support for null value detection for scenarios like this? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `' REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment Source/Test/Yamo.Test/Tests/SelectWithConditionTests.vb:1393 — ' TODO: SIP - what about using SQL helper here? Write test also for this! — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `' REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment Source/Test/Yamo.Test/Tests/SelectWithJoinTests.vb:1830 — ' TODO: SIP - test also 1:N relationships — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `' REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
D4 · Code Duplication · Duplicated block (7 lines × 2) · ×11
  • Duplicated block (7 lines × 2) Source/Source/Yamo/Infrastructure/EntitySqlStringProviderFactory.vb:227 — Source/Source/Yamo/Infrastructure/EntitySqlStringProviderFactory.vb:227-233 | Source/Source/Yamo/Infrastructure/EntitySqlStringProviderFactory.vb:319-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.
  • Duplicated block (7 lines × 2) Source/Source/Yamo/Internal/SqlExpressionVisitor.vb:270 — Source/Source/Yamo/Internal/SqlExpressionVisitor.vb:270-276 | Source/Source/Yamo/Internal/SqlExpressionVisitor.vb:302-308 — both copies are in the same file, so extract the 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) Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.OrderBy.vb:121 — Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.OrderBy.vb:121-127 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.OrderBy.vb:134-140 — both copies are in the same file, so extract the 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) Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.ThenBy.vb:121 — Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.ThenBy.vb:121-127 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.ThenBy.vb:134-140 — both copies are in the same file, so extract the 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) Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.ToList.vb:6 — Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.ToList.vb:6-12 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.ToList.vb:18-24 — both copies are in the same file, so extract the 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) Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Where.And.vb:132 — Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Where.And.vb:132-138 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Where.And.vb:145-151 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (7 lines × 2) Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Where.vb:135 — Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Where.vb:135-141 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Where.vb:148-154 — both copies are in the same file, so extract the 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) Source/Source/Yamo/Infrastructure/EntityReaderFactory.vb:371 — Source/Source/Yamo/Infrastructure/EntityReaderFactory.vb:371-377 | Source/Source/Yamo/Infrastructure/SqlResultReaderFactory.vb:454-460 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (7 lines × 2) Source/Source/Yamo/Infrastructure/EntityReaderFactory.vb:387 — Source/Source/Yamo/Infrastructure/EntityReaderFactory.vb:387-393 | Source/Source/Yamo/Infrastructure/SqlResultReaderFactory.vb:470-476 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (7 lines × 2) Source/Samples/Yamo.Playground.CS/MyContext.cs:67 — Source/Samples/Yamo.Playground.CS/MyContext.cs:67-73 | Source/Samples/Yamo.Playground.CS/MyContext.cs:204-210 — both copies are in the same file, so extract the 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) Source/Samples/Yamo.Playground.CS/Program.cs:1219 — Source/Samples/Yamo.Playground.CS/Program.cs:1219-1225 | Source/Samples/Yamo.Playground.CS/Program.cs:1307-1313 — both copies are in the same file, so extract the 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 `Source/Samples/Yamo.Playground.CS/Program.cs:1219` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (12 lines × 2) · ×10
  • Duplicated block (12 lines × 2) Source/Source/Yamo.CodeGenerator/Generator/JoinSelectSqlExpressionCodeGenerator.vb:18 — Source/Source/Yamo.CodeGenerator/Generator/JoinSelectSqlExpressionCodeGenerator.vb:18-29 | Source/Source/Yamo.CodeGenerator/Generator/JoinedSelectSqlExpressionCodeGenerator.vb:26-37 — before extracting anything, compare `Source/Source/Yamo.CodeGenerator/Generator/JoinSelectSqlExpressionCodeGenerator.vb` and `Source/Source/Yamo.CodeGenerator/Generator/JoinedSelectSqlExpressionCodeGenerator.vb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 35 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (12 lines × 2) Source/Source/Yamo.CodeGenerator/Generator/SelectSqlExpressionCodeGenerator.vb:27 — Source/Source/Yamo.CodeGenerator/Generator/SelectSqlExpressionCodeGenerator.vb:27-38 | Source/Source/Yamo.CodeGenerator/Generator/WithHintsSelectSqlExpressionCodeGenerator.vb:26-37 — before extracting anything, compare `Source/Source/Yamo.CodeGenerator/Generator/SelectSqlExpressionCodeGenerator.vb` and `Source/Source/Yamo.CodeGenerator/Generator/WithHintsSelectSqlExpressionCodeGenerator.vb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 83 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (12 lines × 2) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17.vb:274 — Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17.vb:274-285 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16.vb:1869-1880 — before extracting anything, compare `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17.vb` and `Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16.vb` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 114 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (12 lines × 2) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18.vb:285 — Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18.vb:285-296 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17.vb:1947-1958 — before extracting anything, compare `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18.vb` and `Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17.vb` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 114 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (12 lines × 2) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:296 — Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:296-307 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18.vb:2025-2036 — before extracting anything, compare `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb` and `Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18.vb` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 123 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (12 lines × 2) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb:307 — Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb:307-318 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:2103-2114 — before extracting anything, compare `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb` and `Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 123 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (12 lines × 2) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb:318 — Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb:318-329 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb:2181-2192 — before extracting anything, compare `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb` and `Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 123 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (12 lines × 2) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb:329 — Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb:329-340 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb:2259-2270 — before extracting anything, compare `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb` and `Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 123 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb:2273` calls `GetType`, `JoinSelectSqlExpression` and `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb:343` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (12 lines × 2) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb:340 — Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb:340-351 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb:2337-2348 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb:2350` calls `GetType`, `JoinSelectSqlExpression` and `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb:353` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (12 lines × 2) Source/Source/Yamo/Expressions/CustomDistinctSelectSqlExpression.vb:216 — Source/Source/Yamo/Expressions/CustomDistinctSelectSqlExpression.vb:216-227 | Source/Source/Yamo/Expressions/DistinctSelectSqlExpression.vb:216-227 — before extracting anything, compare `Source/Source/Yamo/Expressions/CustomDistinctSelectSqlExpression.vb` and `Source/Source/Yamo/Expressions/DistinctSelectSqlExpression.vb` as WHOLE FILES: 87% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (5 lines × 3) · ×10
  • Duplicated block (5 lines × 3) Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8.vb:931 — Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8.vb:931-935 | Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8.vb:825-829 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8.vb:817-821 — before extracting anything, compare `Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8.vb` and `Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8.vb` as WHOLE FILES: 84% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8.vb:929` calls `GetType`, `FilteredSelectSqlExpression`, `GroupedSelectSqlExpression` and `Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8.vb:823` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (5 lines × 3) Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9.vb:1009 — Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9.vb:1009-1013 | Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9.vb:893-897 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9.vb:885-889 — before extracting anything, compare `Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9.vb` and `Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9.vb` as WHOLE FILES: 84% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9.vb:1007` calls `GetType`, `FilteredSelectSqlExpression`, `GroupedSelectSqlExpression` and `Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9.vb:891` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (5 lines × 3) Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10.vb:1087 — Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10.vb:1087-1091 | Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10.vb:961-965 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10.vb:953-957 — before extracting anything, compare `Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10.vb` and `Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10.vb` as WHOLE FILES: 84% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10.vb:1085` calls `GetType`, `FilteredSelectSqlExpression`, `GroupedSelectSqlExpression` and `Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10.vb:959` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (5 lines × 3) Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11.vb:1165 — Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11.vb:1165-1169 | Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11.vb:1029-1033 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11.vb:1021-1025 — before extracting anything, compare `Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11.vb` and `Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11.vb` as WHOLE FILES: 84% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11.vb:1163` calls `GetType`, `FilteredSelectSqlExpression`, `GroupedSelectSqlExpression` and `Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11.vb:1027` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (5 lines × 3) Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12.vb:1243 — Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12.vb:1243-1247 | Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12.vb:1097-1101 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12.vb:1089-1093 — before extracting anything, compare `Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12.vb` and `Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12.vb` as WHOLE FILES: 84% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12.vb:1241` calls `GetType`, `FilteredSelectSqlExpression`, `GroupedSelectSqlExpression` and `Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12.vb:1095` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (5 lines × 3) Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13.vb:1321 — Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13.vb:1321-1325 | Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13.vb:1165-1169 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13.vb:1157-1161 — before extracting anything, compare `Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13.vb` and `Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13.vb` as WHOLE FILES: 84% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13.vb:1319` calls `GetType`, `FilteredSelectSqlExpression`, `GroupedSelectSqlExpression` and `Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13.vb:1163` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (5 lines × 3) Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14.vb:1399 — Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14.vb:1399-1403 | Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14.vb:1233-1237 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14.vb:1225-1229 — before extracting anything, compare `Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14.vb` and `Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14.vb` as WHOLE FILES: 84% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14.vb:1397` calls `GetType`, `FilteredSelectSqlExpression`, `GroupedSelectSqlExpression` and `Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14.vb:1231` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (5 lines × 3) Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15.vb:1477 — Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15.vb:1477-1481 | Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15.vb:1301-1305 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15.vb:1293-1297 — before extracting anything, compare `Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15.vb` and `Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15.vb` as WHOLE FILES: 84% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15.vb:1475` calls `GetType`, `FilteredSelectSqlExpression`, `GroupedSelectSqlExpression` and `Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15.vb:1299` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (5 lines × 3) Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16.vb:1555 — Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16.vb:1555-1559 | Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16.vb:1369-1373 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16.vb:1361-1365 — before extracting anything, compare `Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16.vb` and `Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16.vb` as WHOLE FILES: 84% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16.vb:1553` calls `GetType`, `FilteredSelectSqlExpression`, `GroupedSelectSqlExpression` and `Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16.vb:1367` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (5 lines × 3) Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17.vb:1633 — Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17.vb:1633-1637 | Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17.vb:1437-1441 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17.vb:1429-1433 — before extracting anything, compare `Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17.vb` and `Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17.vb` as WHOLE FILES: 84% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17.vb:1631` calls `GetType`, `FilteredSelectSqlExpression`, `GroupedSelectSqlExpression` and `Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17.vb:1435` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (15 lines × 2) · ×8
  • Duplicated block (15 lines × 2) Source/Source/Yamo/Expressions/GroupedSelectSqlExpression.vb:271 — Source/Source/Yamo/Expressions/GroupedSelectSqlExpression.vb:271-285 | Source/Source/Yamo/Expressions/HavingSelectSqlExpression.vb:263-277 — before extracting anything, compare `Source/Source/Yamo/Expressions/GroupedSelectSqlExpression.vb` and `Source/Source/Yamo/Expressions/HavingSelectSqlExpression.vb` as WHOLE FILES: 93% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (15 lines × 2) Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2.vb:436 — Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2.vb:436-450 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2.vb:428-442 — before extracting anything, compare `Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2.vb` and `Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2.vb` as WHOLE FILES: 93% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (15 lines × 2) Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3.vb:504 — Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3.vb:504-518 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3.vb:496-510 — before extracting anything, compare `Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3.vb` and `Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3.vb` as WHOLE FILES: 93% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (15 lines × 2) Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4.vb:554 — Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4.vb:554-568 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4.vb:546-560 — before extracting anything, compare `Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4.vb` and `Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4.vb` as WHOLE FILES: 93% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (15 lines × 2) Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5.vb:622 — Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5.vb:622-636 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5.vb:614-628 — before extracting anything, compare `Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5.vb` and `Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5.vb` as WHOLE FILES: 93% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (15 lines × 2) Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6.vb:690 — Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6.vb:690-704 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6.vb:682-696 — before extracting anything, compare `Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6.vb` and `Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6.vb` as WHOLE FILES: 93% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (15 lines × 2) Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7.vb:758 — Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7.vb:758-772 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7.vb:750-764 — before extracting anything, compare `Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7.vb` and `Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7.vb` as WHOLE FILES: 93% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (15 lines × 2) Source/Source/Yamo/Internal/Query/ReaderDataFactory.vb:107 — Source/Source/Yamo/Internal/Query/ReaderDataFactory.vb:107-121 | Source/Source/Yamo/Internal/Query/ReaderDataFactory.vb:168-182 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (8 lines × 2) · ×6
  • Duplicated block (8 lines × 2) Source/Source/Yamo.CodeGenerator/Generator/SelectSqlExpressionCodeGenerator.vb:114 — Source/Source/Yamo.CodeGenerator/Generator/SelectSqlExpressionCodeGenerator.vb:114-121 | Source/Source/Yamo.CodeGenerator/Generator/SelectSqlExpressionCodeGenerator.vb:136-143 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (8 lines × 2) Source/Source/Yamo.CodeGenerator/Generator/SelectSqlExpressionCodeGenerator.vb:125 — Source/Source/Yamo.CodeGenerator/Generator/SelectSqlExpressionCodeGenerator.vb:125-132 | Source/Source/Yamo.CodeGenerator/Generator/SelectSqlExpressionCodeGenerator.vb:147-154 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (8 lines × 2) Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Having.And.vb:124 — Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Having.And.vb:124-131 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Having.vb:138-145 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (8 lines × 2) Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.OrderBy.vb:212 — Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.OrderBy.vb:212-219 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.ThenBy.vb:212-219 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (8 lines × 2) Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Where.And.vb:158 — Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Where.And.vb:158-165 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Where.vb:172-179 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (8 lines × 2) Source/Source/Yamo.CodeGenerator/Generator/SelectSqlExpressionCodeGenerator.vb:44 — Source/Source/Yamo.CodeGenerator/Generator/SelectSqlExpressionCodeGenerator.vb:44-51 | Source/Source/Yamo.CodeGenerator/Generator/WithHintsSelectSqlExpressionCodeGenerator.vb:42-49 — before extracting anything, compare `Source/Source/Yamo.CodeGenerator/Generator/SelectSqlExpressionCodeGenerator.vb` and `Source/Source/Yamo.CodeGenerator/Generator/WithHintsSelectSqlExpressionCodeGenerator.vb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 83 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D17 · Explicit Debt · CommentedOutCode · ×5
  • CommentedOutCode Source/Samples/Yamo.Playground.CS/Program.cs:23 — 69 consecutive commented-code lines
  • CommentedOutCode Source/Samples/Yamo.Playground.CS/Program.cs:624 — 8 consecutive commented-code lines
  • CommentedOutCode Source/Samples/Yamo.Playground.CS/Program.cs:912 — 3 consecutive commented-code lines
  • CommentedOutCode Source/Samples/Yamo.Playground.CS/Program.cs:928 — 4 consecutive commented-code lines
  • CommentedOutCode Source/Samples/Yamo.Playground.CS/Program.cs:938 — 5 consecutive commented-code lines
D4 · Code Duplication · Edited copies of one member (3 members, 10+ corresponding lines) · ×5
  • Edited copies of one member (3 members, 10+ corresponding lines) Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Join.vb:196 — Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Join.vb:196-205 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Join.vb:209-218 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Join.vb:222-231 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 10+ corresponding lines) Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Join.vb:287 — Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Join.vb:287-296 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Join.vb:300-309 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Join.vb:313-322 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 10+ corresponding lines) Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Join.vb:378 — Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Join.vb:378-387 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Join.vb:391-400 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Join.vb:404-413 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 10+ corresponding lines) Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Join.vb:469 — Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Join.vb:469-478 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Join.vb:482-491 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Join.vb:495-504 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 10+ corresponding lines) Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Select.vb:67 — Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Select.vb:67-76 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Select.vb:80-89 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Select.vb:93-102 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (6 members, 9+ corresponding lines) · ×5
  • Edited copies of one member (6 members, 9+ corresponding lines) Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.OrderBy.vb:96 — Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.OrderBy.vb:96-104 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.OrderBy.vb:108-117 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.OrderBy.vb:121-130 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.OrderBy.vb:134-143 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.OrderBy.vb:212-221 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.ThenBy.vb:212-221 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
  • Edited copies of one member (6 members, 9+ corresponding lines) Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Set.vb:98 — Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Set.vb:98-106 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Set.vb:110-118 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Set.vb:122-130 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Set.vb:134-142 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Set.vb:146-154 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Set.vb:158-166 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
  • Edited copies of one member (6 members, 9+ corresponding lines) Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Set.vb:170 — Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Set.vb:170-178 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Set.vb:182-190 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Set.vb:194-202 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Set.vb:206-214 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Set.vb:218-226 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Set.vb:230-238 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
  • Edited copies of one member (6 members, 9+ corresponding lines) Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Set.vb:242 — Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Set.vb:242-250 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Set.vb:254-262 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Set.vb:266-274 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Set.vb:278-286 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Set.vb:290-298 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Set.vb:302-310 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
  • Edited copies of one member (6 members, 9+ corresponding lines) Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Set.vb:314 — Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Set.vb:314-322 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Set.vb:326-334 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Set.vb:338-346 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Set.vb:350-358 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Set.vb:362-370 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Set.vb:374-382 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication · Duplicated block (5 lines × 6) · ×5
  • Duplicated block (5 lines × 6) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb:203 — Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb:203-207 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3.vb:219-223 | Source/Source/Yamo/Expressions/SelectSqlExpression.vb:849-853 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2.vb:1039-1043 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3.vb:1112-1116 | Source/Source/Yamo/Expressions/WithHintsSelectSqlExpression.vb:769-773 — before extracting anything, compare `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb` and `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3.vb` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 128 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb:202` calls `GetType`, `FilteredSelectSqlExpression` and `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3.vb:218` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (5 lines × 6) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb:227 — Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb:227-231 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3.vb:242-246 | Source/Source/Yamo/Expressions/SelectSqlExpression.vb:874-878 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2.vb:1063-1067 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3.vb:1135-1139 | Source/Source/Yamo/Expressions/WithHintsSelectSqlExpression.vb:794-798 — before extracting anything, compare `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb` and `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3.vb` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 128 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb:226` calls `GetType`, `GroupedSelectSqlExpression` and `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3.vb:241` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (5 lines × 6) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb:251 — Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb:251-255 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3.vb:265-269 | Source/Source/Yamo/Expressions/SelectSqlExpression.vb:899-903 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2.vb:1087-1091 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3.vb:1158-1162 | Source/Source/Yamo/Expressions/WithHintsSelectSqlExpression.vb:819-823 — before extracting anything, compare `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb` and `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3.vb` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 128 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb:250` calls `GetType`, `HavingSelectSqlExpression` and `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3.vb:264` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (5 lines × 6) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb:275 — Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb:275-279 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3.vb:288-292 | Source/Source/Yamo/Expressions/SelectSqlExpression.vb:924-928 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2.vb:1111-1115 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3.vb:1181-1185 | Source/Source/Yamo/Expressions/WithHintsSelectSqlExpression.vb:844-848 — before extracting anything, compare `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb` and `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3.vb` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 128 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb:274` calls `GetType`, `OrderedSelectSqlExpression` and `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3.vb:287` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (5 lines × 6) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb:299 — Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb:299-303 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3.vb:311-315 | Source/Source/Yamo/Expressions/SelectSqlExpression.vb:949-953 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2.vb:1135-1139 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3.vb:1204-1208 | Source/Source/Yamo/Expressions/WithHintsSelectSqlExpression.vb:869-873 — before extracting anything, compare `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb` and `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3.vb` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 128 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb:298` calls `GetType`, `LimitedSelectSqlExpression` and `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3.vb:310` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D6 · Cohesion (LCOM4) · Low cohesion · ×5
  • Low cohesion: MemberCallerCache (LCOM4 6) Source/Source/Yamo/Internal/MemberCallerCache.vb:11 — MemberCallerCache's methods fall into 6 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 6 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: EntitySqlStringProviderCache (LCOM4 5) Source/Source/Yamo/Internal/EntitySqlStringProviderCache.vb:13 — EntitySqlStringProviderCache's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: DeleteSqlExpression (LCOM4 4) Source/Source/Yamo/Expressions/DeleteSqlExpression.vb:13 — DeleteSqlExpression's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: WithHintsDeleteSqlExpression (LCOM4 4) Source/Source/Yamo/Expressions/WithHintsDeleteSqlExpression.vb:13 — WithHintsDeleteSqlExpression's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: EntityReaderCache (LCOM4 4) Source/Source/Yamo/Internal/EntityReaderCache.vb:13 — EntityReaderCache's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
D4 · Code Duplication · Edited copy of a member (12 corresponding lines) · ×4
  • Edited copy of a member (12 corresponding lines) Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.If.vb:16 — Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.If.vb:16-29 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.If.vb:33-44 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) Source/Source/Yamo/Internal/Query/QueryExecutor.vb:345 — Source/Source/Yamo/Internal/Query/QueryExecutor.vb:345-356 | Source/Source/Yamo/Internal/Query/QueryExecutor.vb:545-560 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) Source/Source/Yamo/Internal/EntityReaderCache.vb:132 — Source/Source/Yamo/Internal/EntityReaderCache.vb:132-143 | Source/Source/Yamo/Internal/ValueTypeReaderCache.vb:79-90 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) Source/Source/Yamo/Internal/EntitySqlStringProviderCache.vb:142 — Source/Source/Yamo/Internal/EntitySqlStringProviderCache.vb:142-153 | Source/Source/Yamo/Internal/SqlResultReaderCache.vb:102-113 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (15 corresponding lines) · ×4
  • Edited copy of a member (15 corresponding lines) Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11.vb:1019 — Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11.vb:1019-1033 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11.vb:1011-1025 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10.vb:951 — Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10.vb:951-965 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10.vb:943-957 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9.vb:883 — Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9.vb:883-897 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9.vb:875-889 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8.vb:815 — Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8.vb:815-829 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8.vb:807-821 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 10+ corresponding lines) · ×4
  • Edited copies of one member (4 members, 10+ corresponding lines) Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.ThenBy.vb:121 — Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.ThenBy.vb:121-130 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.ThenBy.vb:134-143 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Where.And.vb:132-141 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Where.And.vb:145-154 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 10+ corresponding lines) Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Join.vb:171 — Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Join.vb:171-180 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Join.vb:262-271 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Join.vb:353-362 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Join.vb:444-453 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 10+ corresponding lines) Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.OrderBy.vb:83 — Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.OrderBy.vb:83-92 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.OrderBy.vb:174-183 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.ThenBy.vb:83-92 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.ThenBy.vb:174-183 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 10+ corresponding lines) Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.GroupBy.vb:25 — Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.GroupBy.vb:25-35 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.GroupBy.vb:39-48 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.GroupBy.vb:52-61 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.GroupBy.vb:65-75 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (10 corresponding lines) · ×4
  • Edited copy of a member (10 corresponding lines) Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Exclude.vb:32 — Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Exclude.vb:32-42 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Exclude.vb:46-55 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.OrderBy.vb:199 — Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.OrderBy.vb:199-208 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.ThenBy.vb:199-208 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) Source/Source/Yamo/Expressions/Builders/SelectSqlExpressionBuilder.vb:862 — Source/Source/Yamo/Expressions/Builders/SelectSqlExpressionBuilder.vb:862-871 | Source/Source/Yamo/Expressions/Builders/SelectSqlExpressionBuilder.vb:888-911 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) Source/Samples/Yamo.Playground.CS/Program.cs:743 — Source/Samples/Yamo.Playground.CS/Program.cs:743-752 | Source/Samples/Yamo.Playground.CS/Program.cs:755-768 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (7 corresponding lines) · ×4
  • Edited copy of a member (7 corresponding lines) Source/Source/Yamo/PredicateBuilder.vb:24 — Source/Source/Yamo/PredicateBuilder.vb:24-30 | Source/Source/Yamo/PredicateBuilder.vb:110-116 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) Source/Source/Yamo/Infrastructure/EntityAutoFieldsGetterFactory.vb:40 — Source/Source/Yamo/Infrastructure/EntityAutoFieldsGetterFactory.vb:40-46 | Source/Source/Yamo/Infrastructure/EntityAutoFieldsSetterFactory.vb:47-53 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) Source/Samples/Yamo.Playground.CS/MyContext.cs:56 — Source/Samples/Yamo.Playground.CS/MyContext.cs:56-63 | Source/Samples/Yamo.Playground.CS/MyContext.cs:142-148 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) Source/Samples/Yamo.Playground.CS/MyContext.cs:105 — Source/Samples/Yamo.Playground.CS/MyContext.cs:105-112 | Source/Samples/Yamo.Playground.CS/MyContext.cs:133-139 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (16 lines × 2) · ×4
  • Duplicated block (16 lines × 2) Source/Source/Yamo/PredicateBuilder.vb:41 — Source/Source/Yamo/PredicateBuilder.vb:41-56 | Source/Source/Yamo/PredicateBuilder.vb:127-142 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (16 lines × 2) Source/Source/Yamo.CodeGenerator/Generator/CustomDistinctSelectSqlExpressionCodeGenerator.vb:16 — Source/Source/Yamo.CodeGenerator/Generator/CustomDistinctSelectSqlExpressionCodeGenerator.vb:16-31 | Source/Source/Yamo.CodeGenerator/Generator/DistinctSelectSqlExpressionCodeGenerator.vb:16-31 — before extracting anything, compare `Source/Source/Yamo.CodeGenerator/Generator/CustomDistinctSelectSqlExpressionCodeGenerator.vb` and `Source/Source/Yamo.CodeGenerator/Generator/DistinctSelectSqlExpressionCodeGenerator.vb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 42 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (16 lines × 2) Source/Source/Yamo.CodeGenerator/Generator/CustomSelectSqlExpressionCodeGenerator.vb:19 — Source/Source/Yamo.CodeGenerator/Generator/CustomSelectSqlExpressionCodeGenerator.vb:19-34 | Source/Source/Yamo.CodeGenerator/Generator/SelectedSelectSqlExpressionCodeGenerator.vb:20-35 — before extracting anything, compare `Source/Source/Yamo.CodeGenerator/Generator/CustomSelectSqlExpressionCodeGenerator.vb` and `Source/Source/Yamo.CodeGenerator/Generator/SelectedSelectSqlExpressionCodeGenerator.vb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 42 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (16 lines × 2) Source/Source/Yamo.CodeGenerator/Generator/CustomSetSelectSqlExpressionCodeGenerator.vb:18 — Source/Source/Yamo.CodeGenerator/Generator/CustomSetSelectSqlExpressionCodeGenerator.vb:18-33 | Source/Source/Yamo.CodeGenerator/Generator/SetSelectSqlExpressionCodeGenerator.vb:18-33 — before extracting anything, compare `Source/Source/Yamo.CodeGenerator/Generator/CustomSetSelectSqlExpressionCodeGenerator.vb` and `Source/Source/Yamo.CodeGenerator/Generator/SetSelectSqlExpressionCodeGenerator.vb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 42 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (14 lines × 2) · ×4
  • Duplicated block (14 lines × 2) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3.vb:120 — Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3.vb:120-133 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2.vb:936-949 — before extracting anything, compare `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3.vb` and `Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2.vb` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 142 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (14 lines × 2) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4.vb:131 — Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4.vb:131-144 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3.vb:1014-1027 — before extracting anything, compare `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4.vb` and `Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3.vb` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 117 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (14 lines × 2) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5.vb:142 — Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5.vb:142-155 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4.vb:1114-1127 — before extracting anything, compare `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5.vb` and `Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4.vb` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 117 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (14 lines × 2) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6.vb:153 — Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6.vb:153-166 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5.vb:1232-1245 — before extracting anything, compare `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6.vb` and `Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5.vb` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 112 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (9 lines × 7) · ×4
  • Duplicated block (9 lines × 7) Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:116 — Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:116-124 | Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb:117-125 | Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb:118-126 | Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb:119-127 | Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb:120-128 | Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24.vb:121-129 | Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24T25.vb:122-130 — before extracting anything, compare `Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb` and `Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb` as WHOLE FILES: 87% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (9 lines × 7) Source/Source/Yamo/Expressions/OrderedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:1173 — Source/Source/Yamo/Expressions/OrderedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:1173-1181 | Source/Source/Yamo/Expressions/OrderedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb:1223-1231 | Source/Source/Yamo/Expressions/OrderedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb:1273-1281 | Source/Source/Yamo/Expressions/OrderedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb:1323-1331 | Source/Source/Yamo/Expressions/OrderedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb:1373-1381 | Source/Source/Yamo/Expressions/OrderedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24.vb:1423-1431 | Source/Source/Yamo/Expressions/OrderedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24T25.vb:1473-1481 — before extracting anything, compare `Source/Source/Yamo/Expressions/OrderedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb` and `Source/Source/Yamo/Expressions/OrderedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb` as WHOLE FILES: 90% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (9 lines × 7) Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:5177 — Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:5177-5185 | Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb:5674-5682 | Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb:6195-6203 | Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb:6740-6748 | Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb:7309-7317 | Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24.vb:7902-7910 | Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24T25.vb:8519-8527 — before extracting anything, compare `Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb` and `Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb` as WHOLE FILES: 91% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (9 lines × 7) Source/Source/Yamo.CodeGenerator/Generator/FilteredSelectSqlExpressionCodeGenerator.vb:63 — Source/Source/Yamo.CodeGenerator/Generator/FilteredSelectSqlExpressionCodeGenerator.vb:63-71 | Source/Source/Yamo.CodeGenerator/Generator/GroupedSelectSqlExpressionCodeGenerator.vb:58-66 | Source/Source/Yamo.CodeGenerator/Generator/HavingSelectSqlExpressionCodeGenerator.vb:58-66 | Source/Source/Yamo.CodeGenerator/Generator/JoinSelectSqlExpressionCodeGenerator.vb:50-58 | Source/Source/Yamo.CodeGenerator/Generator/JoinWithHintsSelectSqlExpressionCodeGenerator.vb:45-53 | Source/Source/Yamo.CodeGenerator/Generator/JoinedSelectSqlExpressionCodeGenerator.vb:55-63 | Source/Source/Yamo.CodeGenerator/Generator/OrderedSelectSqlExpressionCodeGenerator.vb:54-62 — before extracting anything, compare `Source/Source/Yamo.CodeGenerator/Generator/FilteredSelectSqlExpressionCodeGenerator.vb` and `Source/Source/Yamo.CodeGenerator/Generator/GroupedSelectSqlExpressionCodeGenerator.vb` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 61 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Near-duplicate member pair (34 shared lines) · ×3
  • Near-duplicate member pair (34 shared lines) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12.vb:219 — Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12.vb:219-353 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11.vb:1479-1621 — These two members are variants of one another: 34 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
  • Near-duplicate member pair (34 shared lines) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13.vb:230 — Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13.vb:230-355 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12.vb:1557-1690 — These two members are variants of one another: 34 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
  • Near-duplicate member pair (34 shared lines) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14.vb:241 — Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14.vb:241-357 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13.vb:1635-1759 — These two members are variants of one another: 34 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication · Members sharing a duplicated core (7 members, 50+ identical tokens) · ×3
  • Members sharing a duplicated core (7 members, 50+ identical tokens) Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:116 — Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:116-128 | Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb:117-129 | Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb:118-130 | Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb:119-131 | Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb:120-132 | Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24.vb:121-133 | Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24T25.vb:122-134 — These 7 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 7 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 7 times.
  • Members sharing a duplicated core (7 members, 50+ identical tokens) Source/Source/Yamo/Expressions/OrderedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:1173 — Source/Source/Yamo/Expressions/OrderedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:1173-1186 | Source/Source/Yamo/Expressions/OrderedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb:1223-1236 | Source/Source/Yamo/Expressions/OrderedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb:1273-1286 | Source/Source/Yamo/Expressions/OrderedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb:1323-1336 | Source/Source/Yamo/Expressions/OrderedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb:1373-1386 | Source/Source/Yamo/Expressions/OrderedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24.vb:1423-1436 | Source/Source/Yamo/Expressions/OrderedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24T25.vb:1473-1486 — These 7 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 7 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 7 times.
  • Members sharing a duplicated core (7 members, 50+ identical tokens) Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:5177 — Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:5177-5191 | Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb:5674-5688 | Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb:6195-6209 | Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb:6740-6754 | Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb:7309-7323 | Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24.vb:7902-7916 | Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24T25.vb:8519-8533 — These 7 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 7 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 7 times.
D4 · Code Duplication · Edited copies of one member (3 members, 9+ corresponding lines) · ×3
  • Edited copies of one member (3 members, 9+ corresponding lines) Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.On.vb:27 — Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.On.vb:27-37 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.On.vb:41-49 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.On.vb:65-75 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 9+ corresponding lines) Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.OrderBy.vb:187 — Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.OrderBy.vb:187-195 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.ThenBy.vb:96-104 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.ThenBy.vb:187-195 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 9+ corresponding lines) Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Limit.vb:16 — Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Limit.vb:16-24 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Limit.vb:28-36 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Limit.vb:40-49 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 9+ corresponding lines) · ×3
  • Edited copies of one member (4 members, 9+ corresponding lines) Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Having.And.vb:87 — Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Having.And.vb:87-95 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Having.And.vb:99-107 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Having.vb:90-98 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Having.vb:102-110 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 9+ corresponding lines) Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Where.And.vb:95 — Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Where.And.vb:95-103 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Where.And.vb:107-115 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Where.vb:98-106 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Where.vb:110-118 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 9+ corresponding lines) Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Include.vb:33 — Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Include.vb:33-42 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Include.vb:61-69 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Include.vb:86-95 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Include.vb:99-108 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Duplicated block (17 lines × 2) · ×3
  • Duplicated block (17 lines × 2) Source/Source/Yamo/PredicateBuilder.vb:75 — Source/Source/Yamo/PredicateBuilder.vb:75-91 | Source/Source/Yamo/PredicateBuilder.vb:160-176 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (17 lines × 2) Source/Source/Yamo/Internal/Query/QueryExecutor.vb:639 — Source/Source/Yamo/Internal/Query/QueryExecutor.vb:639-655 | Source/Source/Yamo/Internal/Query/QueryExecutor.vb:719-735 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (17 lines × 2) Source/Samples/Yamo.Playground.CS/Program.cs:461 — Source/Samples/Yamo.Playground.CS/Program.cs:461-477 | Source/Samples/Yamo.Playground.CS/Program.cs:499-515 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (11 lines × 2) · ×3
  • Duplicated block (11 lines × 2) Source/Source/Yamo/Infrastructure/SqlResultReaderFactory.vb:272 — Source/Source/Yamo/Infrastructure/SqlResultReaderFactory.vb:272-282 | Source/Source/Yamo/Infrastructure/SqlResultReaderFactory.vb:301-311 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (11 lines × 2) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24T25.vb:362 — Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24T25.vb:362-372 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24.vb:2493-2503 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (11 lines × 2) Source/Source/Yamo/Expressions/DeleteSqlExpression.vb:88 — Source/Source/Yamo/Expressions/DeleteSqlExpression.vb:88-98 | Source/Source/Yamo/Expressions/WithHintsDeleteSqlExpression.vb:79-89 — before extracting anything, compare `Source/Source/Yamo/Expressions/DeleteSqlExpression.vb` and `Source/Source/Yamo/Expressions/WithHintsDeleteSqlExpression.vb` as WHOLE FILES: 85% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (4–12 lines × 3) · ×3
  • Duplicated block (4–12 lines × 3) Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:1790 — Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:1790-1793 | Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:1563-1574 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:1555-1566 — before extracting anything, compare `Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb` and `Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb` as WHOLE FILES: 84% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:1574` calls `GetType`, `OrderedSelectSqlExpression`, `LimitedSelectSqlExpression` and `Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:1793` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (4–12 lines × 3) Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb:1868 — Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb:1868-1871 | Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb:1631-1642 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb:1623-1634 — before extracting anything, compare `Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb` and `Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb` as WHOLE FILES: 84% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb:1642` calls `GetType`, `OrderedSelectSqlExpression`, `LimitedSelectSqlExpression` and `Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb:1871` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (4–12 lines × 3) Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb:1946 — Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb:1946-1949 | Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb:1699-1710 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb:1691-1702 — before extracting anything, compare `Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb` and `Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb` as WHOLE FILES: 84% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb:1710` calls `GetType`, `OrderedSelectSqlExpression`, `LimitedSelectSqlExpression` and `Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb:1949` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (5 lines × 4) · ×3
  • Duplicated block (5 lines × 4) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb:133 — Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb:133-137 | Source/Source/Yamo/Expressions/SelectSqlExpression.vb:776-780 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2.vb:969-973 | Source/Source/Yamo/Expressions/WithHintsSelectSqlExpression.vb:696-700 — before extracting anything, compare `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb` and `Source/Source/Yamo/Expressions/SelectSqlExpression.vb` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 158 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Source/Source/Yamo/Expressions/SelectSqlExpression.vb:774` calls `GetType`, `WithHintsSelectSqlExpression`, `JoinSelectSqlExpression` and `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb:132` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (5 lines × 4) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb:156 — Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb:156-160 | Source/Source/Yamo/Expressions/SelectSqlExpression.vb:800-804 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2.vb:992-996 | Source/Source/Yamo/Expressions/WithHintsSelectSqlExpression.vb:720-724 — before extracting anything, compare `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb` and `Source/Source/Yamo/Expressions/SelectSqlExpression.vb` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 158 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Source/Source/Yamo/Expressions/SelectSqlExpression.vb:799` calls `GetType`, `JoinWithHintsSelectSqlExpression` and `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb:155` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (5 lines × 4) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb:179 — Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb:179-183 | Source/Source/Yamo/Expressions/SelectSqlExpression.vb:824-828 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2.vb:1015-1019 | Source/Source/Yamo/Expressions/WithHintsSelectSqlExpression.vb:744-748 — before extracting anything, compare `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb` and `Source/Source/Yamo/Expressions/SelectSqlExpression.vb` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 158 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Source/Source/Yamo/Expressions/SelectSqlExpression.vb:823` calls `GetType`, `JoinedSelectSqlExpression` and `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb:178` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (4–5 lines × 20) · ×3
  • Duplicated block (4–5 lines × 20) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb:253 — Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb:253-257 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3.vb:267-271 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4.vb:271-275 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5.vb:275-279 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6.vb:279-283 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7.vb:286-289 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8.vb:290-293 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9.vb:294-297 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10.vb:299-302 | Source/Source/Yamo/Expressions/SelectSqlExpression.vb:901-905 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2.vb:1089-1093 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3.vb:1160-1164 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4.vb:1253-1257 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5.vb:1364-1368 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6.vb:1475-1479 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7.vb:1309-1312 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8.vb:1359-1362 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9.vb:1430-1433 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10.vb:1502-1505 | Source/Source/Yamo/Expressions/WithHintsSelectSqlExpression.vb:821-825 — before extracting anything, compare `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb` and `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3.vb` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 128 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb:250` calls `GetType`, `HavingSelectSqlExpression` and `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3.vb:264` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (4–5 lines × 20) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb:277 — Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb:277-281 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3.vb:290-294 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4.vb:293-297 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5.vb:296-300 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6.vb:299-303 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7.vb:305-308 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8.vb:308-311 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9.vb:311-314 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10.vb:315-318 | Source/Source/Yamo/Expressions/SelectSqlExpression.vb:926-930 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2.vb:1113-1117 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3.vb:1183-1187 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4.vb:1275-1279 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5.vb:1385-1389 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6.vb:1495-1499 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7.vb:1328-1331 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8.vb:1377-1380 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9.vb:1447-1450 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10.vb:1518-1521 | Source/Source/Yamo/Expressions/WithHintsSelectSqlExpression.vb:846-850 — before extracting anything, compare `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb` and `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3.vb` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 128 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb:274` calls `GetType`, `OrderedSelectSqlExpression` and `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3.vb:287` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (4–5 lines × 20) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb:301 — Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb:301-305 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3.vb:313-317 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4.vb:315-319 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5.vb:317-321 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6.vb:319-323 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7.vb:324-327 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8.vb:326-329 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9.vb:328-331 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10.vb:331-334 | Source/Source/Yamo/Expressions/SelectSqlExpression.vb:951-955 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2.vb:1137-1141 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3.vb:1206-1210 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4.vb:1297-1301 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5.vb:1406-1410 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6.vb:1515-1519 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7.vb:1347-1350 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8.vb:1395-1398 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9.vb:1464-1467 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10.vb:1534-1537 | Source/Source/Yamo/Expressions/WithHintsSelectSqlExpression.vb:871-875 — before extracting anything, compare `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb` and `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3.vb` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 128 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb:298` calls `GetType`, `LimitedSelectSqlExpression` and `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3.vb:310` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D3 · God Classes · ClassTooLong · ×2
  • ClassTooLong: Join Source/Source/Yamo/JoinOfT1T2.vb — ClassTooLong — 768 significant lines (blank, comment-only and punctuation-only lines excluded), 24 methods. The bar is 400 significant lines; this is 368 over it, 1.92× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: QueryExecutor Source/Source/Yamo/Internal/Query/QueryExecutor.vb — ClassTooLong — 541 significant lines (blank, comment-only and punctuation-only lines excluded), 25 methods. The bar is 400 significant lines; this is 141 over it, 1.35× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D4 · Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) · ×2
  • Members sharing a duplicated core (4 members, 50+ identical tokens) Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18.vb:1699 — Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18.vb:1699-1715 | Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18.vb:1495-1509 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18.vb:1487-1501 | Source/Source/Yamo/Expressions/OrderedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18.vb:1123-1136 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) Source/Source/Yamo/Infrastructure/SqlResultReaderFactory.vb:183 — Source/Source/Yamo/Infrastructure/SqlResultReaderFactory.vb:183-213 | Source/Source/Yamo/Infrastructure/SqlResultReaderFactory.vb:222-253 | Source/Source/Yamo/Infrastructure/SqlResultReaderFactory.vb:262-282 | Source/Source/Yamo/Infrastructure/SqlResultReaderFactory.vb:291-311 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication · Edited copy of a member (24 corresponding lines) · ×2
  • Edited copy of a member (24 corresponding lines) Source/Source/Yamo/PredicateBuilder.vb:75 — Source/Source/Yamo/PredicateBuilder.vb:75-98 | Source/Source/Yamo/PredicateBuilder.vb:160-183 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (24 corresponding lines) Source/Source/Yamo/Expressions/Builders/DeleteSqlExpressionBuilder.vb:139 — Source/Source/Yamo/Expressions/Builders/DeleteSqlExpressionBuilder.vb:139-162 | Source/Source/Yamo/Expressions/Builders/UpdateSqlExpressionBuilder.vb:168-211 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (8 members, 10+ corresponding lines) · ×2
  • Edited copies of one member (8 members, 10+ corresponding lines) Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.OrderBy.vb:56 — Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.OrderBy.vb:56-66 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.OrderBy.vb:70-79 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.OrderBy.vb:147-157 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.OrderBy.vb:161-170 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.ThenBy.vb:56-66 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.ThenBy.vb:70-79 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.ThenBy.vb:147-157 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.ThenBy.vb:161-170 — These 8 members are one piece of code written 8 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 8 times and the copies will drift further apart.
  • Edited copies of one member (8 members, 10+ corresponding lines) Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Join.vb:144 — Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Join.vb:144-154 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Join.vb:158-167 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Join.vb:235-245 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Join.vb:249-258 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Join.vb:326-336 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Join.vb:340-349 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Join.vb:417-427 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Join.vb:431-440 — These 8 members are one piece of code written 8 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 8 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (11 corresponding lines) · ×2
  • Edited copy of a member (11 corresponding lines) Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.As.vb:20 — Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.As.vb:20-30 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.As.vb:34-44 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) Source/Samples/Yamo.Playground.CS/Program.cs:971 — Source/Samples/Yamo.Playground.CS/Program.cs:971-981 | Source/Samples/Yamo.Playground.CS/Program.cs:984-994 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (8 members, 9+ corresponding lines) · ×2
  • Edited copies of one member (8 members, 9+ corresponding lines) Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Having.And.vb:37 — Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Having.And.vb:37-46 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Having.And.vb:50-59 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Having.And.vb:63-71 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Having.And.vb:75-83 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Having.vb:40-49 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Having.vb:53-62 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Having.vb:66-74 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Having.vb:78-86 — These 8 members are one piece of code written 8 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 8 times and the copies will drift further apart.
  • Edited copies of one member (8 members, 9+ corresponding lines) Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Where.And.vb:45 — Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Where.And.vb:45-54 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Where.And.vb:58-67 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Where.And.vb:71-79 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Where.And.vb:83-91 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Where.vb:48-57 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Where.vb:61-70 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Where.vb:74-82 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Where.vb:86-94 — These 8 members are one piece of code written 8 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 8 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (17 corresponding lines) · ×2
  • Edited copy of a member (17 corresponding lines) Source/Source/Yamo/Expressions/Builders/DeleteSqlExpressionBuilder.vb:211 — Source/Source/Yamo/Expressions/Builders/DeleteSqlExpressionBuilder.vb:211-227 | Source/Source/Yamo/Expressions/Builders/DeleteSqlExpressionBuilder.vb:237-253 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (17 corresponding lines) Source/Source/Yamo/Internal/EntityReaderCache.vb:155 — Source/Source/Yamo/Internal/EntityReaderCache.vb:155-171 | Source/Source/Yamo/Internal/ValueTypeReaderCache.vb:101-117 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (20 lines × 3) · ×2
  • Duplicated block (20 lines × 3) Source/Source/Yamo.CodeGenerator/Generator/CustomDistinctSelectSqlExpressionCodeGenerator.vb:35 — Source/Source/Yamo.CodeGenerator/Generator/CustomDistinctSelectSqlExpressionCodeGenerator.vb:35-54 | Source/Source/Yamo.CodeGenerator/Generator/CustomSelectSqlExpressionCodeGenerator.vb:41-60 | Source/Source/Yamo.CodeGenerator/Generator/CustomSetSelectSqlExpressionCodeGenerator.vb:37-56 — before extracting anything, compare `Source/Source/Yamo.CodeGenerator/Generator/CustomDistinctSelectSqlExpressionCodeGenerator.vb` and `Source/Source/Yamo.CodeGenerator/Generator/CustomSelectSqlExpressionCodeGenerator.vb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 46 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Source/Source/Yamo.CodeGenerator/Generator/CustomSelectSqlExpressionCodeGenerator.vb:38` calls `AppendLine`, `GenerateCustomDistinct` and `Source/Source/Yamo.CodeGenerator/Generator/CustomDistinctSelectSqlExpressionCodeGenerator.vb:34` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (20 lines × 3) Source/Source/Yamo.CodeGenerator/Generator/DistinctSelectSqlExpressionCodeGenerator.vb:35 — Source/Source/Yamo.CodeGenerator/Generator/DistinctSelectSqlExpressionCodeGenerator.vb:35-54 | Source/Source/Yamo.CodeGenerator/Generator/SelectedSelectSqlExpressionCodeGenerator.vb:48-67 | Source/Source/Yamo.CodeGenerator/Generator/SetSelectSqlExpressionCodeGenerator.vb:37-56 — before extracting anything, compare `Source/Source/Yamo.CodeGenerator/Generator/DistinctSelectSqlExpressionCodeGenerator.vb` and `Source/Source/Yamo.CodeGenerator/Generator/SelectedSelectSqlExpressionCodeGenerator.vb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 46 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (9 lines × 14) · ×2
  • Duplicated block (9 lines × 14) Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:1563 — Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:1563-1571 | Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb:1631-1639 | Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb:1699-1707 | Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb:1767-1775 | Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb:1835-1843 | Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24.vb:1903-1911 | Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24T25.vb:1971-1979 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:1555-1563 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb:1623-1631 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb:1691-1699 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb:1759-1767 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb:1827-1835 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24.vb:1895-1903 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24T25.vb:1963-1971 — before extracting anything, compare `Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb` and `Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb` as WHOLE FILES: 88% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (9 lines × 14) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:296 — Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:296-304 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb:307-315 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb:318-326 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb:329-337 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb:340-348 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24.vb:351-359 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24T25.vb:362-370 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18.vb:2025-2033 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:2103-2111 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb:2181-2189 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb:2259-2267 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb:2337-2345 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb:2415-2423 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24.vb:2493-2501 — before extracting anything, compare `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb` and `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 111 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:306` calls `GetType`, `SelectSqlExpression` and `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb:317` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (9 lines × 2) · ×2
  • Duplicated block (9 lines × 2) Source/Source/Yamo/Infrastructure/EntitySqlStringProviderFactory.vb:215 — Source/Source/Yamo/Infrastructure/EntitySqlStringProviderFactory.vb:215-223 | Source/Source/Yamo/Infrastructure/EntitySqlStringProviderFactory.vb:298-306 — both copies are in the same file, so extract the 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) Source/Source/Yamo/Expressions/InsertSqlExpression.vb:42 — Source/Source/Yamo/Expressions/InsertSqlExpression.vb:42-50 | Source/Source/Yamo/Expressions/WithHintsInsertSqlExpression.vb:33-41 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (5 lines × 2) · ×2
  • Duplicated block (5 lines × 2) Source/Source/Yamo/PredicateBuilder.vb:24 — Source/Source/Yamo/PredicateBuilder.vb:24-28 | Source/Source/Yamo/PredicateBuilder.vb:110-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.
  • Duplicated block (5 lines × 2) Source/Source/Yamo.SQLite/Infrastructure/SQLiteEntitySqlStringProviderFactory.vb:44 — Source/Source/Yamo.SQLite/Infrastructure/SQLiteEntitySqlStringProviderFactory.vb:44-48 | Source/Source/Yamo/Infrastructure/EntitySqlStringProviderFactory.vb:175-179 — 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.
D4 · Code Duplication · Duplicated block (3–5 lines × 54) · ×2
  • Duplicated block (3–5 lines × 54) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb:205 — Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb:205-209 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3.vb:221-225 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4.vb:224-226 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4.vb:227-231 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5.vb:233-237 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6.vb:239-243 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7.vb:245-247 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7.vb:248-251 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8.vb:252-254 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8.vb:255-258 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9.vb:259-261 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10.vb:266-268 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11.vb:273-275 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12.vb:280-282 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13.vb:287-289 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14.vb:294-296 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15.vb:301-303 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16.vb:308-310 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17.vb:315-317 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18.vb:322-324 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:329-331 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb:336-338 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb:343-345 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb:350-352 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb:357-359 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24.vb:364-366 | Source/Source/Yamo/Expressions/SelectSqlExpression.vb:851-855 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2.vb:1041-1045 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3.vb:1114-1118 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4.vb:1206-1208 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4.vb:1209-1213 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5.vb:1322-1326 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6.vb:1435-1439 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7.vb:1268-1270 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7.vb:1271-1274 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8.vb:1321-1323 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8.vb:1324-1327 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9.vb:1395-1397 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10.vb:1469-1471 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11.vb:1543-1545 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12.vb:1617-1619 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13.vb:1691-1693 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14.vb:1765-1767 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15.vb:1839-1841 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16.vb:1913-1915 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17.vb:1987-1989 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18.vb:2061-2063 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:2135-2137 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb:2209-2211 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb:2283-2285 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb:2357-2359 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb:2431-2433 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24.vb:2505-2507 | Source/Source/Yamo/Expressions/WithHintsSelectSqlExpression.vb:771-775 — before extracting anything, compare `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb` and `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3.vb` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 128 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb:202` calls `GetType`, `FilteredSelectSqlExpression` and `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3.vb:218` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (3–5 lines × 54) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb:229 — Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb:229-233 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3.vb:244-248 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4.vb:246-248 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4.vb:249-253 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5.vb:254-258 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6.vb:259-263 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7.vb:264-266 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7.vb:267-270 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8.vb:270-272 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8.vb:273-276 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9.vb:276-278 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10.vb:282-284 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11.vb:288-290 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12.vb:294-296 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13.vb:300-302 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14.vb:306-308 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15.vb:312-314 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16.vb:318-320 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17.vb:324-326 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18.vb:330-332 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:336-338 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb:342-344 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb:348-350 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb:354-356 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb:360-362 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24.vb:366-368 | Source/Source/Yamo/Expressions/SelectSqlExpression.vb:876-880 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2.vb:1065-1069 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3.vb:1137-1141 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4.vb:1228-1230 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4.vb:1231-1235 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5.vb:1343-1347 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6.vb:1455-1459 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7.vb:1287-1289 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7.vb:1290-1293 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8.vb:1339-1341 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8.vb:1342-1345 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9.vb:1412-1414 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10.vb:1485-1487 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11.vb:1558-1560 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12.vb:1631-1633 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13.vb:1704-1706 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14.vb:1777-1779 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15.vb:1850-1852 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16.vb:1923-1925 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17.vb:1996-1998 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18.vb:2069-2071 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:2142-2144 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb:2215-2217 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb:2288-2290 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb:2361-2363 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb:2434-2436 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24.vb:2507-2509 | Source/Source/Yamo/Expressions/WithHintsSelectSqlExpression.vb:796-800 — before extracting anything, compare `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb` and `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3.vb` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 128 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb:226` calls `GetType`, `GroupedSelectSqlExpression` and `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3.vb:241` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
C1 · Data Protection · No data-protection/encryption · ×1
  • No data-protection/encryption — No data-protection or encryption usage (ASP.NET Data Protection, AES, column encryption, PBKDF2) was found — sensitive data at rest may be unprotected. If TDE/KMS/vault is delegated to infrastructure, ignore.
D1 · Cyclomatic Complexity · SelectSqlExpression.CanCreateResultForCondition (cyclomatic 225) · ×1
  • SelectSqlExpression.CanCreateResultForCondition (cyclomatic 225) Source/Source/Yamo/Expressions/SelectSqlExpression.vb:739 — SelectSqlExpression.CanCreateResultForCondition has cyclomatic complexity 225 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · WithHintsSelectSqlExpression.CanCreateResultForCondition (cyclomatic 224) · ×1
  • WithHintsSelectSqlExpression.CanCreateResultForCondition (cyclomatic 224) Source/Source/Yamo/Expressions/WithHintsSelectSqlExpression.vb:660 — WithHintsSelectSqlExpression.CanCreateResultForCondition has cyclomatic complexity 224 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · JoinedSelectSqlExpression.CanCreateResultForCondition (cyclomatic 216) · ×1
  • JoinedSelectSqlExpression.CanCreateResultForCondition (cyclomatic 216) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb:98 — JoinedSelectSqlExpression.CanCreateResultForCondition has cyclomatic complexity 216 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SelectSqlExpression.CanCreateResultForCondition (cyclomatic 215) · ×1
  • SelectSqlExpression.CanCreateResultForCondition (cyclomatic 215) Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2.vb:935 — SelectSqlExpression.CanCreateResultForCondition has cyclomatic complexity 215 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · JoinedSelectSqlExpression.CanCreateResultForCondition (cyclomatic 207) · ×1
  • JoinedSelectSqlExpression.CanCreateResultForCondition (cyclomatic 207) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3.vb:119 — JoinedSelectSqlExpression.CanCreateResultForCondition has cyclomatic complexity 207 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SelectSqlExpression.CanCreateResultForCondition (cyclomatic 206) · ×1
  • SelectSqlExpression.CanCreateResultForCondition (cyclomatic 206) Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3.vb:1013 — SelectSqlExpression.CanCreateResultForCondition has cyclomatic complexity 206 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · JoinedSelectSqlExpression.CanCreateResultForCondition (cyclomatic 198) · ×1
  • JoinedSelectSqlExpression.CanCreateResultForCondition (cyclomatic 198) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4.vb:130 — JoinedSelectSqlExpression.CanCreateResultForCondition has cyclomatic complexity 198 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SelectSqlExpression.CanCreateResultForCondition (cyclomatic 197) · ×1
  • SelectSqlExpression.CanCreateResultForCondition (cyclomatic 197) Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4.vb:1113 — SelectSqlExpression.CanCreateResultForCondition has cyclomatic complexity 197 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · JoinedSelectSqlExpression.CanCreateResultForCondition (cyclomatic 189) · ×1
  • JoinedSelectSqlExpression.CanCreateResultForCondition (cyclomatic 189) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5.vb:141 — JoinedSelectSqlExpression.CanCreateResultForCondition has cyclomatic complexity 189 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SelectSqlExpression.CanCreateResultForCondition (cyclomatic 188) · ×1
  • SelectSqlExpression.CanCreateResultForCondition (cyclomatic 188) Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5.vb:1231 — SelectSqlExpression.CanCreateResultForCondition has cyclomatic complexity 188 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · JoinedSelectSqlExpression.CanCreateResultForCondition (cyclomatic 180) · ×1
  • JoinedSelectSqlExpression.CanCreateResultForCondition (cyclomatic 180) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6.vb:152 — JoinedSelectSqlExpression.CanCreateResultForCondition has cyclomatic complexity 180 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SelectSqlExpression.CanCreateResultForCondition (cyclomatic 179) · ×1
  • SelectSqlExpression.CanCreateResultForCondition (cyclomatic 179) Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6.vb:1349 — SelectSqlExpression.CanCreateResultForCondition has cyclomatic complexity 179 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · JoinedSelectSqlExpression.CanCreateResultForCondition (cyclomatic 171) · ×1
  • JoinedSelectSqlExpression.CanCreateResultForCondition (cyclomatic 171) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7.vb:163 — JoinedSelectSqlExpression.CanCreateResultForCondition has cyclomatic complexity 171 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SelectSqlExpression.CanCreateResultForCondition (cyclomatic 170) · ×1
  • SelectSqlExpression.CanCreateResultForCondition (cyclomatic 170) Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7.vb:1187 — SelectSqlExpression.CanCreateResultForCondition has cyclomatic complexity 170 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · JoinedSelectSqlExpression.CanCreateResultForCondition (cyclomatic 162) · ×1
  • JoinedSelectSqlExpression.CanCreateResultForCondition (cyclomatic 162) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8.vb:174 — JoinedSelectSqlExpression.CanCreateResultForCondition has cyclomatic complexity 162 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SelectSqlExpression.CanCreateResultForCondition (cyclomatic 161) · ×1
  • SelectSqlExpression.CanCreateResultForCondition (cyclomatic 161) Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8.vb:1244 — SelectSqlExpression.CanCreateResultForCondition has cyclomatic complexity 161 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · JoinedSelectSqlExpression.CanCreateResultForCondition (cyclomatic 153) · ×1
  • JoinedSelectSqlExpression.CanCreateResultForCondition (cyclomatic 153) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9.vb:185 — JoinedSelectSqlExpression.CanCreateResultForCondition has cyclomatic complexity 153 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SelectSqlExpression.CanCreateResultForCondition (cyclomatic 152) · ×1
  • SelectSqlExpression.CanCreateResultForCondition (cyclomatic 152) Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9.vb:1322 — SelectSqlExpression.CanCreateResultForCondition has cyclomatic complexity 152 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · JoinedSelectSqlExpression.CanCreateResultForCondition (cyclomatic 144) · ×1
  • JoinedSelectSqlExpression.CanCreateResultForCondition (cyclomatic 144) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10.vb:196 — JoinedSelectSqlExpression.CanCreateResultForCondition has cyclomatic complexity 144 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SelectSqlExpression.CanCreateResultForCondition (cyclomatic 143) · ×1
  • SelectSqlExpression.CanCreateResultForCondition (cyclomatic 143) Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10.vb:1400 — SelectSqlExpression.CanCreateResultForCondition has cyclomatic complexity 143 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · JoinedSelectSqlExpression.CanCreateResultForCondition (cyclomatic 135) · ×1
  • JoinedSelectSqlExpression.CanCreateResultForCondition (cyclomatic 135) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11.vb:207 — JoinedSelectSqlExpression.CanCreateResultForCondition has cyclomatic complexity 135 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SelectSqlExpression.CanCreateResultForCondition (cyclomatic 134) · ×1
  • SelectSqlExpression.CanCreateResultForCondition (cyclomatic 134) Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11.vb:1478 — SelectSqlExpression.CanCreateResultForCondition has cyclomatic complexity 134 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · JoinedSelectSqlExpression.CanCreateResultForCondition (cyclomatic 126) · ×1
  • JoinedSelectSqlExpression.CanCreateResultForCondition (cyclomatic 126) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12.vb:218 — JoinedSelectSqlExpression.CanCreateResultForCondition has cyclomatic complexity 126 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SelectSqlExpression.CanCreateResultForCondition (cyclomatic 125) · ×1
  • SelectSqlExpression.CanCreateResultForCondition (cyclomatic 125) Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12.vb:1556 — SelectSqlExpression.CanCreateResultForCondition has cyclomatic complexity 125 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · JoinedSelectSqlExpression.CanCreateResultForCondition (cyclomatic 117) · ×1
  • JoinedSelectSqlExpression.CanCreateResultForCondition (cyclomatic 117) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13.vb:229 — JoinedSelectSqlExpression.CanCreateResultForCondition has cyclomatic complexity 117 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SelectSqlExpression.CanCreateResultForCondition (cyclomatic 116) · ×1
  • SelectSqlExpression.CanCreateResultForCondition (cyclomatic 116) Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13.vb:1634 — SelectSqlExpression.CanCreateResultForCondition has cyclomatic complexity 116 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · JoinedSelectSqlExpression.CanCreateResultForCondition (cyclomatic 108) · ×1
  • JoinedSelectSqlExpression.CanCreateResultForCondition (cyclomatic 108) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14.vb:240 — JoinedSelectSqlExpression.CanCreateResultForCondition has cyclomatic complexity 108 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SelectSqlExpression.CanCreateResultForCondition (cyclomatic 107) · ×1
  • SelectSqlExpression.CanCreateResultForCondition (cyclomatic 107) Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14.vb:1712 — SelectSqlExpression.CanCreateResultForCondition has cyclomatic complexity 107 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · JoinedSelectSqlExpression.CanCreateResultForCondition (cyclomatic 99) · ×1
  • JoinedSelectSqlExpression.CanCreateResultForCondition (cyclomatic 99) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15.vb:251 — JoinedSelectSqlExpression.CanCreateResultForCondition has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SelectSqlExpression.CanCreateResultForCondition (cyclomatic 98) · ×1
  • SelectSqlExpression.CanCreateResultForCondition (cyclomatic 98) Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15.vb:1790 — SelectSqlExpression.CanCreateResultForCondition has cyclomatic complexity 98 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · JoinedSelectSqlExpression.CanCreateResultForCondition (cyclomatic 90) · ×1
  • JoinedSelectSqlExpression.CanCreateResultForCondition (cyclomatic 90) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16.vb:262 — JoinedSelectSqlExpression.CanCreateResultForCondition has cyclomatic complexity 90 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SelectSqlExpression.CanCreateResultForCondition (cyclomatic 89) · ×1
  • SelectSqlExpression.CanCreateResultForCondition (cyclomatic 89) Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16.vb:1868 — SelectSqlExpression.CanCreateResultForCondition has cyclomatic complexity 89 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · JoinedSelectSqlExpression.CanCreateResultForCondition (cyclomatic 81) · ×1
  • JoinedSelectSqlExpression.CanCreateResultForCondition (cyclomatic 81) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17.vb:273 — JoinedSelectSqlExpression.CanCreateResultForCondition has cyclomatic complexity 81 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SelectSqlExpression.CanCreateResultForCondition (cyclomatic 80) · ×1
  • SelectSqlExpression.CanCreateResultForCondition (cyclomatic 80) Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17.vb:1946 — SelectSqlExpression.CanCreateResultForCondition has cyclomatic complexity 80 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · JoinedSelectSqlExpression.CanCreateResultForCondition (cyclomatic 72) · ×1
  • JoinedSelectSqlExpression.CanCreateResultForCondition (cyclomatic 72) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18.vb:284 — JoinedSelectSqlExpression.CanCreateResultForCondition has cyclomatic complexity 72 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SelectSqlExpression.CanCreateResultForCondition (cyclomatic 71) · ×1
  • SelectSqlExpression.CanCreateResultForCondition (cyclomatic 71) Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18.vb:2024 — SelectSqlExpression.CanCreateResultForCondition has cyclomatic complexity 71 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · JoinedSelectSqlExpression.CanCreateResultForCondition (cyclomatic 63) · ×1
  • JoinedSelectSqlExpression.CanCreateResultForCondition (cyclomatic 63) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:295 — JoinedSelectSqlExpression.CanCreateResultForCondition has cyclomatic complexity 63 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SelectSqlExpression.CanCreateResultForCondition (cyclomatic 62) · ×1
  • SelectSqlExpression.CanCreateResultForCondition (cyclomatic 62) Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:2102 — SelectSqlExpression.CanCreateResultForCondition has cyclomatic complexity 62 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · JoinedSelectSqlExpression.CanCreateResultForCondition (cyclomatic 54) · ×1
  • JoinedSelectSqlExpression.CanCreateResultForCondition (cyclomatic 54) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb:306 — JoinedSelectSqlExpression.CanCreateResultForCondition has cyclomatic complexity 54 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SelectSqlExpression.CanCreateResultForCondition (cyclomatic 53) · ×1
  • SelectSqlExpression.CanCreateResultForCondition (cyclomatic 53) Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb:2180 — SelectSqlExpression.CanCreateResultForCondition has cyclomatic complexity 53 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · JoinedSelectSqlExpression.CanCreateResultForCondition (cyclomatic 45) · ×1
  • JoinedSelectSqlExpression.CanCreateResultForCondition (cyclomatic 45) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb:317 — JoinedSelectSqlExpression.CanCreateResultForCondition has cyclomatic complexity 45 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SelectSqlExpression.CanCreateResultForCondition (cyclomatic 44) · ×1
  • SelectSqlExpression.CanCreateResultForCondition (cyclomatic 44) Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb:2258 — SelectSqlExpression.CanCreateResultForCondition has cyclomatic complexity 44 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SqlExpressionVisitor.VisitBinary (cyclomatic 37) · ×1
  • SqlExpressionVisitor.VisitBinary (cyclomatic 37) Source/Source/Yamo/Internal/SqlExpressionVisitor.vb:714 — SqlExpressionVisitor.VisitBinary has cyclomatic complexity 37 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · JoinedSelectSqlExpression.CanCreateResultForCondition (cyclomatic 36) · ×1
  • JoinedSelectSqlExpression.CanCreateResultForCondition (cyclomatic 36) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb:328 — JoinedSelectSqlExpression.CanCreateResultForCondition has cyclomatic complexity 36 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SelectSqlExpression.CanCreateResultForCondition (cyclomatic 35) · ×1
  • SelectSqlExpression.CanCreateResultForCondition (cyclomatic 35) Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb:2336 — SelectSqlExpression.CanCreateResultForCondition has cyclomatic complexity 35 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · JoinedSelectSqlExpression.CanCreateResultForCondition (cyclomatic 27) · ×1
  • JoinedSelectSqlExpression.CanCreateResultForCondition (cyclomatic 27) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb:339 — JoinedSelectSqlExpression.CanCreateResultForCondition has cyclomatic complexity 27 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SelectSqlExpression.CanCreateResultForCondition (cyclomatic 26) · ×1
  • SelectSqlExpression.CanCreateResultForCondition (cyclomatic 26) Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb:2414 — SelectSqlExpression.CanCreateResultForCondition has cyclomatic complexity 26 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SqlExpressionVisitor.VisitMethodCall (cyclomatic 19) · ×1
  • SqlExpressionVisitor.VisitMethodCall (cyclomatic 19) Source/Source/Yamo/Internal/SqlExpressionVisitor.vb:332 — SqlExpressionVisitor.VisitMethodCall has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · CodeGenerator.GenerateCanCreateResultForCondition (cyclomatic 19) · ×1
  • CodeGenerator.GenerateCanCreateResultForCondition (cyclomatic 19) Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.If.vb:84 — CodeGenerator.GenerateCanCreateResultForCondition has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · JoinedSelectSqlExpression.CanCreateResultForCondition (cyclomatic 18) · ×1
  • JoinedSelectSqlExpression.CanCreateResultForCondition (cyclomatic 18) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24.vb:350 — JoinedSelectSqlExpression.CanCreateResultForCondition has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SelectSqlExpressionBuilder.AddJoin (cyclomatic 17) · ×1
  • SelectSqlExpressionBuilder.AddJoin (cyclomatic 17) Source/Source/Yamo/Expressions/Builders/SelectSqlExpressionBuilder.vb:358 — SelectSqlExpressionBuilder.AddJoin has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SelectSqlExpression.CanCreateResultForCondition (cyclomatic 17) · ×1
  • SelectSqlExpression.CanCreateResultForCondition (cyclomatic 17) Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24.vb:2492 — SelectSqlExpression.CanCreateResultForCondition has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SelectSqlExpressionBuilder.CreateQuery (cyclomatic 16) · ×1
  • SelectSqlExpressionBuilder.CreateQuery (cyclomatic 16) Source/Source/Yamo/Expressions/Builders/SelectSqlExpressionBuilder.vb:1104 — SelectSqlExpressionBuilder.CreateQuery has cyclomatic complexity 16 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D17 · Explicit Debt · Dead code · ×1
  • Dead code: MyContext1 Source/Samples/Yamo.Playground.CS/MyContext.cs:161 — NamedType MyContext1 — Roslyn's SymbolFinder walked every project the solution loads, including Yamo.Playground.CS, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
D2 · Cognitive Complexity · SelectSqlExpression.CanCreateResultForCondition (cognitive 224) · ×1
  • SelectSqlExpression.CanCreateResultForCondition (cognitive 224) Source/Source/Yamo/Expressions/SelectSqlExpression.vb:739 — SelectSqlExpression.CanCreateResultForCondition has cognitive complexity 224 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · WithHintsSelectSqlExpression.CanCreateResultForCondition (cognitive 223) · ×1
  • WithHintsSelectSqlExpression.CanCreateResultForCondition (cognitive 223) Source/Source/Yamo/Expressions/WithHintsSelectSqlExpression.vb:660 — WithHintsSelectSqlExpression.CanCreateResultForCondition has cognitive complexity 223 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · JoinedSelectSqlExpression.CanCreateResultForCondition (cognitive 215) · ×1
  • JoinedSelectSqlExpression.CanCreateResultForCondition (cognitive 215) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb:98 — JoinedSelectSqlExpression.CanCreateResultForCondition has cognitive complexity 215 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SelectSqlExpression.CanCreateResultForCondition (cognitive 214) · ×1
  • SelectSqlExpression.CanCreateResultForCondition (cognitive 214) Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2.vb:935 — SelectSqlExpression.CanCreateResultForCondition has cognitive complexity 214 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · JoinedSelectSqlExpression.CanCreateResultForCondition (cognitive 206) · ×1
  • JoinedSelectSqlExpression.CanCreateResultForCondition (cognitive 206) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3.vb:119 — JoinedSelectSqlExpression.CanCreateResultForCondition has cognitive complexity 206 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SelectSqlExpression.CanCreateResultForCondition (cognitive 205) · ×1
  • SelectSqlExpression.CanCreateResultForCondition (cognitive 205) Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3.vb:1013 — SelectSqlExpression.CanCreateResultForCondition has cognitive complexity 205 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · JoinedSelectSqlExpression.CanCreateResultForCondition (cognitive 197) · ×1
  • JoinedSelectSqlExpression.CanCreateResultForCondition (cognitive 197) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4.vb:130 — JoinedSelectSqlExpression.CanCreateResultForCondition has cognitive complexity 197 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SelectSqlExpression.CanCreateResultForCondition (cognitive 196) · ×1
  • SelectSqlExpression.CanCreateResultForCondition (cognitive 196) Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4.vb:1113 — SelectSqlExpression.CanCreateResultForCondition has cognitive complexity 196 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · JoinedSelectSqlExpression.CanCreateResultForCondition (cognitive 188) · ×1
  • JoinedSelectSqlExpression.CanCreateResultForCondition (cognitive 188) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5.vb:141 — JoinedSelectSqlExpression.CanCreateResultForCondition has cognitive complexity 188 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SelectSqlExpression.CanCreateResultForCondition (cognitive 187) · ×1
  • SelectSqlExpression.CanCreateResultForCondition (cognitive 187) Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5.vb:1231 — SelectSqlExpression.CanCreateResultForCondition has cognitive complexity 187 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · JoinedSelectSqlExpression.CanCreateResultForCondition (cognitive 179) · ×1
  • JoinedSelectSqlExpression.CanCreateResultForCondition (cognitive 179) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6.vb:152 — JoinedSelectSqlExpression.CanCreateResultForCondition has cognitive complexity 179 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SelectSqlExpression.CanCreateResultForCondition (cognitive 178) · ×1
  • SelectSqlExpression.CanCreateResultForCondition (cognitive 178) Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6.vb:1349 — SelectSqlExpression.CanCreateResultForCondition has cognitive complexity 178 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · JoinedSelectSqlExpression.CanCreateResultForCondition (cognitive 170) · ×1
  • JoinedSelectSqlExpression.CanCreateResultForCondition (cognitive 170) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7.vb:163 — JoinedSelectSqlExpression.CanCreateResultForCondition has cognitive complexity 170 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SelectSqlExpression.CanCreateResultForCondition (cognitive 169) · ×1
  • SelectSqlExpression.CanCreateResultForCondition (cognitive 169) Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7.vb:1187 — SelectSqlExpression.CanCreateResultForCondition has cognitive complexity 169 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · JoinedSelectSqlExpression.CanCreateResultForCondition (cognitive 161) · ×1
  • JoinedSelectSqlExpression.CanCreateResultForCondition (cognitive 161) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8.vb:174 — JoinedSelectSqlExpression.CanCreateResultForCondition has cognitive complexity 161 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SelectSqlExpression.CanCreateResultForCondition (cognitive 160) · ×1
  • SelectSqlExpression.CanCreateResultForCondition (cognitive 160) Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8.vb:1244 — SelectSqlExpression.CanCreateResultForCondition has cognitive complexity 160 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · JoinedSelectSqlExpression.CanCreateResultForCondition (cognitive 152) · ×1
  • JoinedSelectSqlExpression.CanCreateResultForCondition (cognitive 152) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9.vb:185 — JoinedSelectSqlExpression.CanCreateResultForCondition has cognitive complexity 152 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SelectSqlExpression.CanCreateResultForCondition (cognitive 151) · ×1
  • SelectSqlExpression.CanCreateResultForCondition (cognitive 151) Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9.vb:1322 — SelectSqlExpression.CanCreateResultForCondition has cognitive complexity 151 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · JoinedSelectSqlExpression.CanCreateResultForCondition (cognitive 143) · ×1
  • JoinedSelectSqlExpression.CanCreateResultForCondition (cognitive 143) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10.vb:196 — JoinedSelectSqlExpression.CanCreateResultForCondition has cognitive complexity 143 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SelectSqlExpression.CanCreateResultForCondition (cognitive 142) · ×1
  • SelectSqlExpression.CanCreateResultForCondition (cognitive 142) Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10.vb:1400 — SelectSqlExpression.CanCreateResultForCondition has cognitive complexity 142 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · JoinedSelectSqlExpression.CanCreateResultForCondition (cognitive 134) · ×1
  • JoinedSelectSqlExpression.CanCreateResultForCondition (cognitive 134) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11.vb:207 — JoinedSelectSqlExpression.CanCreateResultForCondition has cognitive complexity 134 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SelectSqlExpression.CanCreateResultForCondition (cognitive 133) · ×1
  • SelectSqlExpression.CanCreateResultForCondition (cognitive 133) Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11.vb:1478 — SelectSqlExpression.CanCreateResultForCondition has cognitive complexity 133 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · JoinedSelectSqlExpression.CanCreateResultForCondition (cognitive 125) · ×1
  • JoinedSelectSqlExpression.CanCreateResultForCondition (cognitive 125) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12.vb:218 — JoinedSelectSqlExpression.CanCreateResultForCondition has cognitive complexity 125 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SelectSqlExpression.CanCreateResultForCondition (cognitive 124) · ×1
  • SelectSqlExpression.CanCreateResultForCondition (cognitive 124) Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12.vb:1556 — SelectSqlExpression.CanCreateResultForCondition has cognitive complexity 124 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · JoinedSelectSqlExpression.CanCreateResultForCondition (cognitive 116) · ×1
  • JoinedSelectSqlExpression.CanCreateResultForCondition (cognitive 116) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13.vb:229 — JoinedSelectSqlExpression.CanCreateResultForCondition has cognitive complexity 116 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SelectSqlExpression.CanCreateResultForCondition (cognitive 115) · ×1
  • SelectSqlExpression.CanCreateResultForCondition (cognitive 115) Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13.vb:1634 — SelectSqlExpression.CanCreateResultForCondition has cognitive complexity 115 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · JoinedSelectSqlExpression.CanCreateResultForCondition (cognitive 107) · ×1
  • JoinedSelectSqlExpression.CanCreateResultForCondition (cognitive 107) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14.vb:240 — JoinedSelectSqlExpression.CanCreateResultForCondition has cognitive complexity 107 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SelectSqlExpression.CanCreateResultForCondition (cognitive 106) · ×1
  • SelectSqlExpression.CanCreateResultForCondition (cognitive 106) Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14.vb:1712 — SelectSqlExpression.CanCreateResultForCondition has cognitive complexity 106 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · JoinedSelectSqlExpression.CanCreateResultForCondition (cognitive 98) · ×1
  • JoinedSelectSqlExpression.CanCreateResultForCondition (cognitive 98) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15.vb:251 — JoinedSelectSqlExpression.CanCreateResultForCondition has cognitive complexity 98 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SelectSqlExpression.CanCreateResultForCondition (cognitive 97) · ×1
  • SelectSqlExpression.CanCreateResultForCondition (cognitive 97) Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15.vb:1790 — SelectSqlExpression.CanCreateResultForCondition has cognitive complexity 97 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · JoinedSelectSqlExpression.CanCreateResultForCondition (cognitive 89) · ×1
  • JoinedSelectSqlExpression.CanCreateResultForCondition (cognitive 89) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16.vb:262 — JoinedSelectSqlExpression.CanCreateResultForCondition has cognitive complexity 89 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SelectSqlExpression.CanCreateResultForCondition (cognitive 88) · ×1
  • SelectSqlExpression.CanCreateResultForCondition (cognitive 88) Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16.vb:1868 — SelectSqlExpression.CanCreateResultForCondition has cognitive complexity 88 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · JoinedSelectSqlExpression.CanCreateResultForCondition (cognitive 80) · ×1
  • JoinedSelectSqlExpression.CanCreateResultForCondition (cognitive 80) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17.vb:273 — JoinedSelectSqlExpression.CanCreateResultForCondition has cognitive complexity 80 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SelectSqlExpression.CanCreateResultForCondition (cognitive 79) · ×1
  • SelectSqlExpression.CanCreateResultForCondition (cognitive 79) Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17.vb:1946 — SelectSqlExpression.CanCreateResultForCondition has cognitive complexity 79 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · JoinedSelectSqlExpression.CanCreateResultForCondition (cognitive 71) · ×1
  • JoinedSelectSqlExpression.CanCreateResultForCondition (cognitive 71) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18.vb:284 — JoinedSelectSqlExpression.CanCreateResultForCondition has cognitive complexity 71 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SelectSqlExpression.CanCreateResultForCondition (cognitive 70) · ×1
  • SelectSqlExpression.CanCreateResultForCondition (cognitive 70) Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18.vb:2024 — SelectSqlExpression.CanCreateResultForCondition has cognitive complexity 70 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · JoinedSelectSqlExpression.CanCreateResultForCondition (cognitive 62) · ×1
  • JoinedSelectSqlExpression.CanCreateResultForCondition (cognitive 62) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:295 — JoinedSelectSqlExpression.CanCreateResultForCondition has cognitive complexity 62 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SelectSqlExpression.CanCreateResultForCondition (cognitive 61) · ×1
  • SelectSqlExpression.CanCreateResultForCondition (cognitive 61) Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:2102 — SelectSqlExpression.CanCreateResultForCondition has cognitive complexity 61 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · JoinedSelectSqlExpression.CanCreateResultForCondition (cognitive 53) · ×1
  • JoinedSelectSqlExpression.CanCreateResultForCondition (cognitive 53) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb:306 — JoinedSelectSqlExpression.CanCreateResultForCondition has cognitive complexity 53 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SelectSqlExpression.CanCreateResultForCondition (cognitive 52) · ×1
  • SelectSqlExpression.CanCreateResultForCondition (cognitive 52) Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb:2180 — SelectSqlExpression.CanCreateResultForCondition has cognitive complexity 52 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SelectSqlExpressionBuilder.AddJoin (cognitive 47) · ×1
  • SelectSqlExpressionBuilder.AddJoin (cognitive 47) Source/Source/Yamo/Expressions/Builders/SelectSqlExpressionBuilder.vb:358 — SelectSqlExpressionBuilder.AddJoin has cognitive complexity 47 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · JoinedSelectSqlExpression.CanCreateResultForCondition (cognitive 44) · ×1
  • JoinedSelectSqlExpression.CanCreateResultForCondition (cognitive 44) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb:317 — JoinedSelectSqlExpression.CanCreateResultForCondition has cognitive complexity 44 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SelectSqlExpression.CanCreateResultForCondition (cognitive 43) · ×1
  • SelectSqlExpression.CanCreateResultForCondition (cognitive 43) Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb:2258 — SelectSqlExpression.CanCreateResultForCondition has cognitive complexity 43 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SelectSqlExpressionBuilder.BuildAndAppendSelectExpression (cognitive 36) · ×1
  • SelectSqlExpressionBuilder.BuildAndAppendSelectExpression (cognitive 36) Source/Source/Yamo/Expressions/Builders/SelectSqlExpressionBuilder.vb:1031 — SelectSqlExpressionBuilder.BuildAndAppendSelectExpression has cognitive complexity 36 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · JoinedSelectSqlExpression.CanCreateResultForCondition (cognitive 35) · ×1
  • JoinedSelectSqlExpression.CanCreateResultForCondition (cognitive 35) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb:328 — JoinedSelectSqlExpression.CanCreateResultForCondition has cognitive complexity 35 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SelectSqlExpressionBuilder.GetEntityAndProperty (cognitive 34) · ×1
  • SelectSqlExpressionBuilder.GetEntityAndProperty (cognitive 34) Source/Source/Yamo/Expressions/Builders/SelectSqlExpressionBuilder.vb:1202 — SelectSqlExpressionBuilder.GetEntityAndProperty has cognitive complexity 34 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SelectSqlExpression.CanCreateResultForCondition (cognitive 34) · ×1
  • SelectSqlExpression.CanCreateResultForCondition (cognitive 34) Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb:2336 — SelectSqlExpression.CanCreateResultForCondition has cognitive complexity 34 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SqlExpressionVisitor.Evaluate (cognitive 32) · ×1
  • SqlExpressionVisitor.Evaluate (cognitive 32) Source/Source/Yamo/Internal/SqlExpressionVisitor.vb:1342 — SqlExpressionVisitor.Evaluate has cognitive complexity 32 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ReaderDataFactory.CreateAuto (cognitive 31) · ×1
  • ReaderDataFactory.CreateAuto (cognitive 31) Source/Source/Yamo/Internal/Query/ReaderDataFactory.vb:29 — ReaderDataFactory.CreateAuto has cognitive complexity 31 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · QueryExecutor.ReadSimpleList (cognitive 30) · ×1
  • QueryExecutor.ReadSimpleList (cognitive 30) Source/Source/Yamo/Internal/Query/QueryExecutor.vb:465 — QueryExecutor.ReadSimpleList has cognitive complexity 30 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · JoinedSelectSqlExpression.CanCreateResultForCondition (cognitive 26) · ×1
  • JoinedSelectSqlExpression.CanCreateResultForCondition (cognitive 26) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb:339 — JoinedSelectSqlExpression.CanCreateResultForCondition has cognitive complexity 26 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SelectSqlExpression.CanCreateResultForCondition (cognitive 25) · ×1
  • SelectSqlExpression.CanCreateResultForCondition (cognitive 25) Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb:2414 — SelectSqlExpression.CanCreateResultForCondition has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · AdHocTypeSqlResultReaderKey.Equals (cognitive 25) · ×1
  • AdHocTypeSqlResultReaderKey.Equals (cognitive 25) Source/Source/Yamo/Internal/Query/Metadata/AdHocTypeSqlResultReaderKey.vb:51 — AdHocTypeSqlResultReaderKey.Equals has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SqlExpressionVisitor.VisitBinary (cognitive 24) · ×1
  • SqlExpressionVisitor.VisitBinary (cognitive 24) Source/Source/Yamo/Internal/SqlExpressionVisitor.vb:714 — SqlExpressionVisitor.VisitBinary has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · Exp.GetSqlFormatForRaw (cognitive 22) · ×1
  • Exp.GetSqlFormatForRaw (cognitive 22) Source/Source/Yamo/Sql/Exp.vb:146 — Exp.GetSqlFormatForRaw has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SqlExpressionVisitor.ShouldIgnoreNegation (cognitive 21) · ×1
  • SqlExpressionVisitor.ShouldIgnoreNegation (cognitive 21) Source/Source/Yamo/Internal/SqlExpressionVisitor.vb:1656 — SqlExpressionVisitor.ShouldIgnoreNegation has cognitive complexity 21 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · QueryExecutor.ReadSimpleFirstOrDefault (cognitive 20) · ×1
  • QueryExecutor.ReadSimpleFirstOrDefault (cognitive 20) Source/Source/Yamo/Internal/Query/QueryExecutor.vb:279 — QueryExecutor.ReadSimpleFirstOrDefault has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SqlExpressionVisitor.VisitInCustomSelectOrIncludeMode (cognitive 20) · ×1
  • SqlExpressionVisitor.VisitInCustomSelectOrIncludeMode (cognitive 20) Source/Source/Yamo/Internal/SqlExpressionVisitor.vb:1286 — SqlExpressionVisitor.VisitInCustomSelectOrIncludeMode has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · Select500RecordsOneByOne.Handcoded (cognitive 20) · ×1
  • Select500RecordsOneByOne.Handcoded (cognitive 20) Source/Benchmarks/Yamo.Benchmarks/Select500RecordsOneByOne.vb:79 — Select500RecordsOneByOne.Handcoded has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · QueryExecutor.Read (cognitive 19) · ×1
  • QueryExecutor.Read (cognitive 19) Source/Source/Yamo/Internal/Query/QueryExecutor.vb:686 — QueryExecutor.Read has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SqlExpressionVisitor.VisitMethodCall (cognitive 19) · ×1
  • SqlExpressionVisitor.VisitMethodCall (cognitive 19) Source/Source/Yamo/Internal/SqlExpressionVisitor.vb:332 — SqlExpressionVisitor.VisitMethodCall has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · CodeGenerator.GenerateCanCreateResultForCondition (cognitive 19) · ×1
  • CodeGenerator.GenerateCanCreateResultForCondition (cognitive 19) Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.If.vb:84 — CodeGenerator.GenerateCanCreateResultForCondition has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SelectListOf1000RecordsWith1ToNJoin.Handcoded (cognitive 19) · ×1
  • SelectListOf1000RecordsWith1ToNJoin.Handcoded (cognitive 19) Source/Benchmarks/Yamo.Benchmarks/SelectListOf1000RecordsWith1ToNJoin.vb:52 — SelectListOf1000RecordsWith1ToNJoin.Handcoded has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SelectSqlExpressionBuilder.CreateQuery (cognitive 18) · ×1
  • SelectSqlExpressionBuilder.CreateQuery (cognitive 18) Source/Source/Yamo/Expressions/Builders/SelectSqlExpressionBuilder.vb:1104 — SelectSqlExpressionBuilder.CreateQuery has cognitive complexity 18 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · EntityReaderFactory.CreateReader (cognitive 18) · ×1
  • EntityReaderFactory.CreateReader (cognitive 18) Source/Source/Yamo/Infrastructure/EntityReaderFactory.vb:25 — EntityReaderFactory.CreateReader has cognitive complexity 18 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: one other method here (EntityReaderFactory.CreateDbGeneratedValuesReader) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · EntityReaderFactory.CreateDbGeneratedValuesReader (cognitive 18) · ×1
  • EntityReaderFactory.CreateDbGeneratedValuesReader (cognitive 18) Source/Source/Yamo/Infrastructure/EntityReaderFactory.vb:276 — EntityReaderFactory.CreateDbGeneratedValuesReader has cognitive complexity 18 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: one other method here (EntityReaderFactory.CreateReader) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · SqlExpressionVisitor.VisitMember (cognitive 18) · ×1
  • SqlExpressionVisitor.VisitMember (cognitive 18) Source/Source/Yamo/Internal/SqlExpressionVisitor.vb:950 — SqlExpressionVisitor.VisitMember has cognitive complexity 18 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · JoinedSelectSqlExpression.CanCreateResultForCondition (cognitive 17) · ×1
  • JoinedSelectSqlExpression.CanCreateResultForCondition (cognitive 17) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24.vb:350 — JoinedSelectSqlExpression.CanCreateResultForCondition has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SqlExpressionVisitor.VisitEnumerableContainsMethodCall (cognitive 17) · ×1
  • SqlExpressionVisitor.VisitEnumerableContainsMethodCall (cognitive 17) Source/Source/Yamo/Internal/SqlExpressionVisitor.vb:603 — SqlExpressionVisitor.VisitEnumerableContainsMethodCall has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SelectSqlExpression.CanCreateResultForCondition (cognitive 16) · ×1
  • SelectSqlExpression.CanCreateResultForCondition (cognitive 16) Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24.vb:2492 — SelectSqlExpression.CanCreateResultForCondition has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SqlExpressionVisitor.VisitNewValueTupleOrAnonymousOrAdHocType (cognitive 16) · ×1
  • SqlExpressionVisitor.VisitNewValueTupleOrAnonymousOrAdHocType (cognitive 16) Source/Source/Yamo/Internal/SqlExpressionVisitor.vb:1089 — SqlExpressionVisitor.VisitNewValueTupleOrAnonymousOrAdHocType has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SqlExpressionVisitor.IsNestedConstructorOfNullableValueTupleTypeSqlResult (cognitive 16) · ×1
  • SqlExpressionVisitor.IsNestedConstructorOfNullableValueTupleTypeSqlResult (cognitive 16) Source/Source/Yamo/Internal/SqlExpressionVisitor.vb:1849 — SqlExpressionVisitor.IsNestedConstructorOfNullableValueTupleTypeSqlResult has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SqlExpressionVisitor.IsNestedConstructorOfNullableAdHocTypeSqlResult (cognitive 16) · ×1
  • SqlExpressionVisitor.IsNestedConstructorOfNullableAdHocTypeSqlResult (cognitive 16) Source/Source/Yamo/Internal/SqlExpressionVisitor.vb:1896 — SqlExpressionVisitor.IsNestedConstructorOfNullableAdHocTypeSqlResult has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · CodeGenerator.GenerateJoin (cognitive 16) · ×1
  • CodeGenerator.GenerateJoin (cognitive 16) Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Join.vb:5 — CodeGenerator.GenerateJoin has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D30 · Dependency Vulnerabilities · Medium CVE · ×1
  • REDACTED
D4 · Code Duplication · Near-duplicate member family (42 members, 7 shared lines) · ×1
  • Near-duplicate member family (42 members, 7 shared lines) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb:99 — Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb:99-323 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3.vb:120-335 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4.vb:131-337 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5.vb:142-339 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6.vb:153-341 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7.vb:164-343 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8.vb:175-345 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9.vb:186-347 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10.vb:197-349 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11.vb:208-351 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15.vb:252-359 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16.vb:263-361 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17.vb:274-363 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18.vb:285-365 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:296-367 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb:307-369 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb:318-371 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb:329-373 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb:340-375 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24.vb:351-377 | Source/Source/Yamo/Expressions/SelectSqlExpression.vb:740-973 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2.vb:936-1159 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3.vb:1014-1228 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4.vb:1114-1319 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5.vb:1232-1428 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6.vb:1350-1537 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7.vb:1188-1366 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8.vb:1245-1414 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9.vb:1323-1483 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10.vb:1401-1552 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14.vb:1713-1828 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15.vb:1791-1897 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16.vb:1869-1966 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17.vb:1947-2035 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18.vb:2025-2104 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:2103-2173 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb:2181-2242 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb:2259-2311 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb:2337-2380 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb:2415-2449 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24.vb:2493-2518 | Source/Source/Yamo/Expressions/WithHintsSelectSqlExpression.vb:661-893 — These 42 members are variants of one another: a block of 7 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 42 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 42 times.
D4 · Code Duplication · Near-duplicate member family (18 members, 22 shared lines) · ×1
  • Near-duplicate member family (18 members, 22 shared lines) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15.vb:252 — Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15.vb:252-359 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16.vb:263-361 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17.vb:274-363 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18.vb:285-365 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:296-367 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb:307-369 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb:318-371 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb:329-373 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb:340-375 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15.vb:1791-1897 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16.vb:1869-1966 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17.vb:1947-2035 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18.vb:2025-2104 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:2103-2173 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb:2181-2242 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb:2259-2311 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb:2337-2380 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb:2415-2449 — These 18 members are variants of one another: a block of 22 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 18 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 18 times.
D4 · Code Duplication · Near-duplicate member family (14 members, 13 shared lines) · ×1
  • Near-duplicate member family (14 members, 13 shared lines) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:296 — Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:296-367 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb:307-369 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb:318-371 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb:329-373 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb:340-375 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24.vb:351-377 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24T25.vb:362-379 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18.vb:2025-2104 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:2103-2173 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb:2181-2242 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb:2259-2311 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb:2337-2380 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb:2415-2449 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24.vb:2493-2518 — These 14 members are variants of one another: a block of 13 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 14 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 14 times.
D4 · Code Duplication · Near-duplicate member family (14 members, 9 shared lines) · ×1
  • Near-duplicate member family (14 members, 9 shared lines) Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:1563 — Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:1563-1577 | Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb:1631-1645 | Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb:1699-1713 | Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb:1767-1781 | Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb:1835-1849 | Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24.vb:1903-1917 | Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24T25.vb:1971-1985 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:1555-1569 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb:1623-1637 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb:1691-1705 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb:1759-1773 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb:1827-1841 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24.vb:1895-1909 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24T25.vb:1963-1977 — These 14 members are variants of one another: a block of 9 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 14 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 14 times.
D4 · Code Duplication · Near-duplicate member family (9 members, 51 shared lines) · ×1
  • Near-duplicate member family (9 members, 51 shared lines) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb:99 — Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb:99-323 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3.vb:120-335 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4.vb:131-337 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5.vb:142-339 | Source/Source/Yamo/Expressions/SelectSqlExpression.vb:740-973 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2.vb:936-1159 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3.vb:1014-1228 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4.vb:1114-1319 | Source/Source/Yamo/Expressions/WithHintsSelectSqlExpression.vb:661-893 — These 9 members are variants of one another: a block of 51 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 9 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 9 times.
D4 · Code Duplication · Near-duplicate member family (8 members, 9 shared lines) · ×1
  • Near-duplicate member family (8 members, 9 shared lines) Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:1777 — Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:1777-1793 | Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb:1855-1871 | Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb:1933-1949 | Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb:2011-2027 | Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb:2089-2105 | Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24.vb:2167-2183 | Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24T25.vb:2245-2261 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24T25.vb:2264-2280 — These 8 members are variants of one another: a block of 9 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 8 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 8 times.
D4 · Code Duplication · Near-duplicate member family (6 members, 35 shared lines) · ×1
  • Near-duplicate member family (6 members, 35 shared lines) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7.vb:164 — Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7.vb:164-343 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8.vb:175-345 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9.vb:186-347 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7.vb:1188-1366 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8.vb:1245-1414 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9.vb:1323-1483 — These 6 members are variants of one another: a block of 35 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
D4 · Code Duplication · Near-duplicate member family (6 members, 19 shared lines) · ×1
  • Near-duplicate member family (6 members, 19 shared lines) Source/Source/Yamo.CodeGenerator/Generator/CustomDistinctSelectSqlExpressionCodeGenerator.vb:15 — Source/Source/Yamo.CodeGenerator/Generator/CustomDistinctSelectSqlExpressionCodeGenerator.vb:15-54 | Source/Source/Yamo.CodeGenerator/Generator/CustomSelectSqlExpressionCodeGenerator.vb:18-60 | Source/Source/Yamo.CodeGenerator/Generator/CustomSetSelectSqlExpressionCodeGenerator.vb:17-56 | Source/Source/Yamo.CodeGenerator/Generator/DistinctSelectSqlExpressionCodeGenerator.vb:15-54 | Source/Source/Yamo.CodeGenerator/Generator/SelectedSelectSqlExpressionCodeGenerator.vb:19-67 | Source/Source/Yamo.CodeGenerator/Generator/SetSelectSqlExpressionCodeGenerator.vb:17-56 — These 6 members are variants of one another: a block of 19 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
D4 · Code Duplication · Near-duplicate member family (4 members, 27 shared lines) · ×1
  • Near-duplicate member family (4 members, 27 shared lines) Source/Source/Yamo/Infrastructure/EntitySqlStringProviderFactory.vb:215 — Source/Source/Yamo/Infrastructure/EntitySqlStringProviderFactory.vb:215-287 | Source/Source/Yamo/Infrastructure/EntitySqlStringProviderFactory.vb:394-447 | Source/Source/Yamo/Infrastructure/EntitySqlStringProviderFactory.vb:458-529 | Source/Source/Yamo/Infrastructure/EntitySqlStringProviderFactory.vb:540-590 — These 4 members are variants of one another: a block of 27 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication · Near-duplicate member family (4 members, 20 shared lines) · ×1
  • Near-duplicate member family (4 members, 20 shared lines) Source/Source/Yamo/Infrastructure/EntitySqlStringProviderFactory.vb:27 — Source/Source/Yamo/Infrastructure/EntitySqlStringProviderFactory.vb:27-131 | Source/Source/Yamo/Infrastructure/EntitySqlStringProviderFactory.vb:215-287 | Source/Source/Yamo/Infrastructure/EntitySqlStringProviderFactory.vb:394-447 | Source/Source/Yamo/Infrastructure/EntitySqlStringProviderFactory.vb:458-529 — These 4 members are variants of one another: a block of 20 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication · Near-duplicate member family (4 members, 18 shared lines) · ×1
  • Near-duplicate member family (4 members, 18 shared lines) Source/Source/Yamo/Infrastructure/EntitySqlStringProviderFactory.vb:215 — Source/Source/Yamo/Infrastructure/EntitySqlStringProviderFactory.vb:215-287 | Source/Source/Yamo/Infrastructure/EntitySqlStringProviderFactory.vb:298-383 | Source/Source/Yamo/Infrastructure/EntitySqlStringProviderFactory.vb:394-447 | Source/Source/Yamo/Infrastructure/EntitySqlStringProviderFactory.vb:458-529 — These 4 members are variants of one another: a block of 18 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication · Near-duplicate member pair (41 shared lines) · ×1
  • Near-duplicate member pair (41 shared lines) Source/Source/Yamo.CodeGenerator/Generator/SelectSqlExpressionCodeGenerator.vb:26 — Source/Source/Yamo.CodeGenerator/Generator/SelectSqlExpressionCodeGenerator.vb:26-83 | Source/Source/Yamo.CodeGenerator/Generator/WithHintsSelectSqlExpressionCodeGenerator.vb:25-74 — These two members are variants of one another: 41 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication · Members sharing a duplicated core (154 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (154 members, 50+ identical tokens) Source/Source/Yamo/Expressions/CustomDistinctSelectSqlExpression.vb:196 — Source/Source/Yamo/Expressions/CustomDistinctSelectSqlExpression.vb:196-207 | Source/Source/Yamo/Expressions/CustomSelectSqlExpression.vb:205-216 | Source/Source/Yamo/Expressions/CustomSetSelectSqlExpression.vb:196-207 | Source/Source/Yamo/Expressions/DistinctSelectSqlExpression.vb:196-207 | Source/Source/Yamo/Expressions/FilteredSelectSqlExpression.vb:275-286 | Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2.vb:470-481 | Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3.vb:548-559 | Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4.vb:608-619 | Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5.vb:686-697 | Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6.vb:764-775 | Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7.vb:842-853 | Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8.vb:899-910 | Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9.vb:977-988 | Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10.vb:1055-1066 | Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11.vb:1133-1144 | Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12.vb:1211-1222 | Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13.vb:1289-1300 | Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14.vb:1367-1378 | Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15.vb:1445-1456 | Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16.vb:1523-1534 | Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17.vb:1601-1612 | Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18.vb:1679-1690 | Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:1757-1768 | Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb:1835-1846 | Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb:1913-1924 | Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb:1991-2002 | Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb:2069-2080 | Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24.vb:2147-2158 | Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24T25.vb:2225-2236 | Source/Source/Yamo/Expressions/GroupedSelectSqlExpression.vb:251-262 | Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2.vb:416-427 | Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3.vb:484-495 | Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4.vb:534-545 | Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5.vb:602-613 | Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6.vb:670-681 | Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7.vb:738-749 | Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8.vb:795-806 | Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9.vb:863-874 | Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10.vb:931-942 | Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11.vb:999-1010 | Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12.vb:1067-1078 | Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13.vb:1135-1146 | Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14.vb:1203-1214 | Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15.vb:1271-1282 | Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16.vb:1339-1350 | Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17.vb:1407-1418 | Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18.vb:1475-1486 | Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:1543-1554 | Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb:1611-1622 | Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb:1679-1690 | Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb:1747-1758 | Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb:1815-1826 | Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24.vb:1883-1894 | Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24T25.vb:1951-1962 | Source/Source/Yamo/Expressions/HavingSelectSqlExpression.vb:243-254 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2.vb:408-419 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3.vb:476-487 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4.vb:526-537 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5.vb:594-605 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6.vb:662-673 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7.vb:730-741 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8.vb:787-798 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9.vb:855-866 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10.vb:923-934 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11.vb:991-1002 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12.vb:1059-1070 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13.vb:1127-1138 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14.vb:1195-1206 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15.vb:1263-1274 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16.vb:1331-1342 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17.vb:1399-1410 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18.vb:1467-1478 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:1535-1546 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb:1603-1614 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb:1671-1682 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb:1739-1750 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb:1807-1818 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24.vb:1875-1886 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24T25.vb:1943-1954 | Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2.vb:88-99 | Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3.vb:107-118 | Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4.vb:108-119 | Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5.vb:118-129 | Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6.vb:128-139 | Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7.vb:138-149 | Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8.vb:85-96 | Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9.vb:86-97 | Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10.vb:87-98 | Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11.vb:88-99 | Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12.vb:89-100 | Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13.vb:90-101 | Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14.vb:91-102 | Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15.vb:92-103 | Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16.vb:93-104 | Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17.vb:94-105 | Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18.vb:95-106 | Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:96-107 | Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb:97-108 | Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb:98-109 | Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb:99-110 | Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb:100-111 | Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24.vb:101-112 | Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24T25.vb:102-113 | Source/Source/Yamo/Expressions/OrderedSelectSqlExpression.vb:203-214 | Source/Source/Yamo/Expressions/OrderedSelectSqlExpressionOfT1T2.vb:314-325 | Source/Source/Yamo/Expressions/OrderedSelectSqlExpressionOfT1T2T3.vb:364-375 | Source/Source/Yamo/Expressions/OrderedSelectSqlExpressionOfT1T2T3T4.vb:414-425 | Source/Source/Yamo/Expressions/OrderedSelectSqlExpressionOfT1T2T3T4T5.vb:464-475 | Source/Source/Yamo/Expressions/OrderedSelectSqlExpressionOfT1T2T3T4T5T6.vb:514-525 | Source/Source/Yamo/Expressions/OrderedSelectSqlExpressionOfT1T2T3T4T5T6T7.vb:564-575 | Source/Source/Yamo/Expressions/OrderedSelectSqlExpressionOfT1T2T3T4T5T6T7T8.vb:603-614 | Source/Source/Yamo/Expressions/OrderedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9.vb:653-664 | Source/Source/Yamo/Expressions/OrderedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10.vb:703-714 | Source/Source/Yamo/Expressions/OrderedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11.vb:753-764 | Source/Source/Yamo/Expressions/OrderedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12.vb:803-814 | Source/Source/Yamo/Expressions/OrderedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13.vb:853-864 | Source/Source/Yamo/Expressions/OrderedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14.vb:903-914 | Source/Source/Yamo/Expressions/OrderedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15.vb:953-964 | Source/Source/Yamo/Expressions/OrderedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16.vb:1003-1014 | Source/Source/Yamo/Expressions/OrderedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17.vb:1053-1064 | Source/Source/Yamo/Expressions/OrderedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18.vb:1103-1114 | Source/Source/Yamo/Expressions/OrderedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:1153-1164 | Source/Source/Yamo/Expressions/OrderedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb:1203-1214 | Source/Source/Yamo/Expressions/OrderedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb:1253-1264 | Source/Source/Yamo/Expressions/OrderedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb:1303-1314 | Source/Source/Yamo/Expressions/OrderedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb:1353-1364 | Source/Source/Yamo/Expressions/OrderedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24.vb:1403-1414 | Source/Source/Yamo/Expressions/OrderedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24T25.vb:1453-1464 | Source/Source/Yamo/Expressions/SelectedSelectSqlExpression.vb:273-284 | Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2.vb:380-391 | Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3.vb:469-480 | Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4.vb:582-593 | Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5.vb:719-730 | Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6.vb:880-891 | Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7.vb:1065-1076 | Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8.vb:1274-1285 | Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9.vb:1507-1518 | Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10.vb:1764-1775 | Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11.vb:2045-2056 | Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12.vb:2350-2361 | Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13.vb:2679-2690 | Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14.vb:3032-3043 | Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15.vb:3409-3420 | Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16.vb:3810-3821 | Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17.vb:4235-4246 | Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18.vb:4684-4695 | Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:5157-5168 | Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb:5654-5665 | Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb:6175-6186 | Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb:6720-6731 | Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb:7289-7300 | Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24.vb:7882-7893 | Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24T25.vb:8499-8510 | Source/Source/Yamo/Expressions/SetSelectSqlExpression.vb:196-207 — These 154 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 154 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 154 times.
D4 · Code Duplication · Members sharing a duplicated core (50 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (50 members, 50+ identical tokens) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb:69 — Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb:69-90 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3.vb:90-111 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4.vb:101-122 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5.vb:112-133 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6.vb:123-144 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7.vb:134-155 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8.vb:145-166 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9.vb:156-177 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10.vb:167-188 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11.vb:178-199 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12.vb:189-210 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13.vb:200-221 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14.vb:211-232 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15.vb:222-243 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16.vb:233-254 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17.vb:244-265 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18.vb:255-276 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:266-287 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb:277-298 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb:288-309 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb:299-320 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb:310-331 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24.vb:321-342 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24T25.vb:332-353 | Source/Source/Yamo/Expressions/SelectSqlExpression.vb:710-731 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2.vb:906-927 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3.vb:984-1005 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4.vb:1084-1105 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5.vb:1202-1223 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6.vb:1320-1341 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7.vb:1158-1179 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8.vb:1215-1236 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9.vb:1293-1314 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10.vb:1371-1392 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11.vb:1449-1470 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12.vb:1527-1548 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13.vb:1605-1626 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14.vb:1683-1704 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15.vb:1761-1782 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16.vb:1839-1860 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17.vb:1917-1938 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18.vb:1995-2016 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:2073-2094 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb:2151-2172 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb:2229-2250 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb:2307-2328 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb:2385-2406 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24.vb:2463-2484 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24T25.vb:2234-2255 | Source/Source/Yamo/Expressions/WithHintsSelectSqlExpression.vb:631-652 — These 50 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 50 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 50 times.
D4 · Code Duplication · Members sharing a duplicated core (16 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (16 members, 50+ identical tokens) Source/Source/Yamo.CodeGenerator/Generator/CustomDistinctSelectSqlExpressionCodeGenerator.vb:58 — Source/Source/Yamo.CodeGenerator/Generator/CustomDistinctSelectSqlExpressionCodeGenerator.vb:58-64 | Source/Source/Yamo.CodeGenerator/Generator/CustomSelectSqlExpressionCodeGenerator.vb:64-70 | Source/Source/Yamo.CodeGenerator/Generator/CustomSetSelectSqlExpressionCodeGenerator.vb:60-66 | Source/Source/Yamo.CodeGenerator/Generator/DistinctSelectSqlExpressionCodeGenerator.vb:58-64 | Source/Source/Yamo.CodeGenerator/Generator/FilteredSelectSqlExpressionCodeGenerator.vb:63-71 | Source/Source/Yamo.CodeGenerator/Generator/GroupedSelectSqlExpressionCodeGenerator.vb:58-66 | Source/Source/Yamo.CodeGenerator/Generator/HavingSelectSqlExpressionCodeGenerator.vb:58-66 | Source/Source/Yamo.CodeGenerator/Generator/JoinSelectSqlExpressionCodeGenerator.vb:50-58 | Source/Source/Yamo.CodeGenerator/Generator/JoinWithHintsSelectSqlExpressionCodeGenerator.vb:45-53 | Source/Source/Yamo.CodeGenerator/Generator/JoinedSelectSqlExpressionCodeGenerator.vb:55-63 | Source/Source/Yamo.CodeGenerator/Generator/LimitedSelectSqlExpressionCodeGenerator.vb:45-51 | Source/Source/Yamo.CodeGenerator/Generator/OrderedSelectSqlExpressionCodeGenerator.vb:54-62 | Source/Source/Yamo.CodeGenerator/Generator/SelectSqlExpressionCodeGenerator.vb:87-179 | Source/Source/Yamo.CodeGenerator/Generator/SelectedSelectSqlExpressionCodeGenerator.vb:71-77 | Source/Source/Yamo.CodeGenerator/Generator/SetSelectSqlExpressionCodeGenerator.vb:60-66 | Source/Source/Yamo.CodeGenerator/Generator/WithHintsSelectSqlExpressionCodeGenerator.vb:78-88 — These 16 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 16 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 16 times.
D4 · Code Duplication · Members sharing a duplicated core (14 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (14 members, 50+ identical tokens) Source/Source/Yamo/JoinOfT1T2T3T4T5T6T7T8T9T10T11T12.vb:109 — Source/Source/Yamo/JoinOfT1T2T3T4T5T6T7T8T9T10T11T12.vb:109-120 | Source/Source/Yamo/JoinOfT1T2T3T4T5T6T7T8T9T10T11T12T13.vb:117-129 | Source/Source/Yamo/JoinOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14.vb:125-138 | Source/Source/Yamo/JoinOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15.vb:133-147 | Source/Source/Yamo/JoinOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16.vb:141-156 | Source/Source/Yamo/JoinOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17.vb:149-165 | Source/Source/Yamo/JoinOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18.vb:157-174 | Source/Source/Yamo/JoinOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:165-183 | Source/Source/Yamo/JoinOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb:173-192 | Source/Source/Yamo/JoinOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb:181-201 | Source/Source/Yamo/JoinOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb:189-210 | Source/Source/Yamo/JoinOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb:197-219 | Source/Source/Yamo/JoinOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24.vb:205-228 | Source/Source/Yamo/JoinOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24T25.vb:213-237 — These 14 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 14 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 14 times.
D4 · Code Duplication · Members sharing a duplicated core (8 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (8 members, 50+ identical tokens) Source/Source/Yamo.CodeGenerator/Generator/FilteredSelectSqlExpressionCodeGenerator.vb:21 — Source/Source/Yamo.CodeGenerator/Generator/FilteredSelectSqlExpressionCodeGenerator.vb:21-59 | Source/Source/Yamo.CodeGenerator/Generator/GroupedSelectSqlExpressionCodeGenerator.vb:19-54 | Source/Source/Yamo.CodeGenerator/Generator/HavingSelectSqlExpressionCodeGenerator.vb:19-54 | Source/Source/Yamo.CodeGenerator/Generator/JoinSelectSqlExpressionCodeGenerator.vb:17-46 | Source/Source/Yamo.CodeGenerator/Generator/JoinWithHintsSelectSqlExpressionCodeGenerator.vb:15-41 | Source/Source/Yamo.CodeGenerator/Generator/JoinedSelectSqlExpressionCodeGenerator.vb:25-51 | Source/Source/Yamo.CodeGenerator/Generator/LimitedSelectSqlExpressionCodeGenerator.vb:15-41 | Source/Source/Yamo.CodeGenerator/Generator/OrderedSelectSqlExpressionCodeGenerator.vb:18-50 — These 8 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 8 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 8 times.
D4 · Code Duplication · Edited copy of a member (51 corresponding lines) · ×1
  • Edited copy of a member (51 corresponding lines) Source/Source/Yamo/Internal/Query/QueryExecutor.vb:622 — Source/Source/Yamo/Internal/Query/QueryExecutor.vb:622-672 | Source/Source/Yamo/Internal/Query/QueryExecutor.vb:687-756 — These two members are one piece of code written twice and then edited apart: 51 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (35 corresponding lines) · ×1
  • Edited copy of a member (35 corresponding lines) Source/Source/Yamo/Infrastructure/ValueTypeReaderFactory.vb:576 — Source/Source/Yamo/Infrastructure/ValueTypeReaderFactory.vb:576-610 | Source/Source/Yamo/Infrastructure/ValueTypeReaderFactory.vb:621-657 — These two members are one piece of code written twice and then edited apart: 35 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (65 corresponding lines) · ×1
  • Edited copy of a member (65 corresponding lines) Source/Source/Yamo/Infrastructure/EntityReaderFactory.vb:26 — Source/Source/Yamo/Infrastructure/EntityReaderFactory.vb:26-103 | Source/Source/Yamo/Infrastructure/EntityReaderFactory.vb:277-341 — These two members are one piece of code written twice and then edited apart: 65 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (20 corresponding lines) · ×1
  • Edited copy of a member (20 corresponding lines) Source/Source/Yamo/PredicateBuilder.vb:41 — Source/Source/Yamo/PredicateBuilder.vb:41-60 | Source/Source/Yamo/PredicateBuilder.vb:127-146 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (28 corresponding lines) · ×1
  • Edited copy of a member (28 corresponding lines) Source/Source/Yamo/Internal/SqlExpressionVisitor.vb:1862 — Source/Source/Yamo/Internal/SqlExpressionVisitor.vb:1862-1889 | Source/Source/Yamo/Internal/SqlExpressionVisitor.vb:1913-1940 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 31+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 31+ corresponding lines) Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Having.vb:6 — Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Having.vb:6-36 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Where.And.vb:6-41 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Where.vb:6-44 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 31 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (13 corresponding lines) · ×1
  • Edited copy of a member (13 corresponding lines) Source/Source/Yamo/Infrastructure/MemberSetterFactory.vb:23 — Source/Source/Yamo/Infrastructure/MemberSetterFactory.vb:23-35 | Source/Source/Yamo/Infrastructure/MemberSetterFactory.vb:47-60 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (8 members, 11+ corresponding lines) · ×1
  • Edited copies of one member (8 members, 11+ corresponding lines) Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Join.vb:520 — Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Join.vb:520-531 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Join.vb:535-546 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Join.vb:550-561 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Join.vb:565-575 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Join.vb:579-589 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Join.vb:593-603 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Join.vb:607-617 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Join.vb:621-631 — These 8 members are one piece of code written 8 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 8 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (6 members, 10+ corresponding lines) · ×1
  • Edited copies of one member (6 members, 10+ corresponding lines) Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Set.vb:386 — Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Set.vb:386-395 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Set.vb:399-408 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Set.vb:412-421 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Set.vb:425-434 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Set.vb:438-447 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Set.vb:451-460 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 8+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 8+ corresponding lines) Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Having.vb:114 — Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Having.vb:114-123 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Having.vb:127-134 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Having.vb:138-147 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 8+ corresponding lines) · ×1
  • Edited copies of one member (5 members, 8+ corresponding lines) Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Where.vb:122 — Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Where.vb:122-131 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Where.vb:135-144 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Where.vb:148-157 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Where.vb:161-168 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Where.vb:172-181 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (6 members, 8+ corresponding lines) · ×1
  • Edited copies of one member (6 members, 8+ corresponding lines) Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Distinct.vb:6 — Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Distinct.vb:6-14 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.Distinct.vb:18-26 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.FirstOrDefault.vb:19-27 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.ToList.vb:6-14 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.ToList.vb:18-26 | Source/Source/Yamo.CodeGenerator/Generator/CodeGenerator.ToSubquery.vb:6-13 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (21 corresponding lines) · ×1
  • Edited copy of a member (21 corresponding lines) Source/Source/Yamo/Internal/PostProcessorCache.vb:105 — Source/Source/Yamo/Internal/PostProcessorCache.vb:105-125 | Source/Source/Yamo/Internal/PostProcessorCache.vb:134-154 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (22 corresponding lines) · ×1
  • Edited copy of a member (22 corresponding lines) Source/Source/Yamo/Internal/SqlResultReaderCache.vb:137 — Source/Source/Yamo/Internal/SqlResultReaderCache.vb:137-158 | Source/Source/Yamo/Internal/SqlResultReaderCache.vb:168-189 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (19 corresponding lines) · ×1
  • Edited copy of a member (19 corresponding lines) Source/Source/Yamo/Internal/MemberSetterCache.vb:131 — Source/Source/Yamo/Internal/MemberSetterCache.vb:131-149 | Source/Source/Yamo/Internal/MemberSetterCache.vb:160-178 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (3 corresponding lines) · ×1
  • Edited copy of a member (3 corresponding lines) Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7.vb:247 — Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7.vb:247-249 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7.vb:272-274 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (6 corresponding lines) · ×1
  • Edited copy of a member (6 corresponding lines) Source/Source/Yamo.SqlServer/Sql/Exp.vb:24 — Source/Source/Yamo.SqlServer/Sql/Exp.vb:24-29 | Source/Source/Yamo.SQLite/Sql/Exp.vb:24-29 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (10–25 lines × 5) · ×1
  • Duplicated block (10–25 lines × 5) Source/Source/Yamo/Infrastructure/EntitySqlStringProviderFactory.vb:106 — Source/Source/Yamo/Infrastructure/EntitySqlStringProviderFactory.vb:106-130 | Source/Source/Yamo/Infrastructure/EntitySqlStringProviderFactory.vb:277-286 | Source/Source/Yamo/Infrastructure/EntitySqlStringProviderFactory.vb:437-446 | Source/Source/Yamo/Infrastructure/EntitySqlStringProviderFactory.vb:519-528 | Source/Source/Yamo/Infrastructure/EntitySqlStringProviderFactory.vb:580-589 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (22 lines × 50) · ×1
  • Duplicated block (22 lines × 50) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb:69 — Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb:69-90 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3.vb:90-111 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4.vb:101-122 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5.vb:112-133 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6.vb:123-144 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7.vb:134-155 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8.vb:145-166 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9.vb:156-177 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10.vb:167-188 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11.vb:178-199 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12.vb:189-210 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13.vb:200-221 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14.vb:211-232 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15.vb:222-243 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16.vb:233-254 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17.vb:244-265 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18.vb:255-276 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:266-287 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb:277-298 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb:288-309 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb:299-320 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb:310-331 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24.vb:321-342 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24T25.vb:332-353 | Source/Source/Yamo/Expressions/SelectSqlExpression.vb:710-731 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2.vb:906-927 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3.vb:984-1005 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4.vb:1084-1105 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5.vb:1202-1223 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6.vb:1320-1341 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7.vb:1158-1179 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8.vb:1215-1236 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9.vb:1293-1314 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10.vb:1371-1392 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11.vb:1449-1470 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12.vb:1527-1548 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13.vb:1605-1626 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14.vb:1683-1704 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15.vb:1761-1782 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16.vb:1839-1860 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17.vb:1917-1938 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18.vb:1995-2016 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:2073-2094 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb:2151-2172 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb:2229-2250 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb:2307-2328 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb:2385-2406 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24.vb:2463-2484 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24T25.vb:2234-2255 | Source/Source/Yamo/Expressions/WithHintsSelectSqlExpression.vb:631-652 — before extracting anything, compare `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb` and `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3.vb` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 128 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (18 lines × 3) · ×1
  • Duplicated block (18 lines × 3) Source/Source/Yamo.CodeGenerator/Generator/FilteredSelectSqlExpressionCodeGenerator.vb:40 — Source/Source/Yamo.CodeGenerator/Generator/FilteredSelectSqlExpressionCodeGenerator.vb:40-57 | Source/Source/Yamo.CodeGenerator/Generator/SelectSqlExpressionCodeGenerator.vb:64-81 | Source/Source/Yamo.CodeGenerator/Generator/WithHintsSelectSqlExpressionCodeGenerator.vb:55-72 — before extracting anything, compare `Source/Source/Yamo.CodeGenerator/Generator/FilteredSelectSqlExpressionCodeGenerator.vb` and `Source/Source/Yamo.CodeGenerator/Generator/SelectSqlExpressionCodeGenerator.vb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 55 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (18–19 lines × 2) · ×1
  • Duplicated block (18–19 lines × 2) Source/Source/Yamo/Infrastructure/EntitySqlStringProviderFactory.vb:394 — Source/Source/Yamo/Infrastructure/EntitySqlStringProviderFactory.vb:394-412 | Source/Source/Yamo/Infrastructure/EntitySqlStringProviderFactory.vb:458-475 — both copies are in the same file, so extract the 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Source/Source/Yamo/Infrastructure/EntitySqlStringProviderFactory.vb:475` calls `GetSetOnDeleteProperties` and `Source/Source/Yamo/Infrastructure/EntitySqlStringProviderFactory.vb:412` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (18 lines × 2) · ×1
  • Duplicated block (18 lines × 2) Source/Source/Yamo/Infrastructure/EntitySqlStringProviderFactory.vb:247 — Source/Source/Yamo/Infrastructure/EntitySqlStringProviderFactory.vb:247-264 | Source/Source/Yamo/Infrastructure/EntitySqlStringProviderFactory.vb:489-506 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (16 lines × 5) · ×1
  • Duplicated block (16 lines × 5) Source/Source/Yamo.CodeGenerator/Generator/FilteredSelectSqlExpressionCodeGenerator.vb:43 — Source/Source/Yamo.CodeGenerator/Generator/FilteredSelectSqlExpressionCodeGenerator.vb:43-58 | Source/Source/Yamo.CodeGenerator/Generator/GroupedSelectSqlExpressionCodeGenerator.vb:38-53 | Source/Source/Yamo.CodeGenerator/Generator/HavingSelectSqlExpressionCodeGenerator.vb:38-53 | Source/Source/Yamo.CodeGenerator/Generator/SelectSqlExpressionCodeGenerator.vb:67-82 | Source/Source/Yamo.CodeGenerator/Generator/WithHintsSelectSqlExpressionCodeGenerator.vb:58-73 — before extracting anything, compare `Source/Source/Yamo.CodeGenerator/Generator/FilteredSelectSqlExpressionCodeGenerator.vb` and `Source/Source/Yamo.CodeGenerator/Generator/GroupedSelectSqlExpressionCodeGenerator.vb` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 61 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (14 lines × 6) · ×1
  • Duplicated block (14 lines × 6) Source/Source/Yamo.CodeGenerator/Generator/FilteredSelectSqlExpressionCodeGenerator.vb:46 — Source/Source/Yamo.CodeGenerator/Generator/FilteredSelectSqlExpressionCodeGenerator.vb:46-59 | Source/Source/Yamo.CodeGenerator/Generator/GroupedSelectSqlExpressionCodeGenerator.vb:41-54 | Source/Source/Yamo.CodeGenerator/Generator/HavingSelectSqlExpressionCodeGenerator.vb:41-54 | Source/Source/Yamo.CodeGenerator/Generator/OrderedSelectSqlExpressionCodeGenerator.vb:37-50 | Source/Source/Yamo.CodeGenerator/Generator/SelectSqlExpressionCodeGenerator.vb:70-83 | Source/Source/Yamo.CodeGenerator/Generator/WithHintsSelectSqlExpressionCodeGenerator.vb:61-74 — before extracting anything, compare `Source/Source/Yamo.CodeGenerator/Generator/FilteredSelectSqlExpressionCodeGenerator.vb` and `Source/Source/Yamo.CodeGenerator/Generator/GroupedSelectSqlExpressionCodeGenerator.vb` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 61 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (15 lines × 3) · ×1
  • Duplicated block (15 lines × 3) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb:99 — Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb:99-113 | Source/Source/Yamo/Expressions/SelectSqlExpression.vb:740-754 | Source/Source/Yamo/Expressions/WithHintsSelectSqlExpression.vb:661-675 — before extracting anything, compare `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb` and `Source/Source/Yamo/Expressions/SelectSqlExpression.vb` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 158 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (12 lines × 3) · ×1
  • Duplicated block (12 lines × 3) Source/Source/Yamo/Expressions/Builders/DeleteSqlExpressionBuilder.vb:211 — Source/Source/Yamo/Expressions/Builders/DeleteSqlExpressionBuilder.vb:211-222 | Source/Source/Yamo/Expressions/Builders/DeleteSqlExpressionBuilder.vb:237-248 | Source/Source/Yamo/Expressions/Builders/UpdateSqlExpressionBuilder.vb:222-233 — 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.
D4 · Code Duplication · Duplicated block (2–14 lines × 4) · ×1
  • Duplicated block (2–14 lines × 4) Source/Source/Yamo/Infrastructure/EntitySqlStringProviderFactory.vb:263 — Source/Source/Yamo/Infrastructure/EntitySqlStringProviderFactory.vb:263-276 | Source/Source/Yamo/Infrastructure/EntitySqlStringProviderFactory.vb:423-436 | Source/Source/Yamo/Infrastructure/EntitySqlStringProviderFactory.vb:505-518 | Source/Source/Yamo/Infrastructure/EntitySqlStringProviderFactory.vb:578-579 — 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.
D4 · Code Duplication · Duplicated block (9 lines × 3) · ×1
  • Duplicated block (9 lines × 3) Source/Source/Yamo/Infrastructure/EntitySqlStringProviderFactory.vb:423 — Source/Source/Yamo/Infrastructure/EntitySqlStringProviderFactory.vb:423-431 | Source/Source/Yamo/Infrastructure/EntitySqlStringProviderFactory.vb:488-496 | Source/Source/Yamo/Infrastructure/EntitySqlStringProviderFactory.vb:505-513 — 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.
D4 · Code Duplication · Duplicated block (13 lines × 13) · ×1
  • Duplicated block (13 lines × 13) Source/Source/Yamo/JoinOfT1T2T3T4T5T6T7T8T9T10T11T12T13.vb:117 — Source/Source/Yamo/JoinOfT1T2T3T4T5T6T7T8T9T10T11T12T13.vb:117-129 | Source/Source/Yamo/JoinOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14.vb:125-137 | Source/Source/Yamo/JoinOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15.vb:133-145 | Source/Source/Yamo/JoinOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16.vb:141-153 | Source/Source/Yamo/JoinOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17.vb:149-161 | Source/Source/Yamo/JoinOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18.vb:157-169 | Source/Source/Yamo/JoinOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:165-177 | Source/Source/Yamo/JoinOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb:173-185 | Source/Source/Yamo/JoinOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb:181-193 | Source/Source/Yamo/JoinOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb:189-201 | Source/Source/Yamo/JoinOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb:197-209 | Source/Source/Yamo/JoinOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24.vb:205-217 | Source/Source/Yamo/JoinOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24T25.vb:213-225 — before extracting anything, compare `Source/Source/Yamo/JoinOfT1T2T3T4T5T6T7T8T9T10T11T12T13.vb` and `Source/Source/Yamo/JoinOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14.vb` as WHOLE FILES: 93% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note what the matched lines are: every one of them assigns one field to another, so the block is a hand-written mapper between two data shapes rather than behaviour with a helper inside it. Extracting one shared function only works if both sites map the SAME pair of types in the same direction — check that first, because inverse or differently-typed mappers have no single function they can both call. Where they do not, the moves that exist are a generated or reflective mapper, a common embedded/base type the fields live on once, or accepting the run and covering it with a test that fails when a field is added to one side only.
D4 · Code Duplication · Duplicated block (9 lines × 5) · ×1
  • Duplicated block (9 lines × 5) Source/Source/Yamo/Infrastructure/EntitySqlStringProviderFactory.vb:246 — Source/Source/Yamo/Infrastructure/EntitySqlStringProviderFactory.vb:246-254 | Source/Source/Yamo/Infrastructure/EntitySqlStringProviderFactory.vb:263-271 | Source/Source/Yamo/Infrastructure/EntitySqlStringProviderFactory.vb:423-431 | Source/Source/Yamo/Infrastructure/EntitySqlStringProviderFactory.vb:488-496 | Source/Source/Yamo/Infrastructure/EntitySqlStringProviderFactory.vb:505-513 — 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.
D4 · Code Duplication · Duplicated block (12 lines × 154) · ×1
  • Duplicated block (12 lines × 154) Source/Source/Yamo/Expressions/CustomDistinctSelectSqlExpression.vb:196 — Source/Source/Yamo/Expressions/CustomDistinctSelectSqlExpression.vb:196-207 | Source/Source/Yamo/Expressions/CustomSelectSqlExpression.vb:205-216 | Source/Source/Yamo/Expressions/CustomSetSelectSqlExpression.vb:196-207 | Source/Source/Yamo/Expressions/DistinctSelectSqlExpression.vb:196-207 | Source/Source/Yamo/Expressions/FilteredSelectSqlExpression.vb:275-286 | Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2.vb:470-481 | Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3.vb:548-559 | Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4.vb:608-619 | Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5.vb:686-697 | Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6.vb:764-775 | Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7.vb:842-853 | Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8.vb:899-910 | Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9.vb:977-988 | Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10.vb:1055-1066 | Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11.vb:1133-1144 | Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12.vb:1211-1222 | Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13.vb:1289-1300 | Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14.vb:1367-1378 | Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15.vb:1445-1456 | Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16.vb:1523-1534 | Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17.vb:1601-1612 | Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18.vb:1679-1690 | Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:1757-1768 | Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb:1835-1846 | Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb:1913-1924 | Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb:1991-2002 | Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb:2069-2080 | Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24.vb:2147-2158 | Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24T25.vb:2225-2236 | Source/Source/Yamo/Expressions/GroupedSelectSqlExpression.vb:251-262 | Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2.vb:416-427 | Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3.vb:484-495 | Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4.vb:534-545 | Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5.vb:602-613 | Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6.vb:670-681 | Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7.vb:738-749 | Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8.vb:795-806 | Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9.vb:863-874 | Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10.vb:931-942 | Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11.vb:999-1010 | Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12.vb:1067-1078 | Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13.vb:1135-1146 | Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14.vb:1203-1214 | Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15.vb:1271-1282 | Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16.vb:1339-1350 | Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17.vb:1407-1418 | Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18.vb:1475-1486 | Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:1543-1554 | Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb:1611-1622 | Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb:1679-1690 | Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb:1747-1758 | Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb:1815-1826 | Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24.vb:1883-1894 | Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24T25.vb:1951-1962 | Source/Source/Yamo/Expressions/HavingSelectSqlExpression.vb:243-254 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2.vb:408-419 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3.vb:476-487 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4.vb:526-537 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5.vb:594-605 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6.vb:662-673 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7.vb:730-741 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8.vb:787-798 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9.vb:855-866 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10.vb:923-934 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11.vb:991-1002 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12.vb:1059-1070 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13.vb:1127-1138 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14.vb:1195-1206 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15.vb:1263-1274 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16.vb:1331-1342 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17.vb:1399-1410 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18.vb:1467-1478 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:1535-1546 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb:1603-1614 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb:1671-1682 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb:1739-1750 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb:1807-1818 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24.vb:1875-1886 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24T25.vb:1943-1954 | Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2.vb:88-99 | Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3.vb:107-118 | Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4.vb:108-119 | Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5.vb:118-129 | Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6.vb:128-139 | Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7.vb:138-149 | Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8.vb:85-96 | Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9.vb:86-97 | Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10.vb:87-98 | Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11.vb:88-99 | Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12.vb:89-100 | Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13.vb:90-101 | Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14.vb:91-102 | Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15.vb:92-103 | Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16.vb:93-104 | Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17.vb:94-105 | Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18.vb:95-106 | Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:96-107 | Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb:97-108 | Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb:98-109 | Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb:99-110 | Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb:100-111 | Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24.vb:101-112 | Source/Source/Yamo/Expressions/JoinSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24T25.vb:102-113 | Source/Source/Yamo/Expressions/OrderedSelectSqlExpression.vb:203-214 | Source/Source/Yamo/Expressions/OrderedSelectSqlExpressionOfT1T2.vb:314-325 | Source/Source/Yamo/Expressions/OrderedSelectSqlExpressionOfT1T2T3.vb:364-375 | Source/Source/Yamo/Expressions/OrderedSelectSqlExpressionOfT1T2T3T4.vb:414-425 | Source/Source/Yamo/Expressions/OrderedSelectSqlExpressionOfT1T2T3T4T5.vb:464-475 | Source/Source/Yamo/Expressions/OrderedSelectSqlExpressionOfT1T2T3T4T5T6.vb:514-525 | Source/Source/Yamo/Expressions/OrderedSelectSqlExpressionOfT1T2T3T4T5T6T7.vb:564-575 | Source/Source/Yamo/Expressions/OrderedSelectSqlExpressionOfT1T2T3T4T5T6T7T8.vb:603-614 | Source/Source/Yamo/Expressions/OrderedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9.vb:653-664 | Source/Source/Yamo/Expressions/OrderedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10.vb:703-714 | Source/Source/Yamo/Expressions/OrderedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11.vb:753-764 | Source/Source/Yamo/Expressions/OrderedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12.vb:803-814 | Source/Source/Yamo/Expressions/OrderedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13.vb:853-864 | Source/Source/Yamo/Expressions/OrderedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14.vb:903-914 | Source/Source/Yamo/Expressions/OrderedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15.vb:953-964 | Source/Source/Yamo/Expressions/OrderedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16.vb:1003-1014 | Source/Source/Yamo/Expressions/OrderedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17.vb:1053-1064 | Source/Source/Yamo/Expressions/OrderedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18.vb:1103-1114 | Source/Source/Yamo/Expressions/OrderedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:1153-1164 | Source/Source/Yamo/Expressions/OrderedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb:1203-1214 | Source/Source/Yamo/Expressions/OrderedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb:1253-1264 | Source/Source/Yamo/Expressions/OrderedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb:1303-1314 | Source/Source/Yamo/Expressions/OrderedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb:1353-1364 | Source/Source/Yamo/Expressions/OrderedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24.vb:1403-1414 | Source/Source/Yamo/Expressions/OrderedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24T25.vb:1453-1464 | Source/Source/Yamo/Expressions/SelectedSelectSqlExpression.vb:273-284 | Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2.vb:380-391 | Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3.vb:469-480 | Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4.vb:582-593 | Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5.vb:719-730 | Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6.vb:880-891 | Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7.vb:1065-1076 | Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8.vb:1274-1285 | Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9.vb:1507-1518 | Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10.vb:1764-1775 | Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11.vb:2045-2056 | Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12.vb:2350-2361 | Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13.vb:2679-2690 | Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14.vb:3032-3043 | Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15.vb:3409-3420 | Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16.vb:3810-3821 | Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17.vb:4235-4246 | Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18.vb:4684-4695 | Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:5157-5168 | Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb:5654-5665 | Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb:6175-6186 | Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb:6720-6731 | Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb:7289-7300 | Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24.vb:7882-7893 | Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24T25.vb:8499-8510 | Source/Source/Yamo/Expressions/SetSelectSqlExpression.vb:196-207 — before extracting anything, compare `Source/Source/Yamo/Expressions/CustomDistinctSelectSqlExpression.vb` and `Source/Source/Yamo/Expressions/CustomSelectSqlExpression.vb` as WHOLE FILES: 97% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (12 lines × 14) · ×1
  • Duplicated block (12 lines × 14) Source/Source/Yamo/JoinOfT1T2T3T4T5T6T7T8T9T10T11T12.vb:109 — Source/Source/Yamo/JoinOfT1T2T3T4T5T6T7T8T9T10T11T12.vb:109-120 | Source/Source/Yamo/JoinOfT1T2T3T4T5T6T7T8T9T10T11T12T13.vb:117-128 | Source/Source/Yamo/JoinOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14.vb:125-136 | Source/Source/Yamo/JoinOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15.vb:133-144 | Source/Source/Yamo/JoinOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16.vb:141-152 | Source/Source/Yamo/JoinOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17.vb:149-160 | Source/Source/Yamo/JoinOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18.vb:157-168 | Source/Source/Yamo/JoinOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:165-176 | Source/Source/Yamo/JoinOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb:173-184 | Source/Source/Yamo/JoinOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb:181-192 | Source/Source/Yamo/JoinOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb:189-200 | Source/Source/Yamo/JoinOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb:197-208 | Source/Source/Yamo/JoinOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24.vb:205-216 | Source/Source/Yamo/JoinOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24T25.vb:213-224 — before extracting anything, compare `Source/Source/Yamo/JoinOfT1T2T3T4T5T6T7T8T9T10T11T12.vb` and `Source/Source/Yamo/JoinOfT1T2T3T4T5T6T7T8T9T10T11T12T13.vb` as WHOLE FILES: 92% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note what the matched lines are: every one of them assigns one field to another, so the block is a hand-written mapper between two data shapes rather than behaviour with a helper inside it. Extracting one shared function only works if both sites map the SAME pair of types in the same direction — check that first, because inverse or differently-typed mappers have no single function they can both call. Where they do not, the moves that exist are a generated or reflective mapper, a common embedded/base type the fields live on once, or accepting the run and covering it with a test that fails when a field is added to one side only.
D4 · Code Duplication · Duplicated block (9 lines × 6) · ×1
  • Duplicated block (9 lines × 6) Source/Source/Yamo/Infrastructure/EntitySqlStringProviderFactory.vb:246 — Source/Source/Yamo/Infrastructure/EntitySqlStringProviderFactory.vb:246-254 | Source/Source/Yamo/Infrastructure/EntitySqlStringProviderFactory.vb:263-271 | Source/Source/Yamo/Infrastructure/EntitySqlStringProviderFactory.vb:364-372 | Source/Source/Yamo/Infrastructure/EntitySqlStringProviderFactory.vb:423-431 | Source/Source/Yamo/Infrastructure/EntitySqlStringProviderFactory.vb:488-496 | Source/Source/Yamo/Infrastructure/EntitySqlStringProviderFactory.vb:505-513 — 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.
D4 · Code Duplication · Duplicated block (10 lines × 4) · ×1
  • Duplicated block (10 lines × 4) Source/Source/Yamo/Infrastructure/EntitySqlStringProviderFactory.vb:32 — Source/Source/Yamo/Infrastructure/EntitySqlStringProviderFactory.vb:32-41 | Source/Source/Yamo/Infrastructure/EntitySqlStringProviderFactory.vb:220-229 | Source/Source/Yamo/Infrastructure/EntitySqlStringProviderFactory.vb:398-407 | Source/Source/Yamo/Infrastructure/EntitySqlStringProviderFactory.vb:462-471 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Source/Source/Yamo/Infrastructure/EntitySqlStringProviderFactory.vb:233` calls `GetNonKeyProperties` and `Source/Source/Yamo/Infrastructure/EntitySqlStringProviderFactory.vb:412` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (2–12 lines × 55) · ×1
  • Duplicated block (2–12 lines × 55) Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24T25.vb:2245 — Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24T25.vb:2245-2256 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7.vb:302-304 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8.vb:306-308 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9.vb:310-312 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10.vb:314-316 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11.vb:318-320 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12.vb:322-324 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13.vb:326-328 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14.vb:330-332 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15.vb:334-336 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16.vb:329-330 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16.vb:338-340 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17.vb:334-335 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17.vb:342-344 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18.vb:339-340 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18.vb:346-348 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:344-345 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:350-352 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb:349-350 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb:354-356 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb:354-355 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb:358-360 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb:359-360 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb:362-364 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb:364-365 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb:366-368 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24.vb:369-370 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24T25.vb:374-376 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7.vb:1325-1327 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8.vb:1375-1377 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9.vb:1446-1448 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10.vb:1517-1519 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11.vb:1588-1590 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12.vb:1659-1661 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13.vb:1730-1732 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14.vb:1801-1803 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15.vb:1872-1874 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16.vb:1934-1935 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16.vb:1943-1945 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17.vb:2006-2007 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17.vb:2014-2016 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18.vb:2078-2079 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18.vb:2085-2087 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:2150-2151 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:2156-2158 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb:2222-2223 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb:2227-2229 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb:2294-2295 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb:2298-2300 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb:2366-2367 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb:2369-2371 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb:2438-2439 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb:2440-2442 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24.vb:2510-2511 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24T25.vb:2264-2275 — before extracting anything, compare `Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24T25.vb` and `Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb` as WHOLE FILES: 83% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24T25.vb:2256` calls `GetType`, `GroupedSelectSqlExpression`, `HavingSelectSqlExpression` and `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24T25.vb:376` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (3–12 lines × 4) · ×1
  • Duplicated block (3–12 lines × 4) Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18.vb:1711 — Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18.vb:1711-1713 | Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18.vb:1495-1506 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18.vb:1487-1498 | Source/Source/Yamo/Expressions/OrderedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18.vb:1133-1136 — before extracting anything, compare `Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18.vb` and `Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18.vb` as WHOLE FILES: 84% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18.vb:1506` calls `GetType`, `OrderedSelectSqlExpression` and `Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18.vb:1713` does not — after which the two agree again for 5 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (2–12 lines × 5) · ×1
  • Duplicated block (2–12 lines × 5) Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb:2024 — Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb:2024-2027 | Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb:1767-1778 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb:1759-1770 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb:367-368 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb:2374-2375 — before extracting anything, compare `Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb` and `Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb` as WHOLE FILES: 84% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb:1778` calls `GetType`, `OrderedSelectSqlExpression`, `LimitedSelectSqlExpression` and `Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb:2027` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (2–12 lines × 49) · ×1
  • Duplicated block (2–12 lines × 49) Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb:2102 — Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb:2102-2105 | Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb:1835-1846 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb:1827-1838 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb:318-319 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3.vb:330-331 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4.vb:332-333 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5.vb:334-335 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6.vb:336-337 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7.vb:338-339 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8.vb:340-341 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9.vb:342-343 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10.vb:344-345 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11.vb:346-347 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12.vb:348-349 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13.vb:350-351 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14.vb:352-353 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15.vb:354-355 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16.vb:356-357 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17.vb:358-359 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18.vb:360-361 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:362-363 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb:364-365 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb:366-367 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb:368-369 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb:370-371 | Source/Source/Yamo/Expressions/SelectSqlExpression.vb:968-969 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2.vb:1154-1155 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3.vb:1223-1224 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4.vb:1314-1315 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5.vb:1423-1424 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6.vb:1532-1533 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7.vb:1361-1362 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8.vb:1409-1410 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9.vb:1478-1479 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10.vb:1547-1548 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11.vb:1616-1617 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12.vb:1685-1686 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13.vb:1754-1755 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14.vb:1823-1824 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15.vb:1892-1893 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16.vb:1961-1962 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17.vb:2030-2031 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18.vb:2099-2100 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:2168-2169 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb:2237-2238 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb:2306-2307 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb:2375-2376 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb:2444-2445 | Source/Source/Yamo/Expressions/WithHintsSelectSqlExpression.vb:888-889 — before extracting anything, compare `Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb` and `Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb` as WHOLE FILES: 84% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb:1846` calls `GetType`, `OrderedSelectSqlExpression`, `LimitedSelectSqlExpression` and `Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb:2105` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (2–12 lines × 51) · ×1
  • Duplicated block (2–12 lines × 51) Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24.vb:2180 — Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24.vb:2180-2183 | Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24.vb:1903-1914 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24.vb:1895-1906 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb:319-320 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3.vb:331-332 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4.vb:333-334 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5.vb:335-336 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6.vb:337-338 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7.vb:339-340 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8.vb:341-342 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9.vb:343-344 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10.vb:345-346 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11.vb:347-348 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12.vb:349-350 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13.vb:351-352 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14.vb:353-354 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15.vb:355-356 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16.vb:357-358 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17.vb:359-360 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18.vb:361-362 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:363-364 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb:365-366 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb:367-368 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb:369-370 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb:371-372 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24.vb:373-374 | Source/Source/Yamo/Expressions/SelectSqlExpression.vb:969-970 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2.vb:1155-1156 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3.vb:1224-1225 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4.vb:1315-1316 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5.vb:1424-1425 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6.vb:1533-1534 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7.vb:1362-1363 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8.vb:1410-1411 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9.vb:1479-1480 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10.vb:1548-1549 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11.vb:1617-1618 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12.vb:1686-1687 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13.vb:1755-1756 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14.vb:1824-1825 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15.vb:1893-1894 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16.vb:1962-1963 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17.vb:2031-2032 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18.vb:2100-2101 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:2169-2170 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb:2238-2239 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb:2307-2308 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb:2376-2377 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb:2445-2446 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24.vb:2514-2515 | Source/Source/Yamo/Expressions/WithHintsSelectSqlExpression.vb:889-890 — before extracting anything, compare `Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24.vb` and `Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24.vb` as WHOLE FILES: 84% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24.vb:1914` calls `GetType`, `OrderedSelectSqlExpression`, `LimitedSelectSqlExpression` and `Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24.vb:2183` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (2–12 lines × 69) · ×1
  • Duplicated block (2–12 lines × 69) Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24T25.vb:2258 — Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24T25.vb:2258-2261 | Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24T25.vb:1971-1982 | Source/Source/Yamo/Expressions/HavingSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24T25.vb:1963-1974 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb:320-323 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3.vb:332-335 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4.vb:334-337 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5.vb:336-339 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6.vb:338-341 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7.vb:340-343 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8.vb:342-345 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9.vb:344-347 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10.vb:346-349 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11.vb:348-351 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12.vb:350-353 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13.vb:352-355 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14.vb:354-357 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15.vb:356-359 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16.vb:349-350 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16.vb:358-361 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17.vb:352-353 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17.vb:360-363 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18.vb:355-356 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18.vb:362-365 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:358-359 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:364-367 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb:361-362 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb:366-369 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb:364-365 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb:368-371 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb:367-368 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb:370-373 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb:370-371 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb:372-375 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24.vb:373-374 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24T25.vb:376-379 | Source/Source/Yamo/Expressions/SelectSqlExpression.vb:970-973 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2.vb:1156-1159 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3.vb:1225-1228 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4.vb:1316-1319 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5.vb:1425-1428 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6.vb:1534-1537 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7.vb:1363-1366 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8.vb:1411-1414 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9.vb:1480-1483 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10.vb:1549-1552 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11.vb:1618-1621 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12.vb:1687-1690 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13.vb:1756-1759 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14.vb:1825-1828 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15.vb:1894-1897 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16.vb:1954-1955 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16.vb:1963-1966 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17.vb:2024-2025 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17.vb:2032-2035 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18.vb:2094-2095 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18.vb:2101-2104 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:2164-2165 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:2170-2173 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb:2234-2235 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb:2239-2242 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb:2304-2305 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb:2308-2311 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb:2374-2375 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb:2377-2380 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb:2444-2445 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb:2446-2449 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24.vb:2514-2515 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24T25.vb:2277-2280 | Source/Source/Yamo/Expressions/WithHintsSelectSqlExpression.vb:890-893 — before extracting anything, compare `Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24T25.vb` and `Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24T25.vb` as WHOLE FILES: 84% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Source/Source/Yamo/Expressions/GroupedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24T25.vb:1982` calls `GetType`, `OrderedSelectSqlExpression`, `LimitedSelectSqlExpression` and `Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24T25.vb:2261` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (2–12 lines × 19) · ×1
  • Duplicated block (2–12 lines × 19) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15.vb:272 — Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15.vb:272-273 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16.vb:282-283 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17.vb:292-293 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18.vb:302-303 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:312-313 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb:322-323 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb:332-333 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb:342-343 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb:352-353 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24.vb:351-362 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15.vb:1810-1811 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16.vb:1887-1888 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17.vb:1964-1965 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18.vb:2041-2042 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:2118-2119 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb:2195-2196 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb:2272-2273 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb:2349-2350 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb:2415-2426 — before extracting anything, compare `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15.vb` and `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16.vb` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 102 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15.vb:273` calls `GetType`, `JoinSelectSqlExpression` and `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16.vb:283` does not — after which the two agree again for 5 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (9 lines × 8) · ×1
  • Duplicated block (9 lines × 8) Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:1777 — Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:1777-1785 | Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb:1855-1863 | Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb:1933-1941 | Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb:2011-2019 | Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb:2089-2097 | Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24.vb:2167-2175 | Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24T25.vb:2245-2253 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24T25.vb:2264-2272 — before extracting anything, compare `Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb` and `Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb` as WHOLE FILES: 88% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (8 lines × 6) · ×1
  • Duplicated block (8 lines × 6) Source/Source/Yamo/Infrastructure/EntitySqlStringProviderFactory.vb:247 — Source/Source/Yamo/Infrastructure/EntitySqlStringProviderFactory.vb:247-254 | Source/Source/Yamo/Infrastructure/EntitySqlStringProviderFactory.vb:264-271 | Source/Source/Yamo/Infrastructure/EntitySqlStringProviderFactory.vb:424-431 | Source/Source/Yamo/Infrastructure/EntitySqlStringProviderFactory.vb:489-496 | Source/Source/Yamo/Infrastructure/EntitySqlStringProviderFactory.vb:506-513 | Source/Source/Yamo/Infrastructure/EntitySqlStringProviderFactory.vb:567-574 — 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.
D4 · Code Duplication · Duplicated block (11 lines × 6) · ×1
  • Duplicated block (11 lines × 6) Source/Source/Yamo.CodeGenerator/Generator/CustomDistinctSelectSqlExpressionCodeGenerator.vb:25 — Source/Source/Yamo.CodeGenerator/Generator/CustomDistinctSelectSqlExpressionCodeGenerator.vb:25-35 | Source/Source/Yamo.CodeGenerator/Generator/CustomSelectSqlExpressionCodeGenerator.vb:28-38 | Source/Source/Yamo.CodeGenerator/Generator/CustomSetSelectSqlExpressionCodeGenerator.vb:27-37 | Source/Source/Yamo.CodeGenerator/Generator/DistinctSelectSqlExpressionCodeGenerator.vb:25-35 | Source/Source/Yamo.CodeGenerator/Generator/SelectedSelectSqlExpressionCodeGenerator.vb:29-39 | Source/Source/Yamo.CodeGenerator/Generator/SetSelectSqlExpressionCodeGenerator.vb:27-37 — before extracting anything, compare `Source/Source/Yamo.CodeGenerator/Generator/CustomDistinctSelectSqlExpressionCodeGenerator.vb` and `Source/Source/Yamo.CodeGenerator/Generator/CustomSelectSqlExpressionCodeGenerator.vb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 46 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Source/Source/Yamo.CodeGenerator/Generator/CustomSelectSqlExpressionCodeGenerator.vb:40` calls `GenerateCustomDistinct`, `AppendLine` and `Source/Source/Yamo.CodeGenerator/Generator/CustomDistinctSelectSqlExpressionCodeGenerator.vb:37` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (8 lines × 8) · ×1
  • Duplicated block (8 lines × 8) Source/Source/Yamo.CodeGenerator/Generator/CustomDistinctSelectSqlExpressionCodeGenerator.vb:15 — Source/Source/Yamo.CodeGenerator/Generator/CustomDistinctSelectSqlExpressionCodeGenerator.vb:15-22 | Source/Source/Yamo.CodeGenerator/Generator/CustomSelectSqlExpressionCodeGenerator.vb:18-25 | Source/Source/Yamo.CodeGenerator/Generator/CustomSetSelectSqlExpressionCodeGenerator.vb:17-24 | Source/Source/Yamo.CodeGenerator/Generator/DistinctSelectSqlExpressionCodeGenerator.vb:15-22 | Source/Source/Yamo.CodeGenerator/Generator/SelectSqlExpressionCodeGenerator.vb:26-33 | Source/Source/Yamo.CodeGenerator/Generator/SelectedSelectSqlExpressionCodeGenerator.vb:19-26 | Source/Source/Yamo.CodeGenerator/Generator/SetSelectSqlExpressionCodeGenerator.vb:17-24 | Source/Source/Yamo.CodeGenerator/Generator/WithHintsSelectSqlExpressionCodeGenerator.vb:25-32 — before extracting anything, compare `Source/Source/Yamo.CodeGenerator/Generator/CustomDistinctSelectSqlExpressionCodeGenerator.vb` and `Source/Source/Yamo.CodeGenerator/Generator/CustomSelectSqlExpressionCodeGenerator.vb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 46 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (9–10 lines × 4) · ×1
  • Duplicated block (9–10 lines × 4) Source/Source/Yamo/Infrastructure/EntitySqlStringProviderFactory.vb:225 — Source/Source/Yamo/Infrastructure/EntitySqlStringProviderFactory.vb:225-233 | Source/Source/Yamo/Infrastructure/EntitySqlStringProviderFactory.vb:317-325 | Source/Source/Yamo/Infrastructure/EntitySqlStringProviderFactory.vb:403-412 | Source/Source/Yamo/Infrastructure/EntitySqlStringProviderFactory.vb:467-475 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Source/Source/Yamo/Infrastructure/EntitySqlStringProviderFactory.vb:233` calls `GetNonKeyProperties` and `Source/Source/Yamo/Infrastructure/EntitySqlStringProviderFactory.vb:412` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (7 lines × 4) · ×1
  • Duplicated block (7 lines × 4) Source/Source/Yamo/Infrastructure/EntitySqlStringProviderFactory.vb:225 — Source/Source/Yamo/Infrastructure/EntitySqlStringProviderFactory.vb:225-231 | Source/Source/Yamo/Infrastructure/EntitySqlStringProviderFactory.vb:403-409 | Source/Source/Yamo/Infrastructure/EntitySqlStringProviderFactory.vb:467-473 | Source/Source/Yamo/Infrastructure/EntitySqlStringProviderFactory.vb:546-552 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Source/Source/Yamo/Infrastructure/EntitySqlStringProviderFactory.vb:233` calls `GetNonKeyProperties` and `Source/Source/Yamo/Infrastructure/EntitySqlStringProviderFactory.vb:412` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (7 lines × 8) · ×1
  • Duplicated block (7 lines × 8) Source/Source/Yamo.CodeGenerator/Generator/FilteredSelectSqlExpressionCodeGenerator.vb:21 — Source/Source/Yamo.CodeGenerator/Generator/FilteredSelectSqlExpressionCodeGenerator.vb:21-27 | Source/Source/Yamo.CodeGenerator/Generator/GroupedSelectSqlExpressionCodeGenerator.vb:19-25 | Source/Source/Yamo.CodeGenerator/Generator/HavingSelectSqlExpressionCodeGenerator.vb:19-25 | Source/Source/Yamo.CodeGenerator/Generator/JoinSelectSqlExpressionCodeGenerator.vb:17-23 | Source/Source/Yamo.CodeGenerator/Generator/JoinWithHintsSelectSqlExpressionCodeGenerator.vb:15-21 | Source/Source/Yamo.CodeGenerator/Generator/JoinedSelectSqlExpressionCodeGenerator.vb:25-31 | Source/Source/Yamo.CodeGenerator/Generator/LimitedSelectSqlExpressionCodeGenerator.vb:15-21 | Source/Source/Yamo.CodeGenerator/Generator/OrderedSelectSqlExpressionCodeGenerator.vb:18-24 — before extracting anything, compare `Source/Source/Yamo.CodeGenerator/Generator/FilteredSelectSqlExpressionCodeGenerator.vb` and `Source/Source/Yamo.CodeGenerator/Generator/GroupedSelectSqlExpressionCodeGenerator.vb` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 61 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (6 lines × 4) · ×1
  • Duplicated block (6 lines × 4) Source/Source/Yamo/Infrastructure/SqlResultReaderFactory.vb:183 — Source/Source/Yamo/Infrastructure/SqlResultReaderFactory.vb:183-188 | Source/Source/Yamo/Infrastructure/SqlResultReaderFactory.vb:222-227 | Source/Source/Yamo/Infrastructure/SqlResultReaderFactory.vb:262-267 | Source/Source/Yamo/Infrastructure/SqlResultReaderFactory.vb:291-296 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
D4 · Code Duplication · Duplicated block (8 lines × 7) · ×1
  • Duplicated block (8 lines × 7) Source/Source/Yamo.CodeGenerator/Generator/FilteredSelectSqlExpressionCodeGenerator.vb:30 — Source/Source/Yamo.CodeGenerator/Generator/FilteredSelectSqlExpressionCodeGenerator.vb:30-37 | Source/Source/Yamo.CodeGenerator/Generator/GroupedSelectSqlExpressionCodeGenerator.vb:28-35 | Source/Source/Yamo.CodeGenerator/Generator/HavingSelectSqlExpressionCodeGenerator.vb:28-35 | Source/Source/Yamo.CodeGenerator/Generator/JoinSelectSqlExpressionCodeGenerator.vb:26-33 | Source/Source/Yamo.CodeGenerator/Generator/JoinWithHintsSelectSqlExpressionCodeGenerator.vb:24-31 | Source/Source/Yamo.CodeGenerator/Generator/LimitedSelectSqlExpressionCodeGenerator.vb:24-31 | Source/Source/Yamo.CodeGenerator/Generator/OrderedSelectSqlExpressionCodeGenerator.vb:27-34 — before extracting anything, compare `Source/Source/Yamo.CodeGenerator/Generator/FilteredSelectSqlExpressionCodeGenerator.vb` and `Source/Source/Yamo.CodeGenerator/Generator/GroupedSelectSqlExpressionCodeGenerator.vb` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 61 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Source/Source/Yamo.CodeGenerator/Generator/JoinSelectSqlExpressionCodeGenerator.vb:35` calls `GenerateWithHints`, `AppendLine` and `Source/Source/Yamo.CodeGenerator/Generator/JoinWithHintsSelectSqlExpressionCodeGenerator.vb:33` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (7 lines × 16) · ×1
  • Duplicated block (7 lines × 16) Source/Source/Yamo.CodeGenerator/Generator/CustomDistinctSelectSqlExpressionCodeGenerator.vb:58 — Source/Source/Yamo.CodeGenerator/Generator/CustomDistinctSelectSqlExpressionCodeGenerator.vb:58-64 | Source/Source/Yamo.CodeGenerator/Generator/CustomSelectSqlExpressionCodeGenerator.vb:64-70 | Source/Source/Yamo.CodeGenerator/Generator/CustomSetSelectSqlExpressionCodeGenerator.vb:60-66 | Source/Source/Yamo.CodeGenerator/Generator/DistinctSelectSqlExpressionCodeGenerator.vb:58-64 | Source/Source/Yamo.CodeGenerator/Generator/FilteredSelectSqlExpressionCodeGenerator.vb:65-71 | Source/Source/Yamo.CodeGenerator/Generator/GroupedSelectSqlExpressionCodeGenerator.vb:60-66 | Source/Source/Yamo.CodeGenerator/Generator/HavingSelectSqlExpressionCodeGenerator.vb:60-66 | Source/Source/Yamo.CodeGenerator/Generator/JoinSelectSqlExpressionCodeGenerator.vb:52-58 | Source/Source/Yamo.CodeGenerator/Generator/JoinWithHintsSelectSqlExpressionCodeGenerator.vb:47-53 | Source/Source/Yamo.CodeGenerator/Generator/JoinedSelectSqlExpressionCodeGenerator.vb:57-63 | Source/Source/Yamo.CodeGenerator/Generator/LimitedSelectSqlExpressionCodeGenerator.vb:45-51 | Source/Source/Yamo.CodeGenerator/Generator/OrderedSelectSqlExpressionCodeGenerator.vb:56-62 | Source/Source/Yamo.CodeGenerator/Generator/SelectSqlExpressionCodeGenerator.vb:172-178 | Source/Source/Yamo.CodeGenerator/Generator/SelectedSelectSqlExpressionCodeGenerator.vb:71-77 | Source/Source/Yamo.CodeGenerator/Generator/SetSelectSqlExpressionCodeGenerator.vb:60-66 | Source/Source/Yamo.CodeGenerator/Generator/WithHintsSelectSqlExpressionCodeGenerator.vb:79-85 — before extracting anything, compare `Source/Source/Yamo.CodeGenerator/Generator/CustomDistinctSelectSqlExpressionCodeGenerator.vb` and `Source/Source/Yamo.CodeGenerator/Generator/CustomSelectSqlExpressionCodeGenerator.vb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 46 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Source/Source/Yamo.CodeGenerator/Generator/FilteredSelectSqlExpressionCodeGenerator.vb:63` calls `Join`, `GetGenericNames` and `Source/Source/Yamo.CodeGenerator/Generator/CustomDistinctSelectSqlExpressionCodeGenerator.vb:57` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (4–5 lines × 18) · ×1
  • Duplicated block (4–5 lines × 18) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb:135 — Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb:135-139 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3.vb:154-158 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4.vb:163-167 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5.vb:172-176 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6.vb:184-187 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7.vb:193-196 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8.vb:202-205 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9.vb:212-215 | Source/Source/Yamo/Expressions/SelectSqlExpression.vb:778-782 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2.vb:971-975 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3.vb:1047-1051 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4.vb:1145-1149 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5.vb:1261-1265 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6.vb:1380-1383 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7.vb:1216-1219 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8.vb:1271-1274 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9.vb:1348-1351 | Source/Source/Yamo/Expressions/WithHintsSelectSqlExpression.vb:698-702 — before extracting anything, compare `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb` and `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3.vb` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 128 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb:133` calls `GetType`, `JoinSelectSqlExpression` and `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3.vb:152` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (3–5 lines × 52) · ×1
  • Duplicated block (3–5 lines × 52) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb:158 — Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb:158-162 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3.vb:173-175 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3.vb:176-180 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4.vb:184-188 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5.vb:192-196 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6.vb:200-202 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6.vb:203-206 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7.vb:209-211 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7.vb:212-215 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8.vb:218-220 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9.vb:227-229 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10.vb:236-238 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11.vb:245-247 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12.vb:254-256 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13.vb:263-265 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14.vb:272-274 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15.vb:281-283 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16.vb:290-292 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17.vb:299-301 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18.vb:308-310 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:317-319 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb:326-328 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb:335-337 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb:344-346 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb:353-355 | Source/Source/Yamo/Expressions/SelectSqlExpression.vb:802-806 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2.vb:994-998 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3.vb:1066-1068 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3.vb:1069-1073 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4.vb:1166-1170 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5.vb:1281-1285 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6.vb:1396-1398 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6.vb:1399-1402 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7.vb:1232-1234 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7.vb:1235-1238 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8.vb:1287-1289 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9.vb:1363-1365 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10.vb:1439-1441 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11.vb:1515-1517 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12.vb:1591-1593 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13.vb:1667-1669 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14.vb:1743-1745 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15.vb:1819-1821 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16.vb:1895-1897 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17.vb:1971-1973 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18.vb:2047-2049 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:2123-2125 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb:2199-2201 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb:2275-2277 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb:2351-2353 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb:2427-2429 | Source/Source/Yamo/Expressions/WithHintsSelectSqlExpression.vb:722-726 — before extracting anything, compare `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb` and `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3.vb` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 128 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb:156` calls `GetType`, `JoinWithHintsSelectSqlExpression` and `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3.vb:174` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (3–5 lines × 53) · ×1
  • Duplicated block (3–5 lines × 53) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb:181 — Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb:181-185 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3.vb:195-197 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3.vb:198-202 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4.vb:205-209 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5.vb:212-216 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6.vb:219-221 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6.vb:222-225 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7.vb:227-229 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7.vb:230-233 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8.vb:235-237 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9.vb:243-245 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10.vb:251-253 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11.vb:259-261 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12.vb:267-269 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13.vb:275-277 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14.vb:283-285 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15.vb:291-293 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16.vb:299-301 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17.vb:307-309 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18.vb:315-317 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:323-325 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb:331-333 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb:339-341 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb:347-349 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb:355-357 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24.vb:363-365 | Source/Source/Yamo/Expressions/SelectSqlExpression.vb:826-830 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2.vb:1017-1021 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3.vb:1088-1090 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3.vb:1091-1095 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4.vb:1187-1191 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5.vb:1301-1305 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6.vb:1415-1417 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6.vb:1418-1421 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7.vb:1250-1252 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7.vb:1253-1256 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8.vb:1304-1306 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9.vb:1379-1381 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10.vb:1454-1456 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11.vb:1529-1531 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12.vb:1604-1606 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13.vb:1679-1681 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14.vb:1754-1756 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15.vb:1829-1831 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16.vb:1904-1906 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17.vb:1979-1981 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18.vb:2054-2056 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:2129-2131 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb:2204-2206 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb:2279-2281 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb:2354-2356 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb:2429-2431 | Source/Source/Yamo/Expressions/WithHintsSelectSqlExpression.vb:746-750 — before extracting anything, compare `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb` and `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3.vb` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 128 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb:179` calls `GetType`, `JoinedSelectSqlExpression` and `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3.vb:196` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (5 lines × 9) · ×1
  • Duplicated block (5 lines × 9) Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb:112 — Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb:112-116 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3.vb:132-136 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4.vb:142-146 | Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4T5.vb:152-156 | Source/Source/Yamo/Expressions/SelectSqlExpression.vb:753-757 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2.vb:948-952 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3.vb:1025-1029 | Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4.vb:1124-1128 | Source/Source/Yamo/Expressions/WithHintsSelectSqlExpression.vb:674-678 — before extracting anything, compare `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb` and `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3.vb` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 128 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb:109` calls `GetType`, `SelectSqlExpression` and `Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3.vb:128` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Edited copy of a member (18 corresponding lines) · ×1
  • Edited copy of a member (18 corresponding lines) Source/Samples/Yamo.Playground.CS/MyContext.cs:66 — Source/Samples/Yamo.Playground.CS/MyContext.cs:66-83 | Source/Samples/Yamo.Playground.CS/MyContext.cs:203-220 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 30+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 30+ corresponding lines) Source/Samples/Yamo.Playground.CS/Program.cs:1124 — Source/Samples/Yamo.Playground.CS/Program.cs:1124-1155 | Source/Samples/Yamo.Playground.CS/Program.cs:1158-1187 | Source/Samples/Yamo.Playground.CS/Program.cs:1190-1230 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 30 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 15+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 15+ corresponding lines) Source/Samples/Yamo.Playground.CS/Program.cs:407 — Source/Samples/Yamo.Playground.CS/Program.cs:407-422 | Source/Samples/Yamo.Playground.CS/Program.cs:425-439 | Source/Samples/Yamo.Playground.CS/Program.cs:442-457 | Source/Samples/Yamo.Playground.CS/Program.cs:1103-1121 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (14 corresponding lines) · ×1
  • Edited copy of a member (14 corresponding lines) Source/Samples/Yamo.Playground.CS/Program.cs:1233 — Source/Samples/Yamo.Playground.CS/Program.cs:1233-1246 | Source/Samples/Yamo.Playground.CS/Program.cs:1266-1282 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (23–34 lines × 2) · ×1
  • Duplicated block (23–34 lines × 2) Source/Samples/Yamo.Playground.CS/Program.cs:1158 — Source/Samples/Yamo.Playground.CS/Program.cs:1158-1180 | Source/Samples/Yamo.Playground.CS/Program.cs:1190-1223 — both copies are in the same file, so extract the 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 `Source/Samples/Yamo.Playground.CS/Program.cs:1158` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (11–12 lines × 2) · ×1
  • Duplicated block (11–12 lines × 2) Source/Samples/Yamo.Playground.CS/MyContext.cs:43 — Source/Samples/Yamo.Playground.CS/MyContext.cs:43-53 | Source/Samples/Yamo.Playground.CS/MyContext.cs:171-182 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D5 · Coupling · Off the main sequence · ×1
  • Off the main sequence: Yamo(netstandard2.0) Source/Source/Yamo/Yamo.vbproj:1 — Yamo(netstandard2.0): abstractness 0.05, instability 0.00, distance 0.95 — zone of pain — concrete and depended on by 2 project(s), so it's rigid to change.
D8 · Code Coverage · No test project references Yamo.CodeGenerator · ×1
  • No test project references Yamo.CodeGenerator Source/Source/Yamo.CodeGenerator/Yamo.CodeGenerator.vbproj — No test project in this repository references Yamo.CodeGenerator (45 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 1.5% above rather than counted at zero. This is the whole assembly, not a gap within one: add a test project that references it (or a ProjectReference from an existing suite) and its coverage starts being measured.
D8 · Code Coverage · CRAP 50850 · ×1
  • CRAP 50850: SelectSqlExpression.CanCreateResultForCondition Source/Source/Yamo/Expressions/SelectSqlExpression.vb:739 — Cyclomatic 225 with 0.0% file coverage — too complex for how untested it is (CRAP = CC²·(1−cov)³ + CC; ≥30 needs tests or simplification).
D8 · Code Coverage · CRAP 50400 · ×1
  • CRAP 50400: WithHintsSelectSqlExpression.CanCreateResultForCondition Source/Source/Yamo/Expressions/WithHintsSelectSqlExpression.vb:660 — Cyclomatic 224 with 0.0% file coverage — too complex for how untested it is (CRAP = CC²·(1−cov)³ + CC; ≥30 needs tests or simplification).
D8 · Code Coverage · CRAP 46872 · ×1
  • CRAP 46872: JoinedSelectSqlExpression.CanCreateResultForCondition Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2.vb:98 — Cyclomatic 216 with 0.0% file coverage — too complex for how untested it is (CRAP = CC²·(1−cov)³ + CC; ≥30 needs tests or simplification).
D8 · Code Coverage · CRAP 46440 · ×1
  • CRAP 46440: SelectSqlExpression.CanCreateResultForCondition Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2.vb:935 — Cyclomatic 215 with 0.0% file coverage — too complex for how untested it is (CRAP = CC²·(1−cov)³ + CC; ≥30 needs tests or simplification).
D8 · Code Coverage · CRAP 43056 · ×1
  • CRAP 43056: JoinedSelectSqlExpression.CanCreateResultForCondition Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3.vb:119 — Cyclomatic 207 with 0.0% file coverage — too complex for how untested it is (CRAP = CC²·(1−cov)³ + CC; ≥30 needs tests or simplification).
D8 · Code Coverage · CRAP 42642 · ×1
  • CRAP 42642: SelectSqlExpression.CanCreateResultForCondition Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3.vb:1013 — Cyclomatic 206 with 0.0% file coverage — too complex for how untested it is (CRAP = CC²·(1−cov)³ + CC; ≥30 needs tests or simplification).
D8 · Code Coverage · CRAP 39402 · ×1
  • CRAP 39402: JoinedSelectSqlExpression.CanCreateResultForCondition Source/Source/Yamo/Expressions/JoinedSelectSqlExpressionOfT1T2T3T4.vb:130 — Cyclomatic 198 with 0.0% file coverage — too complex for how untested it is (CRAP = CC²·(1−cov)³ + CC; ≥30 needs tests or simplification).
D8 · Code Coverage · CRAP 39006 · ×1
  • CRAP 39006: SelectSqlExpression.CanCreateResultForCondition Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4.vb:1113 — Cyclomatic 197 with 0.0% file coverage — too complex for how untested it is (CRAP = CC²·(1−cov)³ + CC; ≥30 needs tests or simplification).
P1 · CI/CD gates · No CI pipeline · ×1
  • No CI pipeline — No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.
SC1 · Supply-chain hygiene · NuGet dependencies are not locked · ×1
  • NuGet dependencies are not locked — No packages.lock.json and no central package management — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
Minor — 387 finding(s)
D34 · Knowledge Freshness · Orphaned file · ×369
  • Orphaned file Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18.vb:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17.vb:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16.vb:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15.vb:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14.vb:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13.vb:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12.vb:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24.vb:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22.vb:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11.vb:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21.vb:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24T25.vb:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24T25.vb:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20.vb:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24.vb:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19.vb:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file Source/Source/Yamo/Expressions/FilteredSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18.vb:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10.vb:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file Source/Source/Yamo/Expressions/SelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17.vb:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • + 344 more in this group — see findings.md.
D34 · Knowledge Freshness · Most significant orphaned file · ×3
  • Most significant orphaned file Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24T25.vb:1 — One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
  • Most significant orphaned file Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23T24.vb:1 — One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
  • Most significant orphaned file Source/Source/Yamo/Expressions/SelectedSelectSqlExpressionOfT1T2T3T4T5T6T7T8T9T10T11T12T13T14T15T16T17T18T19T20T21T22T23.vb:1 — One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
D24 · Comment Value · redundant comment · ×2
  • redundant comment Source/Test/Yamo.Test.VB/Tests/ExpressionTests.vb:478 — "static indexer property" repeats the code it sits on: 3 of its 3 words (static, indexer, property) are already in `result = TranslateCondition(visitor, Function(x) x.IntColumn = StaticIndexerPropertyValue(10000))`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment Source/Test/Yamo.Test.VB/Tests/ExpressionTests.vb:647 — "static indexer property" repeats the code it sits on: 3 of its 3 words (static, indexer, property) are already in `result = TranslateCondition(visitor, Function(x) x.IntColumn = Class1.StaticIndexerPropertyValue(10000))`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
GD1 · Unfinished & placeholder code · Placeholder literal left in code · ×2
  • Placeholder literal left in code Source/Samples/Yamo.Playground.CS/Program.cs:294 — A placeholder string ("Lorem ipsum dolor sit amet.") is still in shipped code — typical of generated boilerplate that was never filled in.
  • Placeholder literal left in code Source/Samples/Yamo.Playground.CS/Program.cs:872 — A placeholder string ("Lorem ipsum") is still in shipped code — typical of generated boilerplate that was never filled in.
D20 · ADR Quality · No ADRs found · ×1
  • No ADRs found Source/Source/Yamo.CodeGenerator/Yamo.CodeGenerator.vbproj:4 — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`. ADRs are expected here because `Source/Source/Yamo.CodeGenerator/Yamo.CodeGenerator.vbproj` makes this repository a deployable product (line 4).
D26 · Project Cohesion · Projects may be oversized for their cohesion · ×1
  • Projects may be oversized for their cohesion Source/Source/Yamo/Yamo.vbproj:1 — `Yamo(netstandard2.0)` overshoots its size bounds (257398 LoC, 416 public types across 12 namespaces). 1 of 12 project(s) overshoot their size bounds, lowering Project Cohesion to 8.3/10. Size alone is no reason to split a project: where its type references show a separable part, a Split row names it.
D34 · Knowledge Freshness · Dormant codebase · ×1
  • Dormant codebase — 372 of 372 significant files have no living knowledge — the codebase as a whole is dormant, not 372 separate risks. Counted over 372 of the 474 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over. Re-engage owners or document before change.
M2 · Architecture documentation · No ADRs · ×1
  • No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
M2 · Architecture documentation · No architecture diagram/doc · ×1
  • No architecture diagram/doc — No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
P2 · Observability · Logging is not universal · ×1
  • Logging is not universal — Only 1/7 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 7, 4 ship a process this repository operates; the rest are libraries their consumer hosts, where the logging decision belongs to the host.
P3 · Security & performance tooling · No SAST · ×1
  • No SAST — No static application security testing detected. For this repository's stack, add a Roslyn security analyzer package referenced from the project (the analyzer packages do analyse VB.NET), plus gitleaks for committed secrets — CodeQL has no VB.NET extractor, so its csharp pack would extract nothing from this tree and then report it clean — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
P3 · Security & performance tooling · No dependency-update automation · ×1
  • No dependency-update automation REDACTED:51 — `REDACTED` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`.
P6 · Release Hygiene · No changelog · ×1
  • No changelog — No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
PF1 · Benchmark discipline · Benchmarks don't track allocations · ×1
  • Benchmarks don't track allocations — A BenchmarkDotNet suite exists but no [MemoryDiagnoser] — allocations (the main way hot code pressures the GC) aren't being measured.
X5 · Nullable reference types · Nullable reference types not enabled everywhere · ×1
  • Nullable reference types not enabled everywhere — 0/1 NRT-eligible project(s) enable <Nullable>enable</Nullable> (projects targeting a pre-C#-8 framework are excluded — NRTs aren't available there). NRTs catch a whole class of null-deref bugs at compile time.
Minor — 4 finding(s)
D24 · Comment Value · doc comments repeat the names · ×4
  • doc comments repeat the names Source/Source/Yamo/DbContextOptionsBuilder.vb:45 — 0 of 40798 documented parameters and 83 of 19612 summaries in `Yamo(netstandard2.0)` only repeat the member or parameter name (e.g. "Registers dialect specific SQL helper." for `RegisterDialectSpecificSqlHelper`). 40764 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names Source/Source/Yamo.SQLite/Infrastructure/SQLiteEntitySqlStringProviderFactory.vb:19 — 0 of 17 documented parameters and 0 of 17 summaries in `Yamo.SQLite(netstandard2.0)` only repeat the member or parameter name (e.g. "" for `tableName`). 17 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names Source/Source/Yamo.SqlServer/Sql/DateTime.vb:20 — 0 of 8 documented parameters and 0 of 10 summaries in `Yamo.SqlServer(netstandard2.0)` only repeat the member or parameter name (e.g. "" for `method`). 8 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names Source/Test/Yamo.Test/Helpers/Compare.vb:12 — 0 of 2 documented parameters and 0 of 2 summaries in `Yamo.Test` only repeat the member or parameter name (e.g. "" for `array1`). 2 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.

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.

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-5d4b6831930543c88358f29cf402f200/history.json --exit-code 0 --source .0artifacts/raw/gitleaks-history.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-5d4b6831930543c88358f29cf402f200/tree.json --exit-code 0 --source .0artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)semgrep—semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt .0artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiesdotnet—dotnet list Source/Yamo.sln package --vulnerable --include-transitive --format json4artifacts/raw/dotnet-vulnerable.json
D31 · IaC & Container Securitytrivy—trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.0—
D32 · Data Compliance (PII/GDPR)semgrep—semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.0—
D36 · Supply-chain Provenance & Signingprovenance—provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.0—
D37 · Vulnerability-disclosure Policydisclosure—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.0—
D40 · Network Egress Confinementruntime-hardening—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.0—
D41 · Kernel & Syscall Confinementruntime-hardening—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.0—
D42 · Runtime Threat Enforcementruntime-hardening—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—
D43 · Malicious Dependenciesosv-scanner—osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-1fd811524472425cbc218c22a8b7d9810artifacts/raw/osv-scanner.json

Run 01a1dd3c-64e1-7b99-89a0-cf8d7413444e · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Appendix C — Personal-data map

Every field, property and record parameter whose name is conventional personal data — 12 field(s) across 3 categories, each with an exact repo-relative file:line. This is the data inventory a compliance review starts from — right-to-erasure, retention, minimisation. Detected by NAME, from the C# syntax tree, with a deliberately specific identifier classifier — the same one the C1–C5 compliance cards use to decide whether personal data is present, so CardDefinition or FileName don't trip. Two caveats stated rather than glossed: those cards additionally require corroboration (a persistence/account signal, or two distinct PII categories) that this inventory deliberately does not, so it lists more than they gate on; and D32 Data Compliance shares nothing with it — that dimension is a separate semgrep ruleset for personal data leaking into logs, URLs and browser storage, and a clean D32 result says nothing about this list. Informational — it feeds no score.

Name — 8 field(s)
  • Person.FirstName Source/Samples/Yamo.Playground.CS/Model/Person.cs:13
  • Person.LastName Source/Samples/Yamo.Playground.CS/Model/Person.cs:15
  • User.FirstName Source/Samples/Yamo.Playground.CS/Model/User.cs:15
  • User.LastName Source/Samples/Yamo.Playground.CS/Model/User.cs:17
  • User2.m_FirstName Source/Samples/Yamo.Playground.CS/Model/User2.cs:25
  • User2.FirstName Source/Samples/Yamo.Playground.CS/Model/User2.cs:26
  • User2.m_LastName Source/Samples/Yamo.Playground.CS/Model/User2.cs:32
  • User2.LastName Source/Samples/Yamo.Playground.CS/Model/User2.cs:33
Email — 3 field(s)
  • User.Email Source/Samples/Yamo.Playground.CS/Model/User.cs:19
  • User2.m_Email Source/Samples/Yamo.Playground.CS/Model/User2.cs:39
  • User2.Email Source/Samples/Yamo.Playground.CS/Model/User2.cs:40
Date of birth — 1 field(s)
  • Person.BirthDate Source/Samples/Yamo.Playground.CS/Model/Person.cs:17

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.

⬇ Findings, MITRE CWE-tagged .sarif⬇ Health changelog .md