Public report of Tencent/tdesign-flutter, published 17 November 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.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, 17 November 2026, 23:59 UTC · Survey ID cd_cdf49f504ac242cf8208cb9111053dd9
Tencent/tdesign-flutter
Measured 17 November 2026, 23:56 UTC, at code version c6d3a96
CAI scoreAdequate
CriticalWeakAdequateStrongExemplary
Up 5.9 since the last survey
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A medium codebase: 95,524 lines of product code in 3 projects, tests not counted · Estimated rebuild effort: about 1.4 person-years · Weakest lens: Production Readiness, 43.7
Findings by how serious they are
63 critical468 serious31 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
Canine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
17 November 2026, 23:56 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 ▸
59of 59 dimensions measured by tools.
552of 562 findings point to an exact file and line, so you can open each one in the code. The other 10 concern the repository as a whole, such as missing documentation.
59dimensions across 6 lenses, read from 95,524 lines of product code in 3 projects.
Tencent/tdesign-flutter falls short of our standard for production, in part because we found no automated security scanning of the code, its secrets or its dependencies. It scores 55.8 out of 100 and is rated Adequate, and 61 of its 63 critical findings are security problems in the build pipeline and in the packages it uses.
Production Readiness, at 43.7, is the weakest lens and counts most in the score. The best first step is adding automated security scanning, worth about 7.0 points. Adding tests for the code no test reaches comes next, worth about 4.9 points. Raising Production Readiness to 70 would lift the score to about 65.0.
Forty-five pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Thirteen known security holes in the packages the code depends on can be used by attackers, and three secrets can leak from the build pipeline. Pinning each tool to an exact version, updating the vulnerable packages and limiting each secret to its own step would close these risks. The two parts of the code nobody has worked on for a long time need someone to learn and document them before anyone changes them.
The product code is 95,524 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 forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
If Production Readiness rose from 43.7 to 70, the lowest score rated Strong, the score would rise from 55.8 to about 65.0.
Code composition: what the lines of code are
Product code 47%Tests 53%
New since the last survey: 115 findings
These 115 critical or serious findings weren't in the previous survey, on 5 November 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 (50 corresponding lines) tdesign-component/lib/src/components/slider/t_slider.dart
Code Duplication · Edited copy of a member (41 corresponding lines) tdesign-component/lib/src/components/toast/t_toast.dart
Code Duplication · Edited copy of a member (36 corresponding lines) tdesign-component/lib/src/components/checkbox/t_check_box.dart
Code Duplication · Edited copy of a member (32 corresponding lines) tdesign-component/lib/src/components/action_sheet/t_action_sheet_grid.dart
Code Duplication · Edited copy of a member (37 corresponding lines) tdesign-component/lib/src/components/slider/t_slider.dart
Code Duplication · Edited copy of a member (21 corresponding lines) tdesign-component/lib/src/components/steps/t_steps_horizontal.dart
Code Duplication · Edited copy of a member (24 corresponding lines) tdesign-component/lib/src/components/slider/t_slider.dart
Code Duplication · Edited copy of a member (13 corresponding lines) tdesign-component/lib/src/components/tabs/t_tab_bar.dart
Code Duplication · Edited copy of a member (25 corresponding lines) tdesign-component/lib/src/components/slider/t_slider.dart
Code Duplication · Edited copy of a member (18 corresponding lines) tdesign-component/lib/src/components/tabs/t_horizontal_tab_bar.dart
Code Duplication · Edited copy of a member (14 corresponding lines) tdesign-component/lib/src/theme/t_internal_material.dart
Code Duplication · Edited copy of a member (11 corresponding lines) tdesign-component/lib/src/components/image_viewer/t_image_viewer.dart
Code Duplication · Edited copies of one member (3 members, 11+ corresponding lines) tdesign-component/lib/src/components/date_time_picker/t_date_time_picker.dart
Code Duplication · Edited copies of one member (4 members, 10+ corresponding lines) tdesign-component/lib/src/components/collapse/t_collapse.dart
Code Duplication · Edited copies of one member (6 members, 12+ corresponding lines) tdesign-component/lib/src/components/progress/t_progress_theme_data.dart
Code Duplication · Edited copy of a member (11 corresponding lines) tdesign-component/lib/src/components/popover/t_popover_theme_data.dart
Code Duplication · Edited copy of a member (20 corresponding lines) tdesign-component/lib/src/components/switch/t_cupertino_switch.dart
Code Duplication · Edited copy of a member (11 corresponding lines) tdesign-component/lib/src/components/indexes/sticky_header/layout_builder_hook.dart
Code Duplication · Edited copy of a member (10 corresponding lines) tdesign-component/lib/src/components/date_time_picker/t_date_time_picker_enums.dart
Code Duplication · Edited copy of a member (6 corresponding lines) tdesign-component/lib/src/components/dropdown_menu/t_dropdown_theme_data.dart
Code Duplication · Edited copy of a member (9 corresponding lines) tdesign-component/lib/src/components/swipe_cell/t_swipe_cell.dart
Code Duplication · Edited copy of a member (6 corresponding lines) tdesign-component/lib/src/components/action_sheet/t_action_sheet_theme_data.dart
Code Duplication · Edited copy of a member (6 corresponding lines) tdesign-component/lib/src/components/drawer/t_drawer_theme_data.dart
Code Duplication · Edited copies of one member (4 members, 6+ corresponding lines) tdesign-component/lib/src/components/badge/t_badge_theme_data.dart
Code Duplication · Edited copy of a member (7 corresponding lines) tdesign-component/lib/src/components/checkbox/t_check_box.dart
Code Duplication · Edited copy of a member (10 corresponding lines) tdesign-component/lib/src/components/drawer/t_drawer_theme_data.dart
Code Duplication · Edited copy of a member (6 corresponding lines) tdesign-component/lib/src/components/badge/t_badge_theme_data.dart
Code Duplication · Edited copy of a member (7 corresponding lines) tdesign-component/lib/src/components/notice_bar/t_notice_bar.dart
Code Duplication · Edited copy of a member (5 corresponding lines) tdesign-component/lib/src/components/progress/t_progress_theme_data.dart
Code Duplication · Edited copy of a member (4 corresponding lines) tdesign-component/lib/src/components/indexes/sticky_header/layout_builder_hook.dart
Code Duplication · Near-duplicate member family (8 members, 98 shared lines) tdesign-component/example/lib/page/calendar/calendar_described_example.dart
Code Duplication · Members sharing a duplicated core (9 members, 50+ identical tokens) tdesign-component/example/lib/page/calendar/calendar_described_example.dart
Code Duplication · Members sharing a duplicated core (8 members, 50+ identical tokens) tdesign-component/example/lib/page/calendar/calendar_described_example.dart
Code Duplication · Edited copy of a member (97 corresponding lines) tdesign-component/example/lib/page/badge/badge_page.dart
Code Duplication · Edited copy of a member (86 corresponding lines) tdesign-component/example/lib/page/tabs/tabs_page.dart
Code Duplication · Edited copies of one member (3 members, 83+ corresponding lines) tdesign-component/example/lib/page/input/input_page.dart
Code Duplication · Edited copy of a member (78 corresponding lines) tdesign-component/example/lib/page/popover/popover_page.dart
Code Duplication · Edited copies of one member (3 members, 69+ corresponding lines) tdesign-component/example/lib/page/avatar/avatar_page.dart
Code Duplication · Edited copy of a member (52 corresponding lines) tdesign-component/example/lib/page/drawer/drawer_page.dart
Code Duplication · Edited copies of one member (4 members, 67+ corresponding lines) tdesign-component/example/lib/page/calendar/calendar_page.dart
Code Duplication · Edited copy of a member (55 corresponding lines) tdesign-component/example/lib/page/notice_bar/notice_bar_page.dart
Code Duplication · Edited copy of a member (52 corresponding lines) tdesign-component/example/lib/page/search_bar/search_bar_page.dart
Code Duplication · Edited copy of a member (37 corresponding lines) tdesign-component/example/lib/page/table/table_fixed_last_example.dart
Code Duplication · Edited copy of a member (54 corresponding lines) tdesign-component/example/lib/page/cascader/cascader_page.dart
Code Duplication · Edited copy of a member (38 corresponding lines) tdesign-component/example/lib/page/indexes/indexes_page.dart
Code Duplication · Edited copy of a member (32 corresponding lines) tdesign-component/example/lib/page/link/color_preset_links_example.dart
Code Duplication · Edited copies of one member (3 members, 37+ corresponding lines) tdesign-component/example/lib/page/collapse/collapse_page.dart
Code Duplication · Edited copies of one member (3 members, 28+ corresponding lines) tdesign-component/example/lib/page/stepper/stepper_bounds_example.dart
Code Duplication · Edited copy of a member (34 corresponding lines) tdesign-component/example/lib/page/dropdown_menu/dropdown_menu_page.dart
Code Duplication · Edited copy of a member (20 corresponding lines) tdesign-component/example/lib/page/progress/progress_linear_status_example.dart
Code Duplication · Edited copy of a member (31 corresponding lines) tdesign-component/example/lib/page/message/message_page.dart
Code Duplication · Edited copy of a member (21 corresponding lines) tdesign-component/example/lib/page/radio/radio_positions_example.dart
Code Duplication · Edited copy of a member (27 corresponding lines) tdesign-component/example/lib/base/example_widget.dart
Code Duplication · Edited copy of a member (30 corresponding lines) tdesign-component/example/lib/page/empty/empty_page.dart
Code Duplication · Edited copy of a member (26 corresponding lines) tdesign-component/example/lib/page/icon/priority_demo_example.dart
Code Duplication · Edited copies of one member (3 members, 32+ corresponding lines) tdesign-component/example/lib/page/tag/dark_show_tags_example.dart
Code Duplication · Edited copy of a member (23 corresponding lines) tdesign-component/example/lib/page/popover/popover_page.dart
Code Duplication · Edited copy of a member (30 corresponding lines) tdesign-component/example/lib/page/divider/divider_page.dart
Code Duplication · Edited copy of a member (27 corresponding lines) tdesign-component/example/lib/page/image_viewer/image_viewer_page.dart
Code Duplication · Edited copies of one member (3 members, 12+ corresponding lines) tdesign-component/example/lib/page/table/table_basic_example.dart
Code Duplication · Edited copy of a member (22 corresponding lines) tdesign-component/example/lib/page/input/input_align_example.dart
Code Duplication · Edited copies of one member (4 members, 17+ corresponding lines) tdesign-component/example/lib/page/swiper/controls_swiper_example.dart
Code Duplication · Edited copy of a member (13 corresponding lines) tdesign-component/example/lib/page/result/basic_results_example.dart
Code Duplication · Edited copies of one member (5 members, 15+ corresponding lines) tdesign-component/example/lib/page/calendar/calendar_limited_example.dart
Code Duplication · Edited copy of a member (14 corresponding lines) tdesign-component/example/lib/page/badge/ribbon_badge_example.dart
Code Duplication · Edited copies of one member (5 members, 13+ corresponding lines) tdesign-component/example/lib/page/slider/slider_labeled_example.dart
Code Duplication · Edited copy of a member (19 corresponding lines) tdesign-component/example/lib/page/stepper/stepper_base_example.dart
Code Duplication · Edited copies of one member (4 members, 18+ corresponding lines) tdesign-component/example/lib/page/toast/fail_toast_example.dart
Code Duplication · Edited copy of a member (20 corresponding lines) tdesign-component/example/lib/page/toast/cover_toast_example.dart
Code Duplication · Edited copy of a member (20 corresponding lines) tdesign-component/example/lib/page/switch/switch_label_example.dart
Code Duplication · Edited copies of one member (3 members, 15+ corresponding lines) tdesign-component/example/lib/page/popover/popover_bottom_placements_example.dart
Code Duplication · Edited copies of one member (4 members, 15+ corresponding lines) tdesign-component/example/lib/page/button/disable_primary_fill_button_example.dart
Code Duplication · Edited copy of a member (16 corresponding lines) tdesign-component/example/lib/page/button/large_button_example.dart
Code Duplication · Edited copy of a member (10 corresponding lines) tdesign-component/example/lib/page/action_sheet/action_sheet_paged_grid_example.dart
Code Duplication · Edited copy of a member (14 corresponding lines) tdesign-component/example/lib/page/button/block_fill_button_example.dart
Code Duplication · Edited copy of a member (11 corresponding lines) tdesign-component/example/lib/page/badge/dot_message_badge_example.dart
Code Duplication · Edited copy of a member (13 corresponding lines) tdesign-component/example/lib/page/badge/dot_message_badge_example.dart
Code Duplication · Edited copies of one member (3 members, 13+ corresponding lines) tdesign-component/example/lib/page/picker/picker_area_example.dart
Code Duplication · Edited copy of a member (10 corresponding lines) tdesign-component/example/lib/page/tag/dark_show_tags_example.dart
Code Duplication · Edited copy of a member (9 corresponding lines) tdesign-component/example/lib/page/rate/rate_action_example.dart
Code Duplication · Edited copies of one member (3 members, 14+ corresponding lines) tdesign-component/example/lib/page/backtop/backtop_circle_trigger_example.dart
Code Duplication · Edited copies of one member (5 members, 8+ corresponding lines) tdesign-component/example/lib/page/tabs/tabs_item_with_line_example.dart
Code Duplication · Edited copies of one member (3 members, 8+ corresponding lines) tdesign-component/example/lib/page/date_time_picker/date_time_picker_title_example.dart
Code Duplication · Edited copies of one member (3 members, 9+ corresponding lines) tdesign-component/example/lib/page/action_sheet/action_sheet_center_list_example.dart
Code Duplication · Edited copy of a member (7 corresponding lines) tdesign-component/example/lib/page/date_time_picker/date_time_picker_date_time_example.dart
Code Duplication · Edited copy of a member (10 corresponding lines) tdesign-component/example/lib/page/link/prefix_links_example.dart
Code Duplication · Edited copies of one member (3 members, 12+ corresponding lines) tdesign-component/example/lib/page/tabs/tabs_item_with_split2_example.dart
Code Duplication · Edited copy of a member (9 corresponding lines) tdesign-component/example/lib/page/button/default_fill_button_example.dart
Code Duplication · Edited copy of a member (9 corresponding lines) tdesign-component/example/lib/page/button/default_fill_button_example.dart
Code Duplication · Edited copy of a member (10 corresponding lines) tdesign-component/example/lib/page/upload/upload_status_example.dart
Code Duplication · Edited copy of a member (10 corresponding lines) tdesign-component/example/lib/page/textarea/textarea_max_length_example.dart
Code Duplication · Edited copy of a member (9 corresponding lines) tdesign-component/example/lib/page/button/default_fill_button_example.dart
Code Duplication · Edited copy of a member (10 corresponding lines) tdesign-component/example/lib/page/message/message_styles_example.dart
Code Duplication · Edited copy of a member (5 corresponding lines) tdesign-component/example/lib/page/badge/circle_badge_example.dart
Code Duplication · Edited copy of a member (6 corresponding lines) tdesign-component/example/lib/page/link/basic_links_example.dart
Code Duplication · Edited copy of a member (4 corresponding lines) tdesign-component/example/lib/page/textarea/textarea_disabled_example.dart
We compare every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.
Fixed since the last survey: 23 findings
These 23 critical or serious findings were in the previous survey, on 5 November 2026, and are gone from this one.
Code Duplication · Near-duplicate member family (8 members, 109 shared lines) tdesign-component/example/lib/page/calendar/calendar_described_example.dart
Code Duplication · Members sharing a duplicated core (9 members, 50+ identical tokens) tdesign-component/example/lib/page/calendar/calendar_described_example.dart
Code Duplication · Members sharing a duplicated core (8 members, 50+ identical tokens) tdesign-component/example/lib/page/calendar/calendar_described_example.dart
€68,000 to €340,000, for 1,140 to 3,618 hours of work, about 1.4 person-years for 1 to 3 engineers
Difficulty of the problem
Standard, 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.8 at a score of 56. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Medium: 95,524 lines of product code
What it is not
Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.
How the estimate is made: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Add a SAST step to CI running what this repository's stack ships: the Dart analyzer's security lints plus `semgrep --config=auto` — so a security regression fails the build instead of landing.
Add tests that import the unreached modules (directly or through their public entry).
Raises the score by about 4.9 points · Medium effort · Test Coverage
3
Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
Raises the score by about 4.1 points · Medium effort · Type Safety
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.4 person-years of work. Its weakest lens is Production Readiness, at 43.7 (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
Add a SAST step to CI running what this repository's stack ships: the Dart analyzer's security lints plus `semgrep --config=auto` — so a security regression fails the build instead of landing. Of all the actions in this report, it raises the score most for the work it takes: about 7.0 points for medium effort. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
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 7.1 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 2% to 5% on every change. The history of the code shows how much it changes: about 342,904 lines over the last 90 days, which is about 1,390,666 lines a year. At that pace, the extra work comes to an estimated 74.2 to 463.6 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.
At a glance — Code Health · 56.0 · Adequate · gated by R1 ·
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A05:2025 — Injection
48
High / Critical
A03:2025 — Software Supply Chain Failures
31
High / Critical
Roadmap
Top priorities: Add a SAST step to CI running what this repository's stack ships: the Dart analyzer's security lints plus `semgrep --config=auto` — so a security regression fails the build instead of landing; Add tests that import the unreached modules (directly or through their public entry); Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Add a SAST step to CI running what this repository's stack ships: the Dart analyzer's security lints plus `semgrep --config=auto` — so a security regression fails the build instead of landing.
Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where we can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it.
Bring the 49 bodies over 15 down to 15 or less in Cognitive Complexity — start with TTag._resolveColors (cognitive 62), ExampleCodeGenerator.run (cognitive 51), _TButtonState.build (cognitive 48).
Bring the 41 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with _TDropdownMenuState._buildOverlay (cyclomatic 42), TFormItem.build (cyclomatic 39), TCheckbox.build (cyclomatic 32).
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 — 63
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 — 468
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 — 31
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 59 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, 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 — 59 dimensions across the health lenses
Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.
How to trust any code-health report — three questions
Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 552 of 562 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: this repository's production source spans .ts, .dart, and our analyzer cannot run the .dart test suite(s) — so no coverage was collected for the repository as a whole. The JavaScript/TypeScript half did build and run, and its own line coverage came back at 35.4% — but that is a figure for one half of the product, and we do not publish a partial one as if it were complete. This is OUR limitation, not a defect in the repo — coverage is excluded from the score rather than counted as a near-zero.
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 62 test(s) behind this row are the ones the JavaScript/TypeScript census could read, and this repository also carries at least 383 test source file(s) (.dart) that it cannot: it reads JavaScript/TypeScript test declarations off disk, so a 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.
D11 Test Reliability — 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. Test reliability NOT SCORED: this repository's production source includes .dart, and the built-in reliability runner cannot re-run the .dart test suite(s) — so reliability was not measured for the repository as a whole. The JavaScript/TypeScript (its own test command under node's V8 coverage via `pnpm install --frozen-lockfile --ignore-scripts` in tdesign-site/ (33 tests)): measured (0 flaky) suite(s) did re-run, and came back with 0 flaky across 1 measured tier(s) — but that is a figure for one half of the product, and we do not publish a partial one as if it were complete. This is OUR limitation, not a defect in the repo — test reliability is excluded from the score rather than counted.
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. Not scored — 2 Maven/Gradle manifest(s) were read, stating a version for 0 dependency(ies) and leaving 0 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
D14 License Compliance — 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. Not scored — this repository's 2 Maven/Gradle manifest(s) were read and none of the dependency coordinates they declare carries a version resolvable from the manifest itself: every one is inherited from a parent POM, a <dependencyManagement> block, an imported BOM or a Gradle version reference the catalogue does not define. Licences are resolved from the POMs Maven Central publishes, which requires a version to ask about, and grading whichever release happens to be newest today would be a verdict about a dependency graph this repository has not pinned. NOT a finding that this repository's licences are compliant: this dimension asserts nothing about its licensing in either direction.
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 — 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. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is a COLLECTOR gap, not an environment fault: it declares a published package (tdesign-component/pubspec.yaml), but no published-package marker D22 reads admitted any project here, so this ecosystem's public API has no collector, and the remedy is to write one — no change to the scan image can close it.
D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
D27 Navigability — 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. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
D32 Data Compliance (PII/GDPR) — 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. `scripts/documentation.mjs`, `tdesign-site/site/scripts/md-to-vue.ts` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
AXB2 Runtime readiness — 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. A program the dev server needs is not installed in our sandbox image. This is a limit of our sandbox, not of your repository. (rule: missing-tool). The renderer reported: the dev server (`npm run dev` in tdesign-site/) exited before it served a page. Likely cause (our sandbox): a program the dev server needs is not installed in our sandbox image. This is a limit of our sandbox, not of your repository. Last output: "> dev / > node script/dev.mjs / Error: spawn flutter ENOENT / at ChildProcess._handle.onexit (node:internal/child_process:285:19) / at onErrorNT (node:internal/child_process:483:16) / at process.processTicksAndRejections (node:internal/process/task_queues:90:21) { / errno: -2, / code: 'ENOENT', / syscall: 'spawn flutter', / path: 'flutter', / spawnargs: [ / 'run', / '-d', / 'web-server', / '--web-hostname', / '127.0.0.1', / '--web-port', / '19001', / '-t', / 'lib/main.dart' / ] / }" No runtime evidence was gathered.
AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DevServer (dev). the dev server (`npm run dev` in tdesign-site/) exited before it served a page. Likely cause (our sandbox): a program the dev server needs is not installed in our sandbox image. This is a limit of our sandbox, not of your repository. Last output: "> dev / > node script/dev.mjs / Error: spawn flutter ENOENT / at ChildProcess._handle.onexit (node:internal/child_process:285:19) / at onErrorNT (node:internal/child_process:483:16) / at process.processTicksAndRejections (node:internal/process/task_queues:90:21) { / errno: -2, / code: 'ENOENT', / syscall: 'spawn flutter', / path: 'flutter', / spawnargs: [ / 'run', / '-d', / 'web-server', / '--web-hostname', / '127.0.0.1', / '--web-port', / '19001', / '-t', / 'lib/main.dart' / ] / }" No runtime evidence was gathered.
M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. A badge or prose version claim scored 9/17 in its adjudication (docs/plans/deterministic-engine/adjudication/M4-v3.md: badges 9/9, prose 0/8, where prose versions are minimums or history), short of the 95 % precision gate, so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them. The .NET and Node.js version checks are a different kind and still publish.
M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
Repo exclusion declarations: 4 pattern(s) declared (.gitattributes linguist-generated/vendored, .editorconfig generated_code) excluded 0 source file(s) from code-quality scoring. Declarations are the repo's own visible statement that a tree is machine-written or vendored — auditable in any diff, honored by GitHub the same way.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
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").
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
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.
AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
What it measures: How tangled the control flow is — methods with many branches are hard to test and change.
Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.
41 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was _TDropdownMenuState._buildOverlay at 42. A further 3 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 _ProgressIndicatorState._buildLabelWidget at 24 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: tdesign-component/lib/src/components/link/t_link_resolve.dart (TLinkResolve.resolveColor at 18). 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.
+ 36 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 41 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with _TDropdownMenuState._buildOverlay (cyclomatic 42), TFormItem.build (cyclomatic 39), TCheckbox.build (cyclomatic 32). — 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 41 together lifts Cyclomatic Complexity from 6.9 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.
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.
+ 44 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 49 bodies over 15 down to 15 or less in Cognitive Complexity — start with TTag._resolveColors (cognitive 62), ExampleCodeGenerator.run (cognitive 51), _TButtonState.build (cognitive 48). — 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 49 together lifts Cognitive Complexity from 6.5 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes8.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.
Resolve the 24 MethodTooLong finding(s) in God Classes — start with t_input.dart (2), t_dropdown_menu.dart, t_indexes_list.dart. — One of this dimension's main actionable groups (24 warning-level).
Resolve the 14 FileTooLong finding(s) in God Classes — start with t_tab_bar.dart, t_slider.dart, t_dropdown_menu.dart. — One of this dimension's main actionable groups (14 warning-level).
Resolve the 8 ClassTooLong finding(s) in God Classes — start with t_dropdown_menu.dart, t_popover_widget.dart, t_table.dart. — One of this dimension's main actionable groups (8 warning-level).
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
118 duplicated block group(s) detected. 10.7 % of the production lines (10,218 of 95,524) are in a reported copy. A further 111 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 166 of the 229 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 (10 corresponding lines) · ×8tdesign-component/lib/src/components/date_time_picker/t_date_time_picker_enums.dart:86
+ 123 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 8 Edited copy of a member (10 corresponding lines) finding(s) in Code Duplication — start with t_date_time_picker_enums.dart, t_drawer_theme_data.dart, action_sheet_paged_grid_example.dart. — One of this dimension's main actionable groups (8 warning-level).
Resolve the 8 Duplicated block (14 lines × 2) finding(s) in Code Duplication — start with t_slider.dart (3), action_sheet_description_scroll_grid_example.dart, button_page.dart. — One of this dimension's main actionable groups (8 warning-level).
Resolve the 7 Duplicated block (13 lines × 2) finding(s) in Code Duplication — start with t_action_sheet_grid.dart, t_check_box.dart, t_slider.dart. — One of this dimension's main actionable groups (7 warning-level).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
2 production modules (pub), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 0 module(s) off the main sequence.
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.
Resolve the 19 Low cohesion finding(s) in Cohesion (LCOM4) — start with _popup_retention.dart, sticky_header_render.dart, layout_builder_hook.dart. — One of this dimension's main actionable groups (19 warning-level).
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D10 · Test Quality9.8 / 10Stronggated by 1 serious finding✓ Tool-verified
What it measures: Whether the tests truly assert behaviour rather than just running the code.
Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.
0 skipped, 1 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 62 tests. Measured on the JavaScript/TypeScript suite only — at least 383 test source file(s) (.dart) went unread, so its test quality is unmeasured and is not in these counts.
No assertions: repository copies and runnable migration snippets are synchronizedtdesign-site/site/flutter-example-docs/documentation.test.mjs:80
What to do
Resolve the 1 No assertions finding(s) in Test Quality — start with documentation.test.mjs. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
What it measures: 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.
Top hotspots: tdesign-component/lib/src/components/dropdown_menu/t_dropdown_menu.dart (8×42=336); tdesign-component/lib/src/components/button/t_button.dart (11×28=308); tdesign-component/lib/src/components/badge/t_badge.dart (11×27=297) Repeated repair below the complexity floor: tdesign-component/lib/src/components/picker/picker_item.dart (4 of 6 changes were fixes); tdesign-component/lib/src/components/picker/t_picker.dart (3 of 5 changes were fixes); tdesign-component/lib/src/components/date_time_picker/t_date_time_picker.dart (3 of 5 changes were fixes)
Resolve the 32 Hotspot finding(s) in Churn × Complexity Hotspots — start with t_dropdown_menu.dart, t_button.dart, t_badge.dart. — One of this dimension's main actionable groups (32 warning-level).
Resolve the 4 Repeated repair finding(s) in Churn × Complexity Hotspots — start with picker_item.dart, t_picker.dart, t_date_time_picker.dart. — One of this dimension's main actionable groups (4 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D16 · Bus Factor8.1 / 10Strong✓ Tool-verified
What it measures: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
36 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is tdesign-component/lib/src/components/tabbar/t_tab_bar.dart. Counted over 188 of the 267 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Off-boarding risk: anonymized user #1
What to do
Resolve the 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
1 deducted task-comment markers across 95524 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
Resolve the 1 TodoComment finding(s) in Explicit Debt — start with resource_delegate.dart. — 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.
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.
1 of 3 build units (npm, pub) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesiontdesign-component/pubspec.yaml:1
What to do
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with pubspec.yaml. — 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.
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.
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).
48 finding(s): 0 critical, 48 high, 0 medium, 0 low. 45 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 2 file(s) — `scripts/documentation.mjs` (lines 70–71, line 79, line 80), `tdesign-site/site/scripts/md-to-vue.ts` — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
REDACTED
REDACTED
REDACTED
What to do
Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 issue-level).
No action in Static Analysis (SAST) — all 40 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (40 issue-level, 0 of them charged here).
No action in Static Analysis (SAST) — all 5 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (5 issue-level, 0 of them charged here).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether 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.
Resolve the 13 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (13). — One of this dimension's main actionable groups (13 issue-level).
Resolve the 3 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 warning-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
9 of 188 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is tdesign-component/lib/src/components/tabs/t_horizontal_tab_bar.dart. Counted over 188 of the 267 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Resolve the 2 Orphaned knowledge finding(s) in Knowledge Freshness — start with t_horizontal_tab_bar.dart, t_cupertino_switch.dart. — One of this dimension's main actionable groups (2 issue-level).
Resolve the 7 Orphaned file finding(s) in Knowledge Freshness — start with sticky_header_render.dart, layout_builder_hook.dart, sticky_header_widget.dart. — One of this dimension's main actionable groups (7 recommendation-level).
Resolve the 1 Further orphaned files (smaller) 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.
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.
Resolve the 1 Change coupling finding(s) in Change Coupling — start with t_check_box_group.dart. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
+ 5 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 3 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 3 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Reported apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 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 .NET runtime image a Dockerfile builds FROM, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Other · Architecture — Whether any singleton service captures a scoped/transient dependency — a silent lifetime/threading bug.
Method: Roslyn scan: DI registrations parsed from AddSingleton/Scoped/Transient; each singleton checked for captured shorter-lifetime dependencies. Exhaustive, deterministic.
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. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').
Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.
`AppLocalizations` declares 67 abstract methods: `uploading`, `uploadSelect`, `uploadPending`, `uploadFailed`, `uploadRetry`, `uploadSuccess`, `components`, `setting`, `about`, `version`, `publishDate`, `defaultTheme`, `greenTheme`, `redTheme`, `darkTheme`, `cancel`, `confirm`, `switchClose`, `switchOpen`, `knew`, `loading`, `loadingWithPoint`, `other`, `refreshing`, `releaseRefresh`, `pullToRefresh`, `completeRefresh`, `reset`, `days`, `hours`, `minutes`, `seconds`, `milliseconds`, `yearLabel`, `monthLabel`, `dateLabel`, `weeks`, `sunday`, `monday`, `tuesday`, and 27 more. Counted over its public methods with no body, once per name; concrete methods and `_`-private members are not counted, because no implementer that extends it is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — tdesign-component/example/lib/l10n/app_localizations.dart:13
`TResourceDelegate` declares 53 abstract methods: `open`, `close`, `badgeZero`, `cancel`, `confirm`, `other`, `reset`, `loading`, `loadingWithPoint`, `knew`, `refreshing`, `releaseRefresh`, `pullToRefresh`, `completeRefresh`, `days`, `hours`, `minutes`, `seconds`, `milliseconds`, `yearLabel`, `monthLabel`, `dateLabel`, `weeksLabel`, `sunday`, `monday`, `tuesday`, `wednesday`, `thursday`, `friday`, `saturday`, `year`, `january`, `february`, `march`, `april`, `may`, `june`, `july`, `august`, `september`, and 13 more. Counted over its public methods with no body, once per name; concrete methods and `_`-private members are not counted, because no implementer that extends it is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — tdesign-component/lib/src/theme/resource_delegate.dart:72
What to do
Split fat interfaces into focused role-interfaces so clients depend only on what they use.
Do you agree with this assessment?
AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified
Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.
Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.
Other · Architecture — Whether read (query) handlers stay side-effect-free — a query that writes persistent state or raises events breaks CQS and makes reads unsafe to retry, cache, or route to a read replica.
Method: Roslyn scan: CQRS handlers classified query-vs-command by interface (IQueryHandler/ICommandHandler/IRequestHandler<TQuery,TResult>) and name convention (*Query/Get*/Find* vs *Command); each query handler's body checked for persistent-state writes (SaveChanges/repository Add-Update) or event publishes by resolved invocation. Deterministic, type-level, exhaustive over the detected handlers.
Coverage: Population: CQRS handlers identified by IQueryHandler/ICommandHandler/IRequestHandler interface + *Query/Get*/Find*/*Command NAME convention; query purity then checked exhaustively within that set — a query handler using neither convention is invisible, and mutation is a resolved persistence/publish CALL, not full dataflow.
Other · Code Health — Unreviewed-generation residue in this repository's Dart: methods whose whole body still throws UnimplementedError or a "not implemented" error, and placeholder text (lorem ipsum, changeme/replace_me…) left in strings of non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.
Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.
Other · Code Health — Unfinished work detected by code SHAPE, not keywords, in this repository's Dart: methods that only throw UnimplementedError or a "not implemented" exception, methods that take inputs and return a constant or do nothing, dead `if (false)` branches, and skeleton classes most of whose methods are holes.
Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.
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.
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.
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.
Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.
Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.
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 the Dart analyzer's security lints plus `semgrep --config=auto` as a CI step. What was searched, so you can tell an absence from a miss: the 16 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:4
`tdesign-site/package.json` 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`. — tdesign-site/package.json:16
What to do
Add a SAST step to CI running what this repository's stack ships: the Dart analyzer's security lints plus `semgrep --config=auto` — so a security regression fails the build instead of landing.
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
What to do
Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where we can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it.
Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from each language's code model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
Do you agree with this assessment?
R1 · Type Safety0.0 / 10Critical✓ Tool-verified
React / JS · Code Health — How much of the frontend is typed TypeScript vs untyped JavaScript.
Method: Frontend file inventory: the share of typed TypeScript vs untyped JavaScript across the source tree. Deterministic, exhaustive over frontend files.
0 typed · 10 plain JS — the untyped files are scripts/check-flutter-component-contracts.mjs, scripts/documentation.mjs, scripts/sync-readme.mjs, tdesign-component/tool/generate_api.mjs, tdesign-component/tool/generate_api_test.mjs, tdesign-site/script/config.js (+4 more).
What to do
Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
React / JS · Code Health — The share of the scored frontend lines inside a near-exact copy-pasted block of substantial extent (the D4 clone algorithm over JS/TS tokens, D-386; each line once, 10 at none and 0 at a quarter of the lines, as D4): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.
Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Scored on the share of the scored frontend lines inside a reported copy, on the same curve as D4. Deterministic.
React / JS · Code Health — Per-function cyclomatic/cognitive complexity from the token-level function scanner (D-386) — real branching, not a regex heuristic.
Method: Per-function cyclomatic/cognitive complexity from a token-level function scanner (real branching, not a regex heuristic), computed over every frontend function. Deterministic.
Do you agree with this assessment?
R3 · Large Files10.0 / 10Exemplary✓ Tool-verified
React / JS · Code Health — How many source files exceed the large-file threshold.
Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.
Do you agree with this assessment?
R4 · Test Coverage2.5 / 10Weak✓ Tool-verified
React / JS · Readiness — Static test reachability (D-386): the share of production files reachable from any test via the import graph — measured without running anything.
Method: Static test reachability: the share of production files reachable from any test via the import graph — measured without running anything. Deterministic.
No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×3) — tdesign-site/script/dev.mjs:1, tdesign-site/script/config.js:1, tdesign-site/script/copy-readme.js:1
What to do
Add tests that import the unreached modules (directly or through their public entry).
Do you agree with this assessment?
R6 · Tooling6.7 / 10Adequate✓ Tool-verified
React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each package.json script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.
Method: package.json scanned for test/lint/typecheck script wiring. Deterministic presence check.
test ✓ · lint ✗ · typecheck ✓ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
`tdesign-site` is TypeScript, but a type error in it cannot fail anything this repository runs: its `site` script (`pnpm test:theme && pnpm test:example-code && cd site && vite build`) compiles TypeScript with a transpile-only tool that strips types without checking them, and no script, config or CI step of the package runs `tsc --noEmit` or another type checker over it. Add a type check that can fail — a `typecheck` script running `tsc --noEmit` (or `vue-tsc`/`svelte-check`) that CI or the workspace pipeline runs, or a build step that checks before it bundles. — tdesign-site/package.json:9
`tdesign-site` configures a linter in `.eslintrc.js`, but no package script, bundler plugin, task runner or CI step in this repository runs a linter, so the rules it sets are enforced nowhere. Run it where it can fail: a `lint` script that CI runs, a linter plugin in the build, or a CI step. — tdesign-site/.eslintrc.js:1
What to do
Add eslint as package.json scripts and run them in CI.
Do you agree with this assessment?
R7 · Dead Code10.0 / 10Exemplary✓ Tool-verified
React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).
Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.
React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.
Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.
Declared in tdesign-site/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×6) — tdesign-site/package.json:17, tdesign-site/package.json:18, tdesign-site/package.json:27, …
What to do
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.
Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.
Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.
Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.
Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.
Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X13 · Undrained process stream10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.
Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.
Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.
Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.
Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.
Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a `for … in` loop leaves the `List`, `Map` or `Set` it is walking alone — Dart's collection iterators check that the collection has not changed since the loop began, so a body that adds to or removes from the very collection the loop is walking (or the map whose `keys`, `values` or `entries` it walks) makes the next step throw `ConcurrentModificationError` and the remaining elements are never seen. Whether a `for…of` or an array's own walk (`forEach`, `map`, `filter` …) leaves the array, `Map` or `Set` it is walking alone — JavaScript raises nothing, but the walk and the collection part: an array is walked by index against its live length, so a `splice` or `shift` in the body moves the next element under an index already passed and it is skipped, a `push` in a `for…of` is walked too (a loop that always appends never ends) while `forEach` never sees it; a `Map` or `Set` walk never produces an entry deleted before it is reached and visits every one added. Whether a `for…of` or an array's own walk (`forEach`, `map`, `filter` …) leaves the array, `Map` or `Set` it is walking alone — JavaScript raises nothing, but the walk and the collection part: an array is walked by index against its live length, so a `splice` or `shift` in the body moves the next element under an index already passed and it is skipped, a `push` in a `for…of` is walked too (a loop that always appends never ends) while `forEach` never sees it; a `Map` or `Set` walk never produces an entry deleted before it is reached and visits every one added.
Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.
Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
`catch (e)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×6) — tdesign-component/lib/src/util/iterable_ext.dart:19, tdesign-component/lib/src/util/map_ext.dart:26, tdesign-component/lib/src/util/map_ext.dart:40, …
An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×2) — tdesign-component/lib/src/util/map_ext.dart:167, tdesign-component/lib/src/util/string_util.dart:33
`catch (_)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — tdesign-component/lib/src/components/text/t_font_loader.dart:57
Other · Code Health — Whether Dart's sound null safety is on and is not undermined by null assertions — a package whose `environment: sdk:` lower bound is 2.12 or above is null safe, so `String` cannot hold null and `String?` must be checked before use, and each postfix `!` is a run-time `Null check operator used on a null value` the author has told the analyzer cannot happen.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
Do you agree with this assessment?
Reference — by lens
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 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.
X10 Duplicated predicate — 13 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 68 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 — Frontend below the scale floor (20 DOM element(s) < 25) — too little surface to assess accessibility.
AC2 Forms & labels — Frontend below the scale floor (20 DOM element(s) < 25) — too little surface to assess accessibility.
AC3 Page structure — Frontend below the scale floor (20 DOM element(s) < 25) — too little surface to assess accessibility.
AC4 Keyboard semantics — Frontend below the scale floor (20 DOM element(s) < 25) — too little surface to assess accessibility.
AC5 ARIA correctness — Frontend below the scale floor (20 DOM element(s) < 25) — too little surface to assess accessibility.
AC6 Visual & motion safety — Frontend below the scale floor (20 DOM element(s) < 25) — too little surface to assess accessibility.
AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Kotlin code is a Spring, JSR-330 or CDI singleton bean. No Swift request handler (a Vapor, Hummingbird, Kitura, Swifter or Perfect route handler, as a method or a registered closure) is declared, so no state is shared between request threads. Dart isolates share no mutable memory, so no two requests write one object at the same instant. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — the dev server (`npm run dev` in tdesign-site/) exited before it served a page. Likely cause (our sandbox): a program the dev server needs is not installed in our sandbox image. This is a limit of our sandbox, not of your repository. Last output: "> dev / > node script/dev.mjs / Error: spawn flutter ENOENT / at ChildProcess._handle.onexit (node:internal/child_process:285:19) / at onErrorNT (node:internal/child_process:483:16) / at process.processTicksAndRejections (node:internal/process/task_queues:90:21) { / errno: -2, / code: 'ENOENT', / syscall: 'spawn flutter', / path: 'flutter', / spawnargs: [ / 'run', / '-d', / 'web-server', / '--web-hostname', / '127.0.0.1', / '--web-port', / '19001', / '-t', / 'lib/main.dart' / ] / }" No runtime evidence was gathered. This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Drift table, an Isar, ObjectBox, Floor or Hive entity, or a Serverpod table model — and no database or data-store client (sqflite, Drift, Isar, Hive, Realm, Firestore, Supabase, postgres, …) in the source either, so this repository keeps no data at rest for these controls to protect.
C2 Access Controls — No access-control surface detected in the analyzed source — this repository stands up no server another machine can reach (no HttpServer or shelf server bound beyond loopback, no dart_frog route, no Serverpod endpoint, no Conduit, Alfred or Angel application) and keeps no data in a hosted backend. Access control is therefore N/A here — a Flutter app or pub package is authorized by the server it calls, not by itself; hiding a screen authorizes nothing. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Drift table, an ObjectBox/Floor @Entity, an Isar @collection, a Hive @HiveType or a Serverpod table model — and no database or data-store client (sqflite, Firestore, Supabase, postgres, …) imported either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a hosted backend configured outside this repository, for instance), the trail belongs to wherever that data is stored.
C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Drift table, an ObjectBox/Floor @Entity, an Isar @collection, a Hive @HiveType or a Serverpod table model — and no database or data-store client (sqflite, Firestore, Supabase, postgres, …) imported either, so this repository keeps no personal data whose lifetime a retention limit would bound.
C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Drift table, an ObjectBox/Floor @Entity, an Isar @collection, a Hive @HiveType or a Serverpod table model — and no database or data-store client (sqflite, Firestore, Supabase, postgres, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
D11 Test Reliability — Test reliability not scored — polyglot repository, one half has no runner
D12 Dependency Hygiene — Not scored — 2 Maven/Gradle manifest(s) were read, stating a version for 0 dependency(ies) and leaving 0 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
D14 License Compliance — JVM licences not graded — no declared coordinate carries a version the manifest itself resolves
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
D21 Naming Consistency — Naming consistency does not read html yet; not measured.
D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling 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"]`.
D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .dart, .kt, .py source were not judged.
D25 ADR Conformance — no ADRs to check
D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.dart), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
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) — 2 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
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 project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
D8 Code Coverage — Coverage not measured — polyglot repository, one half has no runner
DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and this analysis resolves a call's owner only where the receiver's type is written down in the source. Reported as guidance rather than measured
ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, which this analysis does not build from source alone for this language. Reported as guidance rather than measured
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
P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
P2 Observability — This repository's Dart, JavaScript/TypeScript source (3 module(s), 275 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the Dart, JavaScript/TypeScript source, so there is no service whose uptime a failing dependency could take down
P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
P9 Domain vs controller coverage — coverage data present for 13 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.
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for classes extending benchmark_harness's `BenchmarkBase`, `AsyncBenchmarkBase` or `PerfBenchmarkBase` (directly or through a base of your own), `benchmark(…)` calls under the pub `benchmark` package, Flutter's `benchmarkWidgets`, `watchPerformance` or `traceAction` in a test importing flutter_test, integration_test or flutter_driver, or benchmark_harness, benchmark or web_benchmarks in a pubspec.yaml, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
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.
R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
R5 Dependency Freshness — uses a pnpm lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
S1 Web-Security Posture — No web surface: 272 Dart file(s) were read for weak hashes and ciphers, key material fixed in the source and disabled TLS certificate validation, and none was found. This repository serves no HTTP of its own — no server framework among its pubspec dependencies, no `HttpServer` bound and no shelf, dart_frog or serverpod import in its production source or `bin/`, no web build target — so HTTPS enforcement, HSTS, cookie flags and input validation are N/A here, as they are for a C# library or worker. If this codebase starts serving HTTP, the dimension reactivates automatically.
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
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
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
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 C# was loaded; this repository's Dart was read, and no request in it can be cancelled by a caller (Dio, or package:http's Abortable requests) — package:http's get and post, HttpClient and Firebase or gRPC stubs offer their callers no token to take
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
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
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
X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
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 — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Dart was read, and it logs through none: package:logging, package:logger, talker and dart:developer take one finished message and no template arguments or fields (as log4net does in C#), so an interpolated message there loses nothing the API could have kept. Sentry's structured logs (`Sentry.logger`) would be judged.
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.
Orphaned knowledge tdesign-component/lib/src/components/tabs/t_horizontal_tab_bar.dart:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge tdesign-component/lib/src/components/switch/t_cupertino_switch.dart:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Hotspot: tdesign-component/lib/src/components/dropdown_menu/t_dropdown_menu.dart tdesign-component/lib/src/components/dropdown_menu/t_dropdown_menu.dart:1145— tdesign-component/lib/src/components/dropdown_menu/t_dropdown_menu.dart changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 42 in _TDropdownMenuState._buildOverlay at line 1145. 3 of those changes were fix/bug commits, and the other 5 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 10:14:06 +08:00' --until='2026-11-17 10:14:06 +08:00' --full-history --no-merges -- tdesign-component/lib/src/components/dropdown_menu/t_dropdown_menu.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: tdesign-component/lib/src/components/button/t_button.dart tdesign-component/lib/src/components/button/t_button.dart:139— tdesign-component/lib/src/components/button/t_button.dart changed 11 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 28 in _TButtonState.build at line 139. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 10:14:06 +08:00' --until='2026-11-17 10:14:06 +08:00' --full-history --no-merges -- tdesign-component/lib/src/components/button/t_button.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: tdesign-component/lib/src/components/badge/t_badge.dart tdesign-component/lib/src/components/badge/t_badge.dart:215— tdesign-component/lib/src/components/badge/t_badge.dart changed 11 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 27 in TBadge.build at line 215. 3 of those changes were fix/bug commits, and the other 8 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 10:14:06 +08:00' --until='2026-11-17 10:14:06 +08:00' --full-history --no-merges -- tdesign-component/lib/src/components/badge/t_badge.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: tdesign-component/lib/src/components/form/t_form_item.dart tdesign-component/lib/src/components/form/t_form_item.dart:74— tdesign-component/lib/src/components/form/t_form_item.dart changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 39 in TFormItem.build at line 74. 1 of those changes was a fix/bug commit, and the other 6 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 10:14:06 +08:00' --until='2026-11-17 10:14:06 +08:00' --full-history --no-merges -- tdesign-component/lib/src/components/form/t_form_item.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: tdesign-component/lib/src/components/checkbox/t_check_box.dart tdesign-component/lib/src/components/checkbox/t_check_box.dart:100— tdesign-component/lib/src/components/checkbox/t_check_box.dart changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 32 in TCheckbox.build at line 100. 2 of those changes were fix/bug commits, and the other 6 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 10:14:06 +08:00' --until='2026-11-17 10:14:06 +08:00' --full-history --no-merges -- tdesign-component/lib/src/components/checkbox/t_check_box.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: tdesign-component/lib/src/components/tabbar/t_tab_bar.dart tdesign-component/lib/src/components/tabbar/t_tab_bar.dart:899— tdesign-component/lib/src/components/tabbar/t_tab_bar.dart changed 14 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in _TTabBarItemWithBadge._constructItem at line 899. 3 of those changes were fix/bug commits, and the other 11 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 10:14:06 +08:00' --until='2026-11-17 10:14:06 +08:00' --full-history --no-merges -- tdesign-component/lib/src/components/tabbar/t_tab_bar.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: tdesign-component/lib/src/components/input/t_input.dart tdesign-component/lib/src/components/input/t_input.dart:559— tdesign-component/lib/src/components/input/t_input.dart changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 32 in _TInputShellState.build at line 559. 1 of those changes was a fix/bug commit, and the other 6 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 10:14:06 +08:00' --until='2026-11-17 10:14:06 +08:00' --full-history --no-merges -- tdesign-component/lib/src/components/input/t_input.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: tdesign-component/lib/src/components/slider/t_slider.dart tdesign-component/lib/src/components/slider/t_slider.dart:338— tdesign-component/lib/src/components/slider/t_slider.dart changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 24 in TSlider.build at line 338. 3 of those changes were fix/bug commits, and the other 4 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 10:14:06 +08:00' --until='2026-11-17 10:14:06 +08:00' --full-history --no-merges -- tdesign-component/lib/src/components/slider/t_slider.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: tdesign-component/lib/src/components/rate/t_rate.dart tdesign-component/lib/src/components/rate/t_rate.dart:120— tdesign-component/lib/src/components/rate/t_rate.dart changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 24 in _TRateState.build at line 120. 3 of those changes were fix/bug commits, and the other 4 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 10:14:06 +08:00' --until='2026-11-17 10:14:06 +08:00' --full-history --no-merges -- tdesign-component/lib/src/components/rate/t_rate.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: tdesign-component/lib/src/components/tag/t_tag.dart tdesign-component/lib/src/components/tag/t_tag.dart:204— tdesign-component/lib/src/components/tag/t_tag.dart changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 27 in TTag._resolveColors at line 204. 1 of those changes was a fix/bug commit, and the other 5 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 10:14:06 +08:00' --until='2026-11-17 10:14:06 +08:00' --full-history --no-merges -- tdesign-component/lib/src/components/tag/t_tag.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: tdesign-component/lib/src/components/radio/t_radio.dart tdesign-component/lib/src/components/radio/t_radio.dart:137— tdesign-component/lib/src/components/radio/t_radio.dart changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 32 in TRadio.build at line 137. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 10:14:06 +08:00' --until='2026-11-17 10:14:06 +08:00' --full-history --no-merges -- tdesign-component/lib/src/components/radio/t_radio.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: tdesign-component/lib/src/components/steps/t_steps_vertical_item.dart tdesign-component/lib/src/components/steps/t_steps_vertical_item.dart:54— tdesign-component/lib/src/components/steps/t_steps_vertical_item.dart changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 28 in TStepsVerticalItem.build at line 54. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 10:14:06 +08:00' --until='2026-11-17 10:14:06 +08:00' --full-history --no-merges -- tdesign-component/lib/src/components/steps/t_steps_vertical_item.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: tdesign-component/lib/src/components/progress/t_progress.dart tdesign-component/lib/src/components/progress/t_progress.dart:240— tdesign-component/lib/src/components/progress/t_progress.dart changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in TProgress.build at line 240. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 10:14:06 +08:00' --until='2026-11-17 10:14:06 +08:00' --full-history --no-merges -- tdesign-component/lib/src/components/progress/t_progress.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: tdesign-component/lib/src/components/swiper/t_swiper.dart tdesign-component/lib/src/components/swiper/t_swiper.dart:856— tdesign-component/lib/src/components/swiper/t_swiper.dart changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in _TSwiperState._buildControls at line 856. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 10:14:06 +08:00' --until='2026-11-17 10:14:06 +08:00' --full-history --no-merges -- tdesign-component/lib/src/components/swiper/t_swiper.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: tdesign-component/lib/src/components/search/t_search_bar.dart tdesign-component/lib/src/components/search/t_search_bar.dart:165— tdesign-component/lib/src/components/search/t_search_bar.dart changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in _TSearchBarState.build at line 165. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 10:14:06 +08:00' --until='2026-11-17 10:14:06 +08:00' --full-history --no-merges -- tdesign-component/lib/src/components/search/t_search_bar.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: tdesign-component/example/lib/page/calendar/calendar_double_described_example.dart tdesign-component/example/lib/page/calendar/calendar_double_described_example.dart:101— tdesign-component/example/lib/page/calendar/calendar_double_described_example.dart changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in _CalendarDoubleDescribedExampleState._showCalendar at line 101. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 10:14:06 +08:00' --until='2026-11-17 10:14:06 +08:00' --full-history --no-merges -- tdesign-component/example/lib/page/calendar/calendar_double_described_example.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: tdesign-component/lib/src/components/indexes/t_indexes_list.dart tdesign-component/lib/src/components/indexes/t_indexes_list.dart:98— tdesign-component/lib/src/components/indexes/t_indexes_list.dart changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 24 in _TIndexesListState.build at line 98. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 10:14:06 +08:00' --until='2026-11-17 10:14:06 +08:00' --full-history --no-merges -- tdesign-component/lib/src/components/indexes/t_indexes_list.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: tdesign-component/lib/src/components/cell/t_cell.dart tdesign-component/lib/src/components/cell/t_cell.dart:85— tdesign-component/lib/src/components/cell/t_cell.dart changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 30 in _TCellState.build at line 85. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 10:14:06 +08:00' --until='2026-11-17 10:14:06 +08:00' --full-history --no-merges -- tdesign-component/lib/src/components/cell/t_cell.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: tdesign-component/lib/src/components/textarea/t_textarea.dart tdesign-component/lib/src/components/textarea/t_textarea.dart:181— tdesign-component/lib/src/components/textarea/t_textarea.dart changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in _TTextareaState.build at line 181. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 10:14:06 +08:00' --until='2026-11-17 10:14:06 +08:00' --full-history --no-merges -- tdesign-component/lib/src/components/textarea/t_textarea.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: tdesign-component/lib/src/components/tabs/t_horizontal_tab_bar.dart tdesign-component/lib/src/components/tabs/t_horizontal_tab_bar.dart:873— tdesign-component/lib/src/components/tabs/t_horizontal_tab_bar.dart changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in _THorizontalTabBarState.build at line 873. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 10:14:06 +08:00' --until='2026-11-17 10:14:06 +08:00' --full-history --no-merges -- tdesign-component/lib/src/components/tabs/t_horizontal_tab_bar.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: tdesign-component/lib/src/components/steps/t_steps_horizontal_item.dart tdesign-component/lib/src/components/steps/t_steps_horizontal_item.dart:54— tdesign-component/lib/src/components/steps/t_steps_horizontal_item.dart changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in TStepsHorizontalItem.build at line 54. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 10:14:06 +08:00' --until='2026-11-17 10:14:06 +08:00' --full-history --no-merges -- tdesign-component/lib/src/components/steps/t_steps_horizontal_item.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: tdesign-component/lib/src/components/time_counter/t_time_counter_style.dart tdesign-component/lib/src/components/time_counter/t_time_counter_style.dart:53— tdesign-component/lib/src/components/time_counter/t_time_counter_style.dart changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 23 in _TTimeCounterStyle.generateStyle at line 53. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 10:14:06 +08:00' --until='2026-11-17 10:14:06 +08:00' --full-history --no-merges -- tdesign-component/lib/src/components/time_counter/t_time_counter_style.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: tdesign-component/lib/src/components/popup/t_popup_handle.dart tdesign-component/lib/src/components/popup/t_popup_handle.dart:55— tdesign-component/lib/src/components/popup/t_popup_handle.dart changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in TPopupHandle.open at line 55. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 10:14:06 +08:00' --until='2026-11-17 10:14:06 +08:00' --full-history --no-merges -- tdesign-component/lib/src/components/popup/t_popup_handle.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: tdesign-component/lib/src/components/tag/t_tag_theme_data.dart tdesign-component/lib/src/components/tag/t_tag_theme_data.dart:228— tdesign-component/lib/src/components/tag/t_tag_theme_data.dart changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in TTagThemeData.lerp at line 228. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 10:14:06 +08:00' --until='2026-11-17 10:14:06 +08:00' --full-history --no-merges -- tdesign-component/lib/src/components/tag/t_tag_theme_data.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: tdesign-component/example/lib/page/calendar/calendar_described_example.dart tdesign-component/example/lib/page/calendar/calendar_described_example.dart:46— tdesign-component/example/lib/page/calendar/calendar_described_example.dart changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in _CalendarDescribedExampleState._showCalendar at line 46. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 10:14:06 +08:00' --until='2026-11-17 10:14:06 +08:00' --full-history --no-merges -- tdesign-component/example/lib/page/calendar/calendar_described_example.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
MethodTooLong: _TDropdownMenuState._buildOverlay tdesign-component/lib/src/components/dropdown_menu/t_dropdown_menu.dart:1145— MethodTooLong — _buildOverlay runs 225 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 125 over it, 2.25× 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: _TIndexesListState.build tdesign-component/lib/src/components/indexes/t_indexes_list.dart:98— MethodTooLong — build runs 215 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 115 over it, 2.15× 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: _TButtonState.build tdesign-component/lib/src/components/button/t_button.dart:139— MethodTooLong — build runs 211 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 111 over it, 2.11× 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: _TSearchBarState.build tdesign-component/lib/src/components/search/t_search_bar.dart:165— MethodTooLong — build runs 194 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 94 over it, 1.94× 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: TFormItem.build tdesign-component/lib/src/components/form/t_form_item.dart:74— MethodTooLong — build runs 171 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 71 over it, 1.71× 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: _TInputState.build tdesign-component/lib/src/components/input/t_input.dart:221— MethodTooLong — build 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: TStepsVerticalItem.build tdesign-component/lib/src/components/steps/t_steps_vertical_item.dart:54— MethodTooLong — build runs 162 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 62 over it, 1.62× 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: _TRateState.build tdesign-component/lib/src/components/rate/t_rate.dart:120— MethodTooLong — build runs 152 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 52 over it, 1.52× 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: _THorizontalTabBarState.build tdesign-component/lib/src/components/tabs/t_horizontal_tab_bar.dart:873— MethodTooLong — build 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: TDialog.build tdesign-component/lib/src/components/dialog/t_dialog.dart:238— MethodTooLong — build runs 131 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 31 over it, 1.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: _TCellState.build tdesign-component/lib/src/components/cell/t_cell.dart:85— MethodTooLong — build runs 127 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 27 over it, 1.27× 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: TBadge.build tdesign-component/lib/src/components/badge/t_badge.dart:215— MethodTooLong — build runs 126 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 26 over it, 1.26× 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: TCheckbox.build tdesign-component/lib/src/components/checkbox/t_check_box.dart:100— MethodTooLong — build runs 118 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 18 over it, 1.18× 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: TSlider.build tdesign-component/lib/src/components/slider/t_slider.dart:338— MethodTooLong — build runs 117 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 17 over it, 1.17× 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: TStepsHorizontalItem.build tdesign-component/lib/src/components/steps/t_steps_horizontal_item.dart:54— MethodTooLong — build runs 117 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 17 over it, 1.17× 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: TProgress.build tdesign-component/lib/src/components/progress/t_progress.dart:240— MethodTooLong — build runs 112 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 12 over it, 1.12× 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: TPopover._showPopover tdesign-component/lib/src/components/popover/t_popover.dart:437— MethodTooLong — _showPopover runs 111 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 11 over it, 1.11× 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: TImage._buildImage tdesign-component/lib/src/components/image/t_image.dart:158— MethodTooLong — _buildImage runs 110 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 10 over it, 1.10× 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: TRadio.build tdesign-component/lib/src/components/radio/t_radio.dart:137— MethodTooLong — build runs 110 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 10 over it, 1.10× 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: _TTimeCounterStyle.generateStyle tdesign-component/lib/src/components/time_counter/t_time_counter_style.dart:53— MethodTooLong — generateStyle runs 110 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 10 over it, 1.10× 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: _TInputShellState.build tdesign-component/lib/src/components/input/t_input.dart:559— MethodTooLong — build runs 106 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 6 over it, 1.06× 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: _TCascaderState.build tdesign-component/lib/src/components/cascader/t_cascader.dart:148— MethodTooLong — build runs 104 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 4 over it, 1.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: _TDrawerContent.build tdesign-component/lib/src/components/drawer/t_drawer_content.dart:59— MethodTooLong — build runs 104 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 4 over it, 1.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: RenderSliverStickyHeader.performLayout tdesign-component/lib/src/components/indexes/sticky_header/sticky_header_render.dart:184— MethodTooLong — performLayout runs 101 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 1 over it, 1.01× 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.
Low cohesion: _PopupParkingRoute (LCOM4 13) tdesign-component/lib/src/components/popup/_popup_retention.dart:188— _PopupParkingRoute's methods fall into 13 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 13 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: RenderSliverStickyHeader (LCOM4 10) tdesign-component/lib/src/components/indexes/sticky_header/sticky_header_render.dart:9— RenderSliverStickyHeader's methods fall into 10 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 10 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: _LayoutBuilderElement (LCOM4 9) tdesign-component/lib/src/components/indexes/sticky_header/layout_builder_hook.dart:52— _LayoutBuilderElement's methods fall into 9 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 9 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: _RenderTDCupertinoSwitch (LCOM4 9) tdesign-component/lib/src/components/switch/t_cupertino_switch.dart:459— _RenderTDCupertinoSwitch's methods fall into 9 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 9 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: _TPopoverPage (LCOM4 7) tdesign-component/example/lib/page/popover/popover_page.dart:27— _TPopoverPage's methods fall into 7 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 7 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: _RenderTButtonTapTarget (LCOM4 7) tdesign-component/lib/src/components/button/t_button.dart:500— _RenderTButtonTapTarget's methods fall into 7 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 7 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: _TNoticeBarState (LCOM4 7) tdesign-component/lib/src/components/notice_bar/t_notice_bar.dart:122— _TNoticeBarState's methods fall into 7 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 7 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: _PopupNavigatorRoute (LCOM4 7) tdesign-component/lib/src/components/popup/_popup_route.dart:3— _PopupNavigatorRoute's methods fall into 7 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 7 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: _InterpolatedTagThemeData (LCOM4 7) tdesign-component/lib/src/components/tag/t_tag_theme_data.dart:351— _InterpolatedTagThemeData's methods fall into 7 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 7 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: _InterpolatedAvatarThemeData (LCOM4 6) tdesign-component/lib/src/components/avatar/t_avatar_theme_data.dart:289— _InterpolatedAvatarThemeData'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: _InterpolatedProgressThemeData (LCOM4 6) tdesign-component/lib/src/components/progress/t_progress_theme_data.dart:281— _InterpolatedProgressThemeData'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: SliverStickyHeaderRenderObjectElement (LCOM4 5) tdesign-component/lib/src/components/indexes/sticky_header/sticky_header_widget.dart:253— SliverStickyHeaderRenderObjectElement'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: _TInputShellState (LCOM4 5) tdesign-component/lib/src/components/input/t_input.dart:524— _TInputShellState'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: _TMessageState (LCOM4 5) tdesign-component/lib/src/components/message/t_message.dart:253— _TMessageState'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: _TabBarPopupRoute (LCOM4 5) tdesign-component/lib/src/components/tabbar/t_tab_bar.dart:1272— _TabBarPopupRoute'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: _TThemeColorsPageState (LCOM4 4) tdesign-component/example/lib/page/theme/theme_page.dart:19— _TThemeColorsPageState'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: _TPopoverWidgetState (LCOM4 4) tdesign-component/lib/src/components/popover/t_popover_widget.dart:101— _TPopoverWidgetState'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: _ProgressIndicatorState (LCOM4 4) tdesign-component/lib/src/components/progress/t_progress.dart:490— _ProgressIndicatorState'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: _TUploadState (LCOM4 4) tdesign-component/lib/src/components/upload/t_upload.dart:110— _TUploadState'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.
FileTooLong: tabbar/t_tab_bar.dart tdesign-component/lib/src/components/tabbar/t_tab_bar.dart— FileTooLong — 1132 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 632 over it, 2.26× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: slider/t_slider.dart tdesign-component/lib/src/components/slider/t_slider.dart— FileTooLong — 1126 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 626 over it, 2.25× 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: dropdown_menu/t_dropdown_menu.dart tdesign-component/lib/src/components/dropdown_menu/t_dropdown_menu.dart— FileTooLong — 1063 significant lines (blank, comment-only and punctuation-only lines excluded), about 78% of them inside a single declaration: _TDropdownMenuState (340-1438). The bar is 500 significant lines; this is 563 over it, 2.13× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: tabs/t_horizontal_tab_bar.dart tdesign-component/lib/src/components/tabs/t_horizontal_tab_bar.dart— FileTooLong — 1009 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 509 over it, 2.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: theme/t_internal_material.dart tdesign-component/lib/src/theme/t_internal_material.dart— FileTooLong — 810 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 310 over it, 1.62× 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: progress/t_progress.dart tdesign-component/lib/src/components/progress/t_progress.dart— FileTooLong — 801 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 301 over it, 1.60× 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: table/t_table.dart tdesign-component/lib/src/components/table/t_table.dart— FileTooLong — 713 significant lines (blank, comment-only and punctuation-only lines excluded), about 80% of them inside a single declaration: _TTableState (152-916). The bar is 500 significant lines; this is 213 over it, 1.43× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: swiper/t_swiper.dart tdesign-component/lib/src/components/swiper/t_swiper.dart— FileTooLong — 693 significant lines (blank, comment-only and punctuation-only lines excluded), about 71% of them inside a single declaration: _TSwiperState (297-931). The bar is 500 significant lines; this is 193 over it, 1.39× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: popover/t_popover_widget.dart tdesign-component/lib/src/components/popover/t_popover_widget.dart— FileTooLong — 690 significant lines (blank, comment-only and punctuation-only lines excluded), about 90% of them inside a single declaration: _TPopoverWidgetState (101-898). The bar is 500 significant lines; this is 190 over it, 1.38× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: theme/t_theme.dart tdesign-component/lib/src/theme/t_theme.dart— FileTooLong — 647 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 147 over it, 1.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: upload/t_upload.dart tdesign-component/lib/src/components/upload/t_upload.dart— FileTooLong — 595 significant lines (blank, comment-only and punctuation-only lines excluded), about 91% of them inside a single declaration: _TUploadState (110-843). The bar is 500 significant lines; this is 95 over it, 1.19× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: toast/t_toast.dart tdesign-component/lib/src/components/toast/t_toast.dart— FileTooLong — 549 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 49 over it, 1.10× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: rate/t_rate.dart tdesign-component/lib/src/components/rate/t_rate.dart— FileTooLong — 548 significant lines (blank, comment-only and punctuation-only lines excluded), about 93% of them inside a single declaration: _TRateState (76-737). The bar is 500 significant lines; this is 48 over it, 1.10× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: input/t_input.dart tdesign-component/lib/src/components/input/t_input.dart— FileTooLong — 537 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 37 over it, 1.07× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
ClassTooLong: _TDropdownMenuState tdesign-component/lib/src/components/dropdown_menu/t_dropdown_menu.dart:340— ClassTooLong — 826 significant lines (blank, comment-only and punctuation-only lines excluded), 33 methods. The bar is 400 significant lines; this is 426 over it, 2.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.
ClassTooLong: _TPopoverWidgetState tdesign-component/lib/src/components/popover/t_popover_widget.dart:101— ClassTooLong — 621 significant lines (blank, comment-only and punctuation-only lines excluded), 36 methods. The bar is 400 significant lines; this is 221 over it, 1.55× 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: _TTableState tdesign-component/lib/src/components/table/t_table.dart:152— ClassTooLong — 571 significant lines (blank, comment-only and punctuation-only lines excluded), 29 methods. The bar is 400 significant lines; this is 171 over it, 1.43× 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: _TUploadState tdesign-component/lib/src/components/upload/t_upload.dart:110— ClassTooLong — 541 significant lines (blank, comment-only and punctuation-only lines excluded), 42 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.
ClassTooLong: _TRateState tdesign-component/lib/src/components/rate/t_rate.dart:76— ClassTooLong — 509 significant lines (blank, comment-only and punctuation-only lines excluded), 26 methods. The bar is 400 significant lines; this is 109 over it, 1.27× 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: _TSwiperState tdesign-component/lib/src/components/swiper/t_swiper.dart:297— ClassTooLong — 492 significant lines (blank, comment-only and punctuation-only lines excluded), 29 methods. The bar is 400 significant lines; this is 92 over it, 1.23× 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: DateTimePickerSnapshot tdesign-component/lib/src/components/date_time_picker/t_date_time_picker_snapshot.part.dart:6— ClassTooLong — 437 significant lines (blank, comment-only and punctuation-only lines excluded), 23 methods. The bar is 400 significant lines; this is 37 over it, 1.09× 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: _ProgressIndicatorState tdesign-component/lib/src/components/progress/t_progress.dart:490— ClassTooLong — 433 significant lines (blank, comment-only and punctuation-only lines excluded), 31 methods. The bar is 400 significant lines; this is 33 over it, 1.08× 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: TResourceDelegate tdesign-component/lib/src/theme/resource_delegate.dart:72— TooManyMethods — 59 methods. The bar is 30 methods; this is 29 over it, 1.97× 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: _DefaultResourceDelegate tdesign-component/lib/src/theme/resource_delegate.dart:258— TooManyMethods — 53 methods. The bar is 30 methods; this is 23 over it, 1.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: _TUploadState tdesign-component/lib/src/components/upload/t_upload.dart:110— TooManyMethods — 42 methods. The bar is 30 methods; this is 12 over it, 1.40× 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: _TPopoverWidgetState tdesign-component/lib/src/components/popover/t_popover_widget.dart:101— TooManyMethods — 36 methods. The bar is 30 methods; this is 6 over it, 1.20× 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: _TSwipeCellState tdesign-component/lib/src/components/swipe_cell/t_swipe_cell.dart:124— TooManyMethods — 34 methods. The bar is 30 methods; this is 4 over it, 1.13× 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: _TDropdownMenuState tdesign-component/lib/src/components/dropdown_menu/t_dropdown_menu.dart:340— TooManyMethods — 33 methods. The bar is 30 methods; this is 3 over it, 1.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: _ProgressIndicatorState tdesign-component/lib/src/components/progress/t_progress.dart:490— TooManyMethods — 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.
TooManyMethods: _RenderTDCupertinoSwitch tdesign-component/lib/src/components/switch/t_cupertino_switch.dart:459— TooManyMethods — 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.
D4 · Code Duplication· Edited copy of a member (10 corresponding lines) · ×8
Edited copy of a member (10 corresponding lines) tdesign-component/lib/src/components/date_time_picker/t_date_time_picker_enums.dart:86— tdesign-component/lib/src/components/date_time_picker/t_date_time_picker_enums.dart:86-95 | tdesign-component/lib/src/components/date_time_picker/t_date_time_picker_model.dart:125-134 — 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) tdesign-component/lib/src/components/drawer/t_drawer_theme_data.dart:264— tdesign-component/lib/src/components/drawer/t_drawer_theme_data.dart:264-278 | tdesign-component/lib/src/components/notice_bar/t_notice_bar_theme_data.dart:207-216 — 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) tdesign-component/example/lib/page/action_sheet/action_sheet_paged_grid_example.dart:9— tdesign-component/example/lib/page/action_sheet/action_sheet_paged_grid_example.dart:9-18 | tdesign-component/example/lib/page/action_sheet/action_sheet_scroll_grid_example.dart:9-22 — 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) tdesign-component/example/lib/page/tag/dark_show_tags_example.dart:9— tdesign-component/example/lib/page/tag/dark_show_tags_example.dart:9-21 | tdesign-component/example/lib/page/tag/tag_page.dart:110-119 — 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) tdesign-component/example/lib/page/link/prefix_links_example.dart:8— tdesign-component/example/lib/page/link/prefix_links_example.dart:8-17 | tdesign-component/example/lib/page/link/suffix_links_example.dart:8-17 — 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) tdesign-component/example/lib/page/upload/upload_status_example.dart:16— tdesign-component/example/lib/page/upload/upload_status_example.dart:16-25 | tdesign-component/example/lib/page/upload/upload_tile_example.dart:16-26 — 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) tdesign-component/example/lib/page/textarea/textarea_max_length_example.dart:9— tdesign-component/example/lib/page/textarea/textarea_max_length_example.dart:9-18 | tdesign-component/example/lib/page/textarea/textarea_vertical_example.dart:9-19 — 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) tdesign-component/example/lib/page/message/message_styles_example.dart:50— tdesign-component/example/lib/page/message/message_styles_example.dart:50-59 | tdesign-component/example/lib/page/message/message_types_example.dart:47-56 — 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.
Duplicated block (14 lines × 2) tdesign-component/lib/src/components/slider/t_slider.dart:805— tdesign-component/lib/src/components/slider/t_slider.dart:805-818 | tdesign-component/lib/src/components/slider/t_slider.dart:908-921 — both copies are in the same file, so extract the 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 `tdesign-component/lib/src/components/slider/t_slider.dart:805` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) tdesign-component/lib/src/components/slider/t_slider.dart:856— tdesign-component/lib/src/components/slider/t_slider.dart:856-869 | tdesign-component/lib/src/components/slider/t_slider.dart:989-1002 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `tdesign-component/lib/src/components/slider/t_slider.dart:856` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) tdesign-component/lib/src/components/slider/t_slider.dart:1122— tdesign-component/lib/src/components/slider/t_slider.dart:1122-1135 | tdesign-component/lib/src/components/slider/t_slider.dart:1262-1275 — both copies are in the same file, so extract the 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 `tdesign-component/lib/src/components/slider/t_slider.dart:1122` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) tdesign-component/example/lib/page/action_sheet/action_sheet_description_scroll_grid_example.dart:73— tdesign-component/example/lib/page/action_sheet/action_sheet_description_scroll_grid_example.dart:73-86 | tdesign-component/example/lib/page/action_sheet/action_sheet_scroll_grid_example.dart:37-50 — before extracting anything, compare `tdesign-component/example/lib/page/action_sheet/action_sheet_description_scroll_grid_example.dart` and `tdesign-component/example/lib/page/action_sheet/action_sheet_scroll_grid_example.dart` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 129 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) tdesign-component/example/lib/page/button/button_page.dart:274— tdesign-component/example/lib/page/button/button_page.dart:274-287 | tdesign-component/example/lib/page/button/button_page.dart:294-307 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `tdesign-component/example/lib/page/button/button_page.dart:274` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `tdesign-component/example/lib/page/button/button_page.dart:273` calls `Text` and `tdesign-component/example/lib/page/button/button_page.dart:293` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (14 lines × 2) tdesign-component/example/lib/page/message/message_page.dart:14— tdesign-component/example/lib/page/message/message_page.dart:14-27 | tdesign-component/example/lib/page/toast/toast_page.dart:23-36 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `tdesign-component/example/lib/page/message/message_page.dart:14` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (14 lines × 2) tdesign-component/example/lib/page/sidebar/sidebar_custom_example.dart:40— tdesign-component/example/lib/page/sidebar/sidebar_custom_example.dart:40-53 | tdesign-component/example/lib/page/sidebar/sidebar_pagination_example.dart:41-54 — before extracting anything, compare `tdesign-component/example/lib/page/sidebar/sidebar_custom_example.dart` and `tdesign-component/example/lib/page/sidebar/sidebar_pagination_example.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 36 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `tdesign-component/example/lib/page/sidebar/sidebar_custom_example.dart:40` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (14 lines × 2) tdesign-component/example/lib/page/theme/theme_page.dart:72— tdesign-component/example/lib/page/theme/theme_page.dart:72-85 | tdesign-component/example/lib/page/theme/theme_page.dart:92-105 — both copies are in the same file, so extract the 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 `tdesign-component/example/lib/page/theme/theme_page.dart:72` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) tdesign-component/lib/src/components/action_sheet/t_action_sheet_grid.dart:79— tdesign-component/lib/src/components/action_sheet/t_action_sheet_grid.dart:79-91 | tdesign-component/lib/src/components/action_sheet/t_action_sheet_list.dart:78-90 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `tdesign-component/lib/src/components/action_sheet/t_action_sheet_grid.dart:79` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) tdesign-component/lib/src/components/checkbox/t_check_box.dart:268— tdesign-component/lib/src/components/checkbox/t_check_box.dart:268-280 | tdesign-component/lib/src/components/radio/t_radio.dart:297-309 — before extracting anything, compare `tdesign-component/lib/src/components/checkbox/t_check_box.dart` and `tdesign-component/lib/src/components/radio/t_radio.dart` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 65 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (13 lines × 2) tdesign-component/lib/src/components/slider/t_slider.dart:939— tdesign-component/lib/src/components/slider/t_slider.dart:939-951 | tdesign-component/lib/src/components/slider/t_slider.dart:1021-1033 — both copies are in the same file, so extract the 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 `tdesign-component/lib/src/components/slider/t_slider.dart:939` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) tdesign-component/lib/src/components/indexes/sticky_header/layout_builder_hook.dart:336— tdesign-component/lib/src/components/indexes/sticky_header/layout_builder_hook.dart:336-349 | tdesign-component/lib/src/components/indexes/sticky_header/sticky_header_layout_builder.dart:117-129 — 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (13 lines × 2) tdesign-component/example/lib/page/navbar/title_below_navbar_example.dart:40— tdesign-component/example/lib/page/navbar/title_below_navbar_example.dart:40-52 | tdesign-component/example/lib/page/navbar/title_left_navbar_example.dart:23-35 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `tdesign-component/example/lib/page/navbar/title_below_navbar_example.dart:40` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) tdesign-component/example/lib/page/popup/application_popups_example.dart:10— tdesign-component/example/lib/page/popup/application_popups_example.dart:10-22 | tdesign-component/example/lib/page/popup/base_popups_example.dart:10-22 — 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (13 lines × 2) tdesign-component/example/lib/page/toast/multiple_text_toast_example.dart:10— tdesign-component/example/lib/page/toast/multiple_text_toast_example.dart:10-22 | tdesign-component/example/lib/page/toast/text_toast_example.dart:10-22 — 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. 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.
Swallowed exception (caught, then discarded) tdesign-component/lib/src/util/iterable_ext.dart:19— `catch (e)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) tdesign-component/lib/src/util/map_ext.dart:26— `catch (e)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) tdesign-component/lib/src/util/map_ext.dart:40— `catch (e)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) tdesign-component/lib/src/util/map_ext.dart:71— `catch (e)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) tdesign-component/lib/src/util/map_ext.dart:88— `catch (e)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) tdesign-component/lib/src/util/map_ext.dart:105— `catch (e)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) tdesign-component/lib/src/components/text/t_font_loader.dart:57— `catch (_)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Duplicated block (11 lines × 2) tdesign-component/lib/src/components/checkbox/t_check_box.dart:446— tdesign-component/lib/src/components/checkbox/t_check_box.dart:446-456 | tdesign-component/lib/src/components/radio/t_radio.dart:397-407 — before extracting anything, compare `tdesign-component/lib/src/components/checkbox/t_check_box.dart` and `tdesign-component/lib/src/components/radio/t_radio.dart` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 65 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `tdesign-component/lib/src/components/checkbox/t_check_box.dart:446` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (11 lines × 2) tdesign-component/lib/src/components/slider/t_slider.dart:446— tdesign-component/lib/src/components/slider/t_slider.dart:446-456 | tdesign-component/lib/src/components/slider/t_slider.dart:615-625 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `tdesign-component/lib/src/components/slider/t_slider.dart:446` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (11 lines × 2) tdesign-component/lib/src/components/toast/t_toast.dart:765— tdesign-component/lib/src/components/toast/t_toast.dart:765-775 | tdesign-component/lib/src/components/toast/t_toast.dart:836-846 — both copies are in the same file, so extract the 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 `tdesign-component/lib/src/components/toast/t_toast.dart:765` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) tdesign-component/lib/src/components/drawer/t_drawer_theme_data.dart:252— tdesign-component/lib/src/components/drawer/t_drawer_theme_data.dart:252-262 | tdesign-component/lib/src/components/tabbar/t_tab_bar_theme_data.dart:134-144 — 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11 lines × 2) tdesign-component/example/lib/page/toast/horizontal_icon_toast_example.dart:10— tdesign-component/example/lib/page/toast/horizontal_icon_toast_example.dart:10-20 | tdesign-component/example/lib/page/toast/vertical_icon_toast_example.dart:10-20 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `tdesign-component/example/lib/page/toast/horizontal_icon_toast_example.dart:10` 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11 lines × 2) tdesign-component/example/lib/base/syntax_highlighter.dart:19— tdesign-component/example/lib/base/syntax_highlighter.dart:19-29 | tdesign-component/example/lib/base/syntax_highlighter.dart:32-42 — both copies are in the same file, so extract the 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.
Duplicated block (9 lines × 2) tdesign-component/example/lib/page/button/default_fill_button_example.dart:8— tdesign-component/example/lib/page/button/default_fill_button_example.dart:8-16 | tdesign-component/example/lib/page/button/primary_fill_button_example.dart:28-36 — before extracting anything, compare `tdesign-component/example/lib/page/button/default_fill_button_example.dart` and `tdesign-component/example/lib/page/button/primary_fill_button_example.dart` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 45 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 2) tdesign-component/example/lib/page/button/default_fill_button_example.dart:38— tdesign-component/example/lib/page/button/default_fill_button_example.dart:38-46 | tdesign-component/example/lib/page/button/primary_fill_button_example.dart:8-16 — before extracting anything, compare `tdesign-component/example/lib/page/button/default_fill_button_example.dart` and `tdesign-component/example/lib/page/button/primary_fill_button_example.dart` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 45 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 2) tdesign-component/example/lib/page/button/default_fill_button_example.dart:48— tdesign-component/example/lib/page/button/default_fill_button_example.dart:48-56 | tdesign-component/example/lib/page/button/primary_fill_button_example.dart:38-46 — before extracting anything, compare `tdesign-component/example/lib/page/button/default_fill_button_example.dart` and `tdesign-component/example/lib/page/button/primary_fill_button_example.dart` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 45 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 2) tdesign-component/example/lib/page/button/default_fill_button_example.dart:58— tdesign-component/example/lib/page/button/default_fill_button_example.dart:58-66 | tdesign-component/example/lib/page/button/primary_fill_button_example.dart:48-56 — before extracting anything, compare `tdesign-component/example/lib/page/button/default_fill_button_example.dart` and `tdesign-component/example/lib/page/button/primary_fill_button_example.dart` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 45 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 2) tdesign-component/example/lib/page/button/default_fill_button_example.dart:98— tdesign-component/example/lib/page/button/default_fill_button_example.dart:98-106 | tdesign-component/example/lib/page/button/primary_fill_button_example.dart:18-26 — before extracting anything, compare `tdesign-component/example/lib/page/button/default_fill_button_example.dart` and `tdesign-component/example/lib/page/button/primary_fill_button_example.dart` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 45 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 2) tdesign-component/example/lib/page/input/input_basic_example.dart:39— tdesign-component/example/lib/page/input/input_basic_example.dart:39-47 | tdesign-component/example/lib/page/input/input_password_example.dart:167-175 — 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, `tdesign-component/example/lib/page/input/input_basic_example.dart:49` calls `TextEditingController`, `FocusNode` and `tdesign-component/example/lib/page/input/input_password_example.dart:177` 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· Edited copy of a member (6 corresponding lines) · ×5
Edited copy of a member (6 corresponding lines) tdesign-component/lib/src/components/dropdown_menu/t_dropdown_theme_data.dart:340— tdesign-component/lib/src/components/dropdown_menu/t_dropdown_theme_data.dart:340-345 | tdesign-component/lib/src/components/swiper/t_swiper_theme_data.dart:309-320 — 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.
Edited copy of a member (6 corresponding lines) tdesign-component/lib/src/components/action_sheet/t_action_sheet_theme_data.dart:107— tdesign-component/lib/src/components/action_sheet/t_action_sheet_theme_data.dart:107-112 | tdesign-component/lib/src/components/notice_bar/t_notice_bar_theme_data.dart:199-205 — 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.
Edited copy of a member (6 corresponding lines) tdesign-component/lib/src/components/drawer/t_drawer_theme_data.dart:287— tdesign-component/lib/src/components/drawer/t_drawer_theme_data.dart:287-292 | tdesign-component/lib/src/components/notice_bar/t_notice_bar_theme_data.dart:225-230 — 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.
Edited copy of a member (6 corresponding lines) tdesign-component/lib/src/components/badge/t_badge_theme_data.dart:158— tdesign-component/lib/src/components/badge/t_badge_theme_data.dart:158-167 | tdesign-component/lib/src/components/result/t_result_theme_data.dart:70-75 — 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.
Edited copy of a member (6 corresponding lines) tdesign-component/example/lib/page/link/basic_links_example.dart:8— tdesign-component/example/lib/page/link/basic_links_example.dart:8-13 | tdesign-component/example/lib/page/link/underline_links_example.dart:8-13 — 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· Edited copy of a member (9 corresponding lines) · ×5
Edited copy of a member (9 corresponding lines) tdesign-component/lib/src/components/swipe_cell/t_swipe_cell.dart:193— tdesign-component/lib/src/components/swipe_cell/t_swipe_cell.dart:193-205 | tdesign-component/lib/src/components/form/t_form.dart:245-253 — These two members are one piece of code written twice and then edited apart: 9 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 (9 corresponding lines) tdesign-component/example/lib/page/rate/rate_action_example.dart:37— tdesign-component/example/lib/page/rate/rate_action_example.dart:37-45 | tdesign-component/example/lib/page/switch/switch_status_example.dart:49-59 — These two members are one piece of code written twice and then edited apart: 9 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 (9 corresponding lines) tdesign-component/example/lib/page/button/default_fill_button_example.dart:18— tdesign-component/example/lib/page/button/default_fill_button_example.dart:18-26 | tdesign-component/example/lib/page/button/primary_ghost_button_example.dart:28-36 — These two members are one piece of code written twice and then edited apart: 9 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 (9 corresponding lines) tdesign-component/example/lib/page/button/default_fill_button_example.dart:68— tdesign-component/example/lib/page/button/default_fill_button_example.dart:68-76 | tdesign-component/example/lib/page/button/primary_ghost_button_example.dart:18-26 — These two members are one piece of code written twice and then edited apart: 9 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 (9 corresponding lines) tdesign-component/example/lib/page/button/default_fill_button_example.dart:28— tdesign-component/example/lib/page/button/default_fill_button_example.dart:28-36 | tdesign-component/example/lib/page/button/disable_primary_fill_button_example.dart:49-57 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (15 lines × 2) tdesign-component/lib/src/components/checkbox/t_check_box.dart:173— tdesign-component/lib/src/components/checkbox/t_check_box.dart:173-187 | tdesign-component/lib/src/components/radio/t_radio.dart:226-240 — before extracting anything, compare `tdesign-component/lib/src/components/checkbox/t_check_box.dart` and `tdesign-component/lib/src/components/radio/t_radio.dart` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 65 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `tdesign-component/lib/src/components/checkbox/t_check_box.dart:173` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) tdesign-component/lib/src/components/slider/t_slider.dart:1079— tdesign-component/lib/src/components/slider/t_slider.dart:1079-1093 | tdesign-component/lib/src/components/slider/t_slider.dart:1206-1220 — both copies are in the same file, so extract the 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 `tdesign-component/lib/src/components/slider/t_slider.dart:1079` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) tdesign-component/example/lib/main.dart:109— tdesign-component/example/lib/main.dart:109-123 | tdesign-component/example/lib/main.dart:146-160 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15 lines × 2) tdesign-component/example/lib/page/message/message_styles_example.dart:83— tdesign-component/example/lib/page/message/message_styles_example.dart:83-97 | tdesign-component/example/lib/page/message/message_types_example.dart:114-128 — before extracting anything, compare `tdesign-component/example/lib/page/message/message_styles_example.dart` and `tdesign-component/example/lib/page/message/message_types_example.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 41 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (15 lines × 2) tdesign-component/example/lib/page/sidebar/sidebar_custom_example.dart:71— tdesign-component/example/lib/page/sidebar/sidebar_custom_example.dart:71-85 | tdesign-component/example/lib/page/sidebar/sidebar_pagination_example.dart:71-85 — before extracting anything, compare `tdesign-component/example/lib/page/sidebar/sidebar_custom_example.dart` and `tdesign-component/example/lib/page/sidebar/sidebar_pagination_example.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 36 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `tdesign-component/example/lib/page/sidebar/sidebar_custom_example.dart:71` 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.
Repeated repair: tdesign-component/lib/src/components/picker/picker_item.dart tdesign-component/lib/src/components/picker/picker_item.dart:46— tdesign-component/lib/src/components/picker/picker_item.dart changed 6 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 7 (its worst body is PickerItemWidget.build at line 46), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(text): 统一自定义文字槽默认样式与菜单高度 (#1184)”; “fix(components): 修复内置文字垂直居中与默认尺寸裁切 (#1160)”; “fix(TPicker): 修复选项文字居中并对齐演示 (#1120)”; “fix(TPicker): 修复主题覆盖顺序和高度插值 (#1076)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 10:14:06 +08:00' --until='2026-11-17 10:14:06 +08:00' --full-history --no-merges -- tdesign-component/lib/src/components/picker/picker_item.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: tdesign-component/lib/src/components/picker/t_picker.dart tdesign-component/lib/src/components/picker/t_picker.dart:69— tdesign-component/lib/src/components/picker/t_picker.dart changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 10 (its worst body is _TPickerState.didUpdateWidget at line 69), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(text): 统一自定义文字槽默认样式与菜单高度 (#1184)”; “fix(components): 修复内置文字垂直居中与默认尺寸裁切 (#1160)”; “fix(TPicker): 修复选择器弹层高度与滚轮裁切 (#1121)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 10:14:06 +08:00' --until='2026-11-17 10:14:06 +08:00' --full-history --no-merges -- tdesign-component/lib/src/components/picker/t_picker.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: tdesign-component/lib/src/components/date_time_picker/t_date_time_picker.dart tdesign-component/lib/src/components/date_time_picker/t_date_time_picker.dart:137— tdesign-component/lib/src/components/date_time_picker/t_date_time_picker.dart changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 9 (its worst body is _TDateTimePickerState.didUpdateWidget at line 137), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(components): 修复内置文字垂直居中与默认尺寸裁切 (#1160)”; “fix(date-time-picker): 修复文案更新导致滚轮拖动和惯性中断 (#1159)”; “fix(TPicker): 修复选择器弹层高度与滚轮裁切 (#1121)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 10:14:06 +08:00' --until='2026-11-17 10:14:06 +08:00' --full-history --no-merges -- tdesign-component/lib/src/components/date_time_picker/t_date_time_picker.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: tdesign-component/lib/src/components/picker/t_picker_theme_data.dart tdesign-component/lib/src/components/picker/t_picker_theme_data.dart:37— tdesign-component/lib/src/components/picker/t_picker_theme_data.dart changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 5 (its worst body is TPickerThemeData.lerp at line 37), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(components): 修复内置文字垂直居中与默认尺寸裁切 (#1160)”; “fix(TPicker): 修复选择器弹层高度与滚轮裁切 (#1121)”; “fix(TPicker): 修复主题覆盖顺序和高度插值 (#1076)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 10:14:06 +08:00' --until='2026-11-17 10:14:06 +08:00' --full-history --no-merges -- tdesign-component/lib/src/components/picker/t_picker_theme_data.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
D4 · Code Duplication· Edited copy of a member (11 corresponding lines) · ×4
Edited copy of a member (11 corresponding lines) tdesign-component/lib/src/components/image_viewer/t_image_viewer.dart:460— tdesign-component/lib/src/components/image_viewer/t_image_viewer.dart:460-470 | tdesign-component/lib/src/components/image_viewer/t_image_viewer.dart:472-484 — 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) tdesign-component/lib/src/components/popover/t_popover_theme_data.dart:173— tdesign-component/lib/src/components/popover/t_popover_theme_data.dart:173-183 | tdesign-component/lib/src/components/stepper/t_stepper_theme_interpolation.dart:143-153 — 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) tdesign-component/lib/src/components/indexes/sticky_header/layout_builder_hook.dart:304— tdesign-component/lib/src/components/indexes/sticky_header/layout_builder_hook.dart:304-314 | tdesign-component/lib/src/components/indexes/sticky_header/sticky_header_layout_builder.dart:93-103 — 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) tdesign-component/example/lib/page/badge/dot_message_badge_example.dart:21— tdesign-component/example/lib/page/badge/dot_message_badge_example.dart:21-32 | tdesign-component/example/lib/page/badge/number_message_badge_example.dart:17-27 — 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 copy of a member (20 corresponding lines) · ×4
Edited copy of a member (20 corresponding lines) tdesign-component/lib/src/components/switch/t_cupertino_switch.dart:160— tdesign-component/lib/src/components/switch/t_cupertino_switch.dart:160-179 | tdesign-component/lib/src/components/switch/t_cupertino_switch.dart:735-757 — 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.
Edited copy of a member (20 corresponding lines) tdesign-component/example/lib/page/progress/progress_linear_status_example.dart:10— tdesign-component/example/lib/page/progress/progress_linear_status_example.dart:10-29 | tdesign-component/example/lib/page/progress/progress_plump_status_example.dart:10-29 — 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.
Edited copy of a member (20 corresponding lines) tdesign-component/example/lib/page/toast/cover_toast_example.dart:9— tdesign-component/example/lib/page/toast/cover_toast_example.dart:9-30 | tdesign-component/example/lib/page/toast/show_toast_example.dart:9-28 — 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.
Edited copy of a member (20 corresponding lines) tdesign-component/example/lib/page/switch/switch_label_example.dart:9— tdesign-component/example/lib/page/switch/switch_label_example.dart:9-28 | tdesign-component/example/lib/page/switch/switch_sizes_example.dart:9-30 — 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.
Duplicated block (10 lines × 2) tdesign-component/lib/src/components/toast/t_toast.dart:762— tdesign-component/lib/src/components/toast/t_toast.dart:762-771 | tdesign-component/lib/src/components/toast/t_toast.dart:880-889 — both copies are in the same file, so extract the 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 `tdesign-component/lib/src/components/toast/t_toast.dart:762` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) tdesign-component/example/lib/page/form/form_basic_example.dart:251— tdesign-component/example/lib/page/form/form_basic_example.dart:251-260 | tdesign-component/example/lib/page/form/form_basic_example.dart:277-286 — both copies are in the same file, so extract the 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 `tdesign-component/example/lib/page/form/form_basic_example.dart:251` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) tdesign-component/example/lib/page/button/rectangle_icon_button_example.dart:19— tdesign-component/example/lib/page/button/rectangle_icon_button_example.dart:19-28 | tdesign-component/example/lib/page/button/rectangle_shape_button_example.dart:19-28 — 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 (10 lines × 2) tdesign-component/example/lib/page/action_sheet/action_sheet_description_grid_example.dart:9— tdesign-component/example/lib/page/action_sheet/action_sheet_description_grid_example.dart:9-18 | tdesign-component/example/lib/page/action_sheet/action_sheet_description_list_example.dart:9-18 — 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· Edited copy of a member (13 corresponding lines) · ×3
Edited copy of a member (13 corresponding lines) tdesign-component/lib/src/components/tabs/t_tab_bar.dart:121— tdesign-component/lib/src/components/tabs/t_tab_bar.dart:121-136 | tdesign-component/lib/src/components/tabs/t_tab_bar.dart:138-150 — 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.
Edited copy of a member (13 corresponding lines) tdesign-component/example/lib/page/result/basic_results_example.dart:9— tdesign-component/example/lib/page/result/basic_results_example.dart:9-21 | tdesign-component/example/lib/page/result/description_results_example.dart:9-33 — 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.
Edited copy of a member (13 corresponding lines) tdesign-component/example/lib/page/badge/dot_message_badge_example.dart:34— tdesign-component/example/lib/page/badge/dot_message_badge_example.dart:34-46 | tdesign-component/example/lib/page/badge/number_message_badge_example.dart:29-41 — 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 copy of a member (14 corresponding lines) · ×3
Edited copy of a member (14 corresponding lines) tdesign-component/lib/src/theme/t_internal_material.dart:644— tdesign-component/lib/src/theme/t_internal_material.dart:644-657 | tdesign-component/lib/src/theme/t_internal_material.dart:676-689 — 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.
Edited copy of a member (14 corresponding lines) tdesign-component/example/lib/page/badge/ribbon_badge_example.dart:9— tdesign-component/example/lib/page/badge/ribbon_badge_example.dart:9-22 | tdesign-component/example/lib/page/badge/triangle_badge_example.dart:9-22 — 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.
Edited copy of a member (14 corresponding lines) tdesign-component/example/lib/page/button/block_fill_button_example.dart:8— tdesign-component/example/lib/page/button/block_fill_button_example.dart:8-22 | tdesign-component/example/lib/page/fab/fab_collapsible_example.dart:22-35 — 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· Edited copy of a member (7 corresponding lines) · ×3
Edited copy of a member (7 corresponding lines) tdesign-component/lib/src/components/checkbox/t_check_box.dart:257— tdesign-component/lib/src/components/checkbox/t_check_box.dart:257-263 | tdesign-component/lib/src/components/radio/t_radio.dart:279-285 — 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) tdesign-component/lib/src/components/notice_bar/t_notice_bar.dart:356— tdesign-component/lib/src/components/notice_bar/t_notice_bar.dart:356-362 | tdesign-component/lib/src/components/swipe_cell/t_swipe_cell.dart:303-309 — 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) tdesign-component/example/lib/page/date_time_picker/date_time_picker_date_time_example.dart:16— tdesign-component/example/lib/page/date_time_picker/date_time_picker_date_time_example.dart:16-22 | tdesign-component/example/lib/page/date_time_picker/date_time_picker_month_day_example.dart:16-22 — 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.
Duplicated block (18 lines × 2) tdesign-component/lib/src/components/slider/t_slider.dart:920— tdesign-component/lib/src/components/slider/t_slider.dart:920-937 | tdesign-component/lib/src/components/slider/t_slider.dart:1001-1018 — both copies are in the same file, so extract the 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 `tdesign-component/lib/src/components/slider/t_slider.dart:920` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (18 lines × 2) tdesign-component/lib/src/components/text/t_text.dart:151— tdesign-component/lib/src/components/text/t_text.dart:151-168 | tdesign-component/lib/src/components/text/t_text.dart:171-188 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `tdesign-component/lib/src/components/text/t_text.dart:151` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (18 lines × 2) tdesign-component/example/lib/page/cell/cell_multiple_line_example.dart:92— tdesign-component/example/lib/page/cell/cell_multiple_line_example.dart:92-109 | tdesign-component/example/lib/page/cell/cell_single_line_example.dart:49-66 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `tdesign-component/example/lib/page/cell/cell_multiple_line_example.dart:92` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11 lines × 3) tdesign-component/lib/src/components/calendar/t_calendar.dart:343— tdesign-component/lib/src/components/calendar/t_calendar.dart:343-353 | tdesign-component/lib/src/components/date_time_picker/t_date_time_picker.dart:245-255 | tdesign-component/lib/src/components/sidebar/t_sidebar.dart:274-285 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `tdesign-component/lib/src/components/calendar/t_calendar.dart:343` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11 lines × 3) tdesign-component/example/lib/page/popover/popover_custom_content_example.dart:45— tdesign-component/example/lib/page/popover/popover_custom_content_example.dart:45-55 | tdesign-component/example/lib/page/popover/popover_custom_content_example.dart:58-68 | tdesign-component/example/lib/page/popover/popover_custom_content_example.dart:71-81 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `tdesign-component/example/lib/page/popover/popover_custom_content_example.dart:45` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 3) tdesign-component/example/lib/page/tag/close_fill_tag_example.dart:51— tdesign-component/example/lib/page/tag/close_fill_tag_example.dart:51-61 | tdesign-component/example/lib/page/tag/icon_fill_tag_example.dart:26-36 | tdesign-component/example/lib/page/tag/simple_fill_tag_example.dart:18-28 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 2) tdesign-component/lib/src/components/checkbox/t_check_box.dart:411— tdesign-component/lib/src/components/checkbox/t_check_box.dart:411-418 | tdesign-component/lib/src/components/radio/t_radio.dart:358-365 — before extracting anything, compare `tdesign-component/lib/src/components/checkbox/t_check_box.dart` and `tdesign-component/lib/src/components/radio/t_radio.dart` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 65 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 2) tdesign-component/lib/src/components/checkbox/t_check_box.dart:420— tdesign-component/lib/src/components/checkbox/t_check_box.dart:420-427 | tdesign-component/lib/src/components/radio/t_radio.dart:367-374 — before extracting anything, compare `tdesign-component/lib/src/components/checkbox/t_check_box.dart` and `tdesign-component/lib/src/components/radio/t_radio.dart` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 65 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 2) tdesign-component/example/lib/page/badge/large_badge_example.dart:9— tdesign-component/example/lib/page/badge/large_badge_example.dart:9-16 | tdesign-component/example/lib/page/badge/medium_badge_example.dart:9-16 — 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 (6 lines × 2) tdesign-component/lib/src/components/indexes/sticky_header/layout_builder_hook.dart:329— tdesign-component/lib/src/components/indexes/sticky_header/layout_builder_hook.dart:329-334 | tdesign-component/lib/src/components/indexes/sticky_header/sticky_header_layout_builder.dart:110-115 — 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 (6 lines × 2) tdesign-component/example/lib/page/action_sheet/action_sheet_basic_list_example.dart:32— tdesign-component/example/lib/page/action_sheet/action_sheet_basic_list_example.dart:32-37 | tdesign-component/example/lib/page/action_sheet/action_sheet_description_list_example.dart:33-38 — before extracting anything, compare `tdesign-component/example/lib/page/action_sheet/action_sheet_basic_list_example.dart` and `tdesign-component/example/lib/page/action_sheet/action_sheet_description_list_example.dart` 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.
Duplicated block (6 lines × 2) tdesign-component/example/lib/page/progress/progress_circle_example.dart:10— tdesign-component/example/lib/page/progress/progress_circle_example.dart:10-15 | tdesign-component/example/lib/page/progress/progress_micro_circle_example.dart:10-15 — 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (5 lines × 2) tdesign-component/lib/src/components/progress/t_progress_theme_data.dart:433— tdesign-component/lib/src/components/progress/t_progress_theme_data.dart:433-437 | tdesign-component/lib/src/components/tag/t_tag_theme_data.dart:482-486 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (5 lines × 2) tdesign-component/lib/src/components/checkbox/t_check_box.dart:245— tdesign-component/lib/src/components/checkbox/t_check_box.dart:245-249 | tdesign-component/lib/src/components/radio/t_radio.dart:267-271 — before extracting anything, compare `tdesign-component/lib/src/components/checkbox/t_check_box.dart` and `tdesign-component/lib/src/components/radio/t_radio.dart` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 65 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) tdesign-component/lib/src/components/checkbox/t_check_box.dart:251— tdesign-component/lib/src/components/checkbox/t_check_box.dart:251-255 | tdesign-component/lib/src/components/radio/t_radio.dart:311-315 — before extracting anything, compare `tdesign-component/lib/src/components/checkbox/t_check_box.dart` and `tdesign-component/lib/src/components/radio/t_radio.dart` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 65 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication· Members sharing a duplicated core (7 members, 50+ identical tokens) · ×3
Members sharing a duplicated core (7 members, 50+ identical tokens) tdesign-component/example/lib/page/action_sheet/action_sheet_badge_grid_example.dart:82— tdesign-component/example/lib/page/action_sheet/action_sheet_badge_grid_example.dart:82-97 | tdesign-component/example/lib/page/action_sheet/action_sheet_basic_grid_example.dart:101-116 | tdesign-component/example/lib/page/action_sheet/action_sheet_description_grid_example.dart:102-117 | tdesign-component/example/lib/page/action_sheet/action_sheet_description_scroll_grid_example.dart:115-130 | tdesign-component/example/lib/page/action_sheet/action_sheet_description_scroll_grid_example.dart:184-199 | tdesign-component/example/lib/page/action_sheet/action_sheet_paged_grid_example.dart:102-117 | tdesign-component/example/lib/page/action_sheet/action_sheet_scroll_grid_example.dart:79-94 — 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) tdesign-component/example/lib/page/link/basic_links_example.dart:26— tdesign-component/example/lib/page/link/basic_links_example.dart:26-45 | tdesign-component/example/lib/page/link/color_preset_links_example.dart:52-71 | tdesign-component/example/lib/page/link/disabled_links_example.dart:56-75 | tdesign-component/example/lib/page/link/link_sizes_example.dart:45-64 | tdesign-component/example/lib/page/link/prefix_links_example.dart:30-49 | tdesign-component/example/lib/page/link/suffix_links_example.dart:30-49 | tdesign-component/example/lib/page/link/underline_links_example.dart:26-45 — 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) tdesign-component/example/lib/page/navbar/logo_navbar_example.dart:9— tdesign-component/example/lib/page/navbar/logo_navbar_example.dart:9-37 | tdesign-component/example/lib/page/navbar/navbar_right_multi_action_example.dart:9-30 | tdesign-component/example/lib/page/navbar/search_navbar_example.dart:9-38 | tdesign-component/example/lib/page/navbar/title_below_navbar_example.dart:9-52 | tdesign-component/example/lib/page/navbar/title_center_navbar_example.dart:9-26 | tdesign-component/example/lib/page/navbar/title_left_navbar_example.dart:9-35 | tdesign-component/example/lib/page/navbar/title_normal_navbar_example.dart:9-26 — 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· Members sharing a duplicated core (6 members, 50+ identical tokens) · ×3
Members sharing a duplicated core (6 members, 50+ identical tokens) tdesign-component/example/lib/page/action_sheet/action_sheet_badge_grid_example.dart:32— tdesign-component/example/lib/page/action_sheet/action_sheet_badge_grid_example.dart:32-76 | tdesign-component/example/lib/page/action_sheet/action_sheet_basic_grid_example.dart:41-62 | tdesign-component/example/lib/page/action_sheet/action_sheet_description_grid_example.dart:42-63 | tdesign-component/example/lib/page/action_sheet/action_sheet_description_scroll_grid_example.dart:92-113 | tdesign-component/example/lib/page/action_sheet/action_sheet_paged_grid_example.dart:79-100 | tdesign-component/example/lib/page/action_sheet/action_sheet_scroll_grid_example.dart:56-77 — These 6 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 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.
Members sharing a duplicated core (6 members, 50+ identical tokens) tdesign-component/example/lib/page/action_sheet/action_sheet_badge_grid_example.dart:99— tdesign-component/example/lib/page/action_sheet/action_sheet_badge_grid_example.dart:99-111 | tdesign-component/example/lib/page/action_sheet/action_sheet_basic_grid_example.dart:87-99 | tdesign-component/example/lib/page/action_sheet/action_sheet_description_grid_example.dart:88-100 | tdesign-component/example/lib/page/action_sheet/action_sheet_description_scroll_grid_example.dart:155-167 | tdesign-component/example/lib/page/action_sheet/action_sheet_paged_grid_example.dart:65-77 | tdesign-component/example/lib/page/action_sheet/action_sheet_scroll_grid_example.dart:119-131 — These 6 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 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.
Members sharing a duplicated core (6 members, 50+ identical tokens) tdesign-component/example/lib/page/popover/popover_left_placements_example.dart:17— tdesign-component/example/lib/page/popover/popover_left_placements_example.dart:17-43 | tdesign-component/example/lib/page/popover/popover_left_placements_example.dart:45-71 | tdesign-component/example/lib/page/popover/popover_left_placements_example.dart:73-99 | tdesign-component/example/lib/page/popover/popover_right_placements_example.dart:17-43 | tdesign-component/example/lib/page/popover/popover_right_placements_example.dart:45-71 | tdesign-component/example/lib/page/popover/popover_right_placements_example.dart:73-99 — These 6 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 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· Members sharing a duplicated core (5 members, 50+ identical tokens) · ×3
Members sharing a duplicated core (5 members, 50+ identical tokens) tdesign-component/example/lib/page/action_sheet/action_sheet_basic_grid_example.dart:64— tdesign-component/example/lib/page/action_sheet/action_sheet_basic_grid_example.dart:64-85 | tdesign-component/example/lib/page/action_sheet/action_sheet_description_grid_example.dart:65-86 | tdesign-component/example/lib/page/action_sheet/action_sheet_description_scroll_grid_example.dart:132-153 | tdesign-component/example/lib/page/action_sheet/action_sheet_paged_grid_example.dart:38-59 | tdesign-component/example/lib/page/action_sheet/action_sheet_scroll_grid_example.dart:96-117 — These 5 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 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
Members sharing a duplicated core (5 members, 50+ identical tokens) tdesign-component/example/lib/page/dialog/button_dialogs_example.dart:97— tdesign-component/example/lib/page/dialog/button_dialogs_example.dart:97-106 | tdesign-component/example/lib/page/dialog/confirm_dialogs_example.dart:42-51 | tdesign-component/example/lib/page/dialog/feedback_dialogs_example.dart:56-65 | tdesign-component/example/lib/page/dialog/image_dialogs_example.dart:62-71 | tdesign-component/example/lib/page/dialog/input_dialogs_example.dart:42-51 — These 5 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 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
Members sharing a duplicated core (5 members, 50+ identical tokens) tdesign-component/example/lib/page/upload/upload_message_file_example.dart:49— tdesign-component/example/lib/page/upload/upload_message_file_example.dart:49-64 | tdesign-component/example/lib/page/upload/upload_multiple_example.dart:48-63 | tdesign-component/example/lib/page/upload/upload_single_example.dart:27-42 | tdesign-component/example/lib/page/upload/upload_status_example.dart:55-70 | tdesign-component/example/lib/page/upload/upload_tile_example.dart:49-64 — These 5 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 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
Duplicated block (17 lines × 2) tdesign-component/example/lib/home.dart:108— tdesign-component/example/lib/home.dart:108-124 | tdesign-component/example/lib/home.dart:133-149 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `tdesign-component/example/lib/home.dart:108` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17 lines × 2) tdesign-component/example/lib/page/navbar/title_center_navbar_example.dart:10— tdesign-component/example/lib/page/navbar/title_center_navbar_example.dart:10-26 | tdesign-component/example/lib/page/navbar/title_normal_navbar_example.dart:10-26 — 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. 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.
Duplicated block (17 lines × 2) tdesign-component/example/lib/page/popover/popover_page.dart:192— tdesign-component/example/lib/page/popover/popover_page.dart:192-208 | tdesign-component/example/lib/page/popover/popover_page.dart:209-225 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (16 lines × 2) tdesign-component/example/lib/page/input/input_basic_example.dart:53— tdesign-component/example/lib/page/input/input_basic_example.dart:53-68 | tdesign-component/example/lib/page/input/input_password_example.dart:177-192 — 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 before the matched lines, `tdesign-component/example/lib/page/input/input_basic_example.dart:49` calls `TextEditingController`, `FocusNode` and `tdesign-component/example/lib/page/input/input_password_example.dart:175` 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 (16 lines × 2) tdesign-component/example/lib/page/pull_down_refresh/pull_down_refresh_loading_texts_example.dart:50— tdesign-component/example/lib/page/pull_down_refresh/pull_down_refresh_loading_texts_example.dart:50-65 | tdesign-component/example/lib/page/pull_down_refresh/pull_down_refresh_timeout_example.dart:44-59 — 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (16 lines × 2) tdesign-component/example/lib/page/table/table_operation_icon_example.dart:13— tdesign-component/example/lib/page/table/table_operation_icon_example.dart:13-28 | tdesign-component/example/lib/page/table/table_operation_text_example.dart:13-28 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `tdesign-component/example/lib/page/table/table_operation_icon_example.dart:13` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) tdesign-component/example/lib/page/button/button_page.dart:270— tdesign-component/example/lib/page/button/button_page.dart:270-281 | tdesign-component/example/lib/page/button/button_page.dart:310-322 — both copies are in the same file, so extract the 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 `tdesign-component/example/lib/page/button/button_page.dart:270` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) tdesign-component/example/lib/page/calendar/lunar_data_source_example.dart:185— tdesign-component/example/lib/page/calendar/lunar_data_source_example.dart:185-196 | tdesign-component/example/lib/page/calendar/lunar_data_source_example.dart:199-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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (12 lines × 2) tdesign-component/example/lib/page/sidebar/navigator_side_bar_example.dart:23— tdesign-component/example/lib/page/sidebar/navigator_side_bar_example.dart:23-35 | tdesign-component/example/lib/page/sidebar/style_side_bar_example.dart:23-34 — before extracting anything, compare `tdesign-component/example/lib/page/sidebar/navigator_side_bar_example.dart` and `tdesign-component/example/lib/page/sidebar/style_side_bar_example.dart` as WHOLE FILES: this scan already matched 3 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. 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.
R4 · Test Coverage· No test reaches this file · ×3
No test reaches this file tdesign-site/script/dev.mjs:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file tdesign-site/script/config.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file tdesign-site/script/copy-readme.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
D4 · Code Duplication· Edited copy of a member (32 corresponding lines) · ×2
Edited copy of a member (32 corresponding lines) tdesign-component/lib/src/components/action_sheet/t_action_sheet_grid.dart:68— tdesign-component/lib/src/components/action_sheet/t_action_sheet_grid.dart:68-103 | tdesign-component/lib/src/components/action_sheet/t_action_sheet_list.dart:66-97 — These two members are one piece of code written twice and then edited apart: 32 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (32 corresponding lines) tdesign-component/example/lib/page/link/color_preset_links_example.dart:8— tdesign-component/example/lib/page/link/color_preset_links_example.dart:8-39 | tdesign-component/example/lib/page/link/disabled_links_example.dart:8-43 — These two members are one piece of code written twice and then edited apart: 32 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (37 corresponding lines) · ×2
Edited copy of a member (37 corresponding lines) tdesign-component/lib/src/components/slider/t_slider.dart:1206— tdesign-component/lib/src/components/slider/t_slider.dart:1206-1244 | tdesign-component/lib/src/components/slider/t_slider.dart:1262-1298 — These two members are one piece of code written twice and then edited apart: 37 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 (37 corresponding lines) tdesign-component/example/lib/page/table/table_fixed_last_example.dart:13— tdesign-component/example/lib/page/table/table_fixed_last_example.dart:13-54 | tdesign-component/example/lib/page/table/table_operation_text_example.dart:13-49 — These two members are one piece of code written twice and then edited apart: 37 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 (21 corresponding lines) · ×2
Edited copy of a member (21 corresponding lines) tdesign-component/lib/src/components/steps/t_steps_horizontal.dart:51— tdesign-component/lib/src/components/steps/t_steps_horizontal.dart:51-77 | tdesign-component/lib/src/components/steps/t_steps_vertical.dart:51-71 — 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.
Edited copy of a member (21 corresponding lines) tdesign-component/example/lib/page/radio/radio_positions_example.dart:14— tdesign-component/example/lib/page/radio/radio_positions_example.dart:14-34 | tdesign-component/example/lib/page/radio/radio_themes_example.dart:14-38 — 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 (5 corresponding lines) · ×2
Edited copy of a member (5 corresponding lines) tdesign-component/lib/src/components/progress/t_progress_theme_data.dart:362— tdesign-component/lib/src/components/progress/t_progress_theme_data.dart:362-367 | tdesign-component/lib/src/components/tag/t_tag_theme_data.dart:441-445 — These two members are one piece of code written twice and then edited apart: 5 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 (5 corresponding lines) tdesign-component/example/lib/page/badge/circle_badge_example.dart:9— tdesign-component/example/lib/page/badge/circle_badge_example.dart:9-13 | tdesign-component/example/lib/page/badge/square_badge_example.dart:9-14 — These two members are one piece of code written twice and then edited apart: 5 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 (4 corresponding lines) · ×2
Edited copy of a member (4 corresponding lines) tdesign-component/lib/src/components/indexes/sticky_header/layout_builder_hook.dart:324— tdesign-component/lib/src/components/indexes/sticky_header/layout_builder_hook.dart:324-327 | tdesign-component/lib/src/components/indexes/sticky_header/sticky_header_layout_builder.dart:105-108 — These two members are one piece of code written twice and then edited apart: 4 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 (4 corresponding lines) tdesign-component/example/lib/page/textarea/textarea_disabled_example.dart:9— tdesign-component/example/lib/page/textarea/textarea_disabled_example.dart:9-18 | tdesign-component/example/lib/page/textarea/textarea_label_example.dart:9-12 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (19 lines × 2) tdesign-component/lib/src/components/image/t_image.dart:176— tdesign-component/lib/src/components/image/t_image.dart:176-194 | tdesign-component/lib/src/components/image/t_image.dart:264-282 — both copies are in the same file, so extract the 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 `tdesign-component/lib/src/components/image/t_image.dart:176` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (19 lines × 2) tdesign-component/example/lib/page/message/message_styles_example.dart:23— tdesign-component/example/lib/page/message/message_styles_example.dart:23-41 | tdesign-component/example/lib/page/message/message_types_example.dart:27-45 — before extracting anything, compare `tdesign-component/example/lib/page/message/message_styles_example.dart` and `tdesign-component/example/lib/page/message/message_types_example.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 41 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (12 lines × 3) tdesign-component/lib/src/components/action_sheet/t_action_sheet_grid.dart:115— tdesign-component/lib/src/components/action_sheet/t_action_sheet_grid.dart:115-126 | tdesign-component/lib/src/components/action_sheet/t_action_sheet_grid.dart:406-417 | tdesign-component/lib/src/components/action_sheet/t_action_sheet_list.dart:130-141 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `tdesign-component/lib/src/components/action_sheet/t_action_sheet_grid.dart:115` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (12 lines × 3) tdesign-component/example/lib/page/sidebar/icon_side_bar_example.dart:26— tdesign-component/example/lib/page/sidebar/icon_side_bar_example.dart:26-37 | tdesign-component/example/lib/page/sidebar/navigator_side_bar_example.dart:37-48 | tdesign-component/example/lib/page/sidebar/style_side_bar_example.dart:36-47 — before extracting anything, compare `tdesign-component/example/lib/page/sidebar/icon_side_bar_example.dart` and `tdesign-component/example/lib/page/sidebar/navigator_side_bar_example.dart` as WHOLE FILES: 89% 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 (10–11 lines × 2) tdesign-component/lib/src/components/tabs/t_tab_bar.dart:122— tdesign-component/lib/src/components/tabs/t_tab_bar.dart:122-132 | tdesign-component/lib/src/components/tabs/t_tab_bar.dart:139-148 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `tdesign-component/lib/src/components/tabs/t_tab_bar.dart:122` 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (10–11 lines × 2) tdesign-component/lib/src/components/toast/t_toast.dart:715— tdesign-component/lib/src/components/toast/t_toast.dart:715-725 | tdesign-component/lib/src/components/toast/t_toast.dart:933-942 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `tdesign-component/lib/src/components/toast/t_toast.dart:715` it begins part-way through the construct above it, so those 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· Members sharing a duplicated core (9 members, 50+ identical tokens) · ×2
Members sharing a duplicated core (9 members, 50+ identical tokens) tdesign-component/example/lib/page/calendar/calendar_described_example.dart:176— tdesign-component/example/lib/page/calendar/calendar_described_example.dart:176-183 | tdesign-component/example/lib/page/calendar/calendar_double_described_example.dart:231-238 | tdesign-component/example/lib/page/calendar/calendar_inline_example.dart:57-64 | tdesign-component/example/lib/page/calendar/calendar_limited_example.dart:174-181 | tdesign-component/example/lib/page/calendar/calendar_localized_example.dart:169-176 | tdesign-component/example/lib/page/calendar/calendar_multiple_example.dart:177-184 | tdesign-component/example/lib/page/calendar/calendar_range_example.dart:178-185 | tdesign-component/example/lib/page/calendar/calendar_single_example.dart:172-179 | tdesign-component/example/lib/page/calendar/calendar_switch_mode_example.dart:174-181 — These 9 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 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.
Members sharing a duplicated core (9 members, 50+ identical tokens) tdesign-component/example/lib/page/skeleton/avatar_skeleton_example.dart:9— tdesign-component/example/lib/page/skeleton/avatar_skeleton_example.dart:9-24 | tdesign-component/example/lib/page/skeleton/cell_skeleton_example.dart:9-24 | tdesign-component/example/lib/page/skeleton/combine_skeleton_example.dart:9-24 | tdesign-component/example/lib/page/skeleton/flashed_skeleton_example.dart:9-24 | tdesign-component/example/lib/page/skeleton/gradient_skeleton_example.dart:9-24 | tdesign-component/example/lib/page/skeleton/grid_skeleton_example.dart:9-24 | tdesign-component/example/lib/page/skeleton/image_skeleton_example.dart:9-24 | tdesign-component/example/lib/page/skeleton/paragraph_skeleton_example.dart:9-24 | tdesign-component/example/lib/page/skeleton/text_skeleton_example.dart:9-24 — These 9 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 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· Members sharing a duplicated core (8 members, 50+ identical tokens) · ×2
Members sharing a duplicated core (8 members, 50+ identical tokens) tdesign-component/example/lib/page/calendar/calendar_described_example.dart:221— tdesign-component/example/lib/page/calendar/calendar_described_example.dart:221-255 | tdesign-component/example/lib/page/calendar/calendar_double_described_example.dart:277-311 | tdesign-component/example/lib/page/calendar/calendar_limited_example.dart:219-253 | tdesign-component/example/lib/page/calendar/calendar_localized_example.dart:216-250 | tdesign-component/example/lib/page/calendar/calendar_multiple_example.dart:222-256 | tdesign-component/example/lib/page/calendar/calendar_range_example.dart:223-257 | tdesign-component/example/lib/page/calendar/calendar_single_example.dart:217-251 | tdesign-component/example/lib/page/calendar/calendar_switch_mode_example.dart:219-253 — 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.
Members sharing a duplicated core (8 members, 50+ identical tokens) tdesign-component/example/lib/page/popover/popover_arrow_example.dart:40— tdesign-component/example/lib/page/popover/popover_arrow_example.dart:40-53 | tdesign-component/example/lib/page/popover/popover_bottom_placements_example.dart:94-107 | tdesign-component/example/lib/page/popover/popover_custom_content_example.dart:104-117 | tdesign-component/example/lib/page/popover/popover_left_placements_example.dart:103-116 | tdesign-component/example/lib/page/popover/popover_no_arrow_example.dart:38-51 | tdesign-component/example/lib/page/popover/popover_page.dart:33-46 | tdesign-component/example/lib/page/popover/popover_right_placements_example.dart:103-116 | tdesign-component/example/lib/page/popover/popover_top_placements_example.dart:94-107 — 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 (52 corresponding lines) · ×2
Edited copy of a member (52 corresponding lines) tdesign-component/example/lib/page/drawer/drawer_page.dart:16— tdesign-component/example/lib/page/drawer/drawer_page.dart:16-67 | tdesign-component/example/lib/page/swiper/swiper_page.dart:23-89 — These two members are one piece of code written twice and then edited apart: 52 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 (52 corresponding lines) tdesign-component/example/lib/page/search_bar/search_bar_page.dart:21— tdesign-component/example/lib/page/search_bar/search_bar_page.dart:21-72 | tdesign-component/example/lib/page/switch/switch_page.dart:17-78 — These two members are one piece of code written twice and then edited apart: 52 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 (27 corresponding lines) · ×2
Edited copy of a member (27 corresponding lines) tdesign-component/example/lib/base/example_widget.dart:383— tdesign-component/example/lib/base/example_widget.dart:383-409 | tdesign-component/example/lib/base/example_widget.dart:511-537 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (27 corresponding lines) tdesign-component/example/lib/page/image_viewer/image_viewer_page.dart:13— tdesign-component/example/lib/page/image_viewer/image_viewer_page.dart:13-39 | tdesign-component/example/lib/page/result/result_page.dart:15-49 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (30 corresponding lines) · ×2
Edited copy of a member (30 corresponding lines) tdesign-component/example/lib/page/empty/empty_page.dart:13— tdesign-component/example/lib/page/empty/empty_page.dart:13-42 | tdesign-component/example/lib/page/pull_down_refresh/pull_down_refresh_page.dart:28-69 — These two members are one piece of code written twice and then edited apart: 30 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 (30 corresponding lines) tdesign-component/example/lib/page/divider/divider_page.dart:12— tdesign-component/example/lib/page/divider/divider_page.dart:12-45 | tdesign-component/example/lib/page/footer/footer_page.dart:13-42 — These two members are one piece of code written twice and then edited apart: 30 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, 12+ corresponding lines) · ×2
Edited copies of one member (3 members, 12+ corresponding lines) tdesign-component/example/lib/page/table/table_basic_example.dart:13— tdesign-component/example/lib/page/table/table_basic_example.dart:13-24 | tdesign-component/example/lib/page/table/table_bordered_example.dart:13-24 | tdesign-component/example/lib/page/table/table_stripe_example.dart:13-24 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 12 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, 12+ corresponding lines) tdesign-component/example/lib/page/tabs/tabs_item_with_split2_example.dart:9— tdesign-component/example/lib/page/tabs/tabs_item_with_split2_example.dart:9-20 | tdesign-component/example/lib/page/tabs/tabs_item_with_split3_example.dart:9-21 | tdesign-component/example/lib/page/tabs/tabs_item_with_split4_example.dart:9-22 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 12 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.
Duplicated block (22 lines × 5) tdesign-component/example/lib/page/action_sheet/action_sheet_basic_grid_example.dart:41— tdesign-component/example/lib/page/action_sheet/action_sheet_basic_grid_example.dart:41-62 | tdesign-component/example/lib/page/action_sheet/action_sheet_description_grid_example.dart:42-63 | tdesign-component/example/lib/page/action_sheet/action_sheet_description_scroll_grid_example.dart:92-113 | tdesign-component/example/lib/page/action_sheet/action_sheet_paged_grid_example.dart:79-100 | tdesign-component/example/lib/page/action_sheet/action_sheet_scroll_grid_example.dart:56-77 — before extracting anything, compare `tdesign-component/example/lib/page/action_sheet/action_sheet_basic_grid_example.dart` and `tdesign-component/example/lib/page/action_sheet/action_sheet_description_grid_example.dart` as WHOLE FILES: this scan already matched 7 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 (22 lines × 5) tdesign-component/example/lib/page/action_sheet/action_sheet_basic_grid_example.dart:64— tdesign-component/example/lib/page/action_sheet/action_sheet_basic_grid_example.dart:64-85 | tdesign-component/example/lib/page/action_sheet/action_sheet_description_grid_example.dart:65-86 | tdesign-component/example/lib/page/action_sheet/action_sheet_description_scroll_grid_example.dart:132-153 | tdesign-component/example/lib/page/action_sheet/action_sheet_paged_grid_example.dart:38-59 | tdesign-component/example/lib/page/action_sheet/action_sheet_scroll_grid_example.dart:96-117 — before extracting anything, compare `tdesign-component/example/lib/page/action_sheet/action_sheet_basic_grid_example.dart` and `tdesign-component/example/lib/page/action_sheet/action_sheet_description_grid_example.dart` as WHOLE FILES: this scan already matched 7 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `tdesign-component/example/lib/page/action_sheet/action_sheet_paged_grid_example.dart:61` calls `_showSelection`, `showText` and `tdesign-component/example/lib/page/action_sheet/action_sheet_basic_grid_example.dart:87` 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 (16 lines × 6) tdesign-component/example/lib/page/action_sheet/action_sheet_badge_grid_example.dart:82— tdesign-component/example/lib/page/action_sheet/action_sheet_badge_grid_example.dart:82-97 | tdesign-component/example/lib/page/action_sheet/action_sheet_basic_grid_example.dart:101-116 | tdesign-component/example/lib/page/action_sheet/action_sheet_description_grid_example.dart:102-117 | tdesign-component/example/lib/page/action_sheet/action_sheet_description_scroll_grid_example.dart:115-130 | tdesign-component/example/lib/page/action_sheet/action_sheet_paged_grid_example.dart:102-117 | tdesign-component/example/lib/page/action_sheet/action_sheet_scroll_grid_example.dart:79-94 — before extracting anything, compare `tdesign-component/example/lib/page/action_sheet/action_sheet_badge_grid_example.dart` and `tdesign-component/example/lib/page/action_sheet/action_sheet_basic_grid_example.dart` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 80 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `tdesign-component/example/lib/page/action_sheet/action_sheet_badge_grid_example.dart:78` calls `_showSelection`, `showText` and `tdesign-component/example/lib/page/action_sheet/action_sheet_description_scroll_grid_example.dart:113` 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 (16 lines × 6) tdesign-component/example/lib/page/popover/popover_left_placements_example.dart:18— tdesign-component/example/lib/page/popover/popover_left_placements_example.dart:18-33 | tdesign-component/example/lib/page/popover/popover_left_placements_example.dart:46-61 | tdesign-component/example/lib/page/popover/popover_left_placements_example.dart:74-89 | tdesign-component/example/lib/page/popover/popover_right_placements_example.dart:18-33 | tdesign-component/example/lib/page/popover/popover_right_placements_example.dart:46-61 | tdesign-component/example/lib/page/popover/popover_right_placements_example.dart:74-89 — there are 6 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 6 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `tdesign-component/example/lib/page/popover/popover_left_placements_example.dart:18` 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (14 lines × 8) tdesign-component/example/lib/page/calendar/calendar_described_example.dart:99— tdesign-component/example/lib/page/calendar/calendar_described_example.dart:99-112 | tdesign-component/example/lib/page/calendar/calendar_double_described_example.dart:154-167 | tdesign-component/example/lib/page/calendar/calendar_limited_example.dart:97-110 | tdesign-component/example/lib/page/calendar/calendar_localized_example.dart:99-112 | tdesign-component/example/lib/page/calendar/calendar_multiple_example.dart:100-113 | tdesign-component/example/lib/page/calendar/calendar_range_example.dart:101-114 | tdesign-component/example/lib/page/calendar/calendar_single_example.dart:95-108 | tdesign-component/example/lib/page/calendar/calendar_switch_mode_example.dart:99-112 — before extracting anything, compare `tdesign-component/example/lib/page/calendar/calendar_described_example.dart` and `tdesign-component/example/lib/page/calendar/calendar_double_described_example.dart` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 150 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `tdesign-component/example/lib/page/calendar/calendar_described_example.dart:99` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (14 lines × 8) tdesign-component/example/lib/page/popover/popover_arrow_example.dart:40— tdesign-component/example/lib/page/popover/popover_arrow_example.dart:40-53 | tdesign-component/example/lib/page/popover/popover_bottom_placements_example.dart:94-107 | tdesign-component/example/lib/page/popover/popover_custom_content_example.dart:104-117 | tdesign-component/example/lib/page/popover/popover_left_placements_example.dart:103-116 | tdesign-component/example/lib/page/popover/popover_no_arrow_example.dart:38-51 | tdesign-component/example/lib/page/popover/popover_page.dart:33-46 | tdesign-component/example/lib/page/popover/popover_right_placements_example.dart:103-116 | tdesign-component/example/lib/page/popover/popover_top_placements_example.dart:94-107 — before extracting anything, compare `tdesign-component/example/lib/page/popover/popover_bottom_placements_example.dart` and `tdesign-component/example/lib/page/popover/popover_top_placements_example.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 37 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, `tdesign-component/example/lib/page/popover/popover_custom_content_example.dart:100` calls `TPopoverController` and `tdesign-component/example/lib/page/popover/popover_arrow_example.dart:36` 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 (12 lines × 7) tdesign-component/example/lib/page/navbar/logo_navbar_example.dart:23— tdesign-component/example/lib/page/navbar/logo_navbar_example.dart:23-34 | tdesign-component/example/lib/page/navbar/navbar_right_multi_action_example.dart:16-27 | tdesign-component/example/lib/page/navbar/search_navbar_example.dart:24-35 | tdesign-component/example/lib/page/navbar/title_below_navbar_example.dart:37-48 | tdesign-component/example/lib/page/navbar/title_center_navbar_example.dart:13-24 | tdesign-component/example/lib/page/navbar/title_left_navbar_example.dart:20-31 | tdesign-component/example/lib/page/navbar/title_normal_navbar_example.dart:13-24 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 7 call sites, so a change lands once.
Duplicated block (12 lines × 7) tdesign-component/example/lib/page/dialog/button_dialogs_example.dart:123— tdesign-component/example/lib/page/dialog/button_dialogs_example.dart:123-134 | tdesign-component/example/lib/page/dialog/command_dialog_example.dart:49-60 | tdesign-component/example/lib/page/dialog/confirm_dialogs_example.dart:53-64 | tdesign-component/example/lib/page/dialog/custom_action_dialog_example.dart:36-47 | tdesign-component/example/lib/page/dialog/feedback_dialogs_example.dart:67-78 | tdesign-component/example/lib/page/dialog/image_dialogs_example.dart:73-84 | tdesign-component/example/lib/page/dialog/input_dialogs_example.dart:53-64 — before extracting anything, compare `tdesign-component/example/lib/page/dialog/button_dialogs_example.dart` and `tdesign-component/example/lib/page/dialog/confirm_dialogs_example.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 38 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 7) tdesign-component/example/lib/page/action_sheet/action_sheet_badge_grid_example.dart:85— tdesign-component/example/lib/page/action_sheet/action_sheet_badge_grid_example.dart:85-94 | tdesign-component/example/lib/page/action_sheet/action_sheet_basic_grid_example.dart:104-113 | tdesign-component/example/lib/page/action_sheet/action_sheet_description_grid_example.dart:105-114 | tdesign-component/example/lib/page/action_sheet/action_sheet_description_scroll_grid_example.dart:118-127 | tdesign-component/example/lib/page/action_sheet/action_sheet_description_scroll_grid_example.dart:187-196 | tdesign-component/example/lib/page/action_sheet/action_sheet_paged_grid_example.dart:105-114 | tdesign-component/example/lib/page/action_sheet/action_sheet_scroll_grid_example.dart:82-91 — before extracting anything, compare `tdesign-component/example/lib/page/action_sheet/action_sheet_badge_grid_example.dart` and `tdesign-component/example/lib/page/action_sheet/action_sheet_basic_grid_example.dart` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 80 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 7) tdesign-component/example/lib/page/link/basic_links_example.dart:15— tdesign-component/example/lib/page/link/basic_links_example.dart:15-24 | tdesign-component/example/lib/page/link/color_preset_links_example.dart:41-50 | tdesign-component/example/lib/page/link/disabled_links_example.dart:45-54 | tdesign-component/example/lib/page/link/link_sizes_example.dart:34-43 | tdesign-component/example/lib/page/link/prefix_links_example.dart:19-28 | tdesign-component/example/lib/page/link/suffix_links_example.dart:19-28 | tdesign-component/example/lib/page/link/underline_links_example.dart:15-24 — before extracting anything, compare `tdesign-component/example/lib/page/link/basic_links_example.dart` and `tdesign-component/example/lib/page/link/color_preset_links_example.dart` as WHOLE FILES: 82% 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `tdesign-component/example/lib/page/link/prefix_links_example.dart:15` calls `_link`, `Icon` and `tdesign-component/example/lib/page/link/link_sizes_example.dart:30` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (10 lines × 5) tdesign-component/example/lib/page/dialog/button_dialogs_example.dart:97— tdesign-component/example/lib/page/dialog/button_dialogs_example.dart:97-106 | tdesign-component/example/lib/page/dialog/confirm_dialogs_example.dart:42-51 | tdesign-component/example/lib/page/dialog/feedback_dialogs_example.dart:56-65 | tdesign-component/example/lib/page/dialog/image_dialogs_example.dart:62-71 | tdesign-component/example/lib/page/dialog/input_dialogs_example.dart:42-51 — before extracting anything, compare `tdesign-component/example/lib/page/dialog/button_dialogs_example.dart` and `tdesign-component/example/lib/page/dialog/confirm_dialogs_example.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 38 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 5) tdesign-component/example/lib/page/search_bar/search_bar_action_example.dart:57— tdesign-component/example/lib/page/search_bar/search_bar_action_example.dart:57-66 | tdesign-component/example/lib/page/search_bar/search_bar_base_example.dart:129-138 | tdesign-component/example/lib/page/search_bar/search_bar_center_example.dart:32-41 | tdesign-component/example/lib/page/search_bar/search_bar_max_length_example.dart:37-46 | tdesign-component/example/lib/page/search_bar/search_bar_shape_example.dart:40-49 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 5 call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 3) tdesign-component/example/lib/page/table/table_basic_example.dart:13— tdesign-component/example/lib/page/table/table_basic_example.dart:13-22 | tdesign-component/example/lib/page/table/table_bordered_example.dart:13-22 | tdesign-component/example/lib/page/table/table_stripe_example.dart:13-22 — before extracting anything, compare `tdesign-component/example/lib/page/table/table_basic_example.dart` and `tdesign-component/example/lib/page/table/table_bordered_example.dart` as WHOLE FILES: 82% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `tdesign-component/example/lib/page/table/table_basic_example.dart:13` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 3) tdesign-component/example/lib/page/upload/upload_message_file_example.dart:17— tdesign-component/example/lib/page/upload/upload_message_file_example.dart:17-26 | tdesign-component/example/lib/page/upload/upload_multiple_example.dart:16-25 | tdesign-component/example/lib/page/upload/upload_single_example.dart:16-25 — before extracting anything, compare `tdesign-component/example/lib/page/upload/upload_message_file_example.dart` and `tdesign-component/example/lib/page/upload/upload_multiple_example.dart` as WHOLE FILES: 82% 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 (7 lines × 2) tdesign-component/example/lib/page/tree_select/tree_select_single_example.dart:60— tdesign-component/example/lib/page/tree_select/tree_select_single_example.dart:60-66 | tdesign-component/example/lib/page/tree_select/tree_select_three_columns_example.dart:122-128 — 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) tdesign-component/example/lib/page/checkbox/horizontal_checkbox_example.dart:52— tdesign-component/example/lib/page/checkbox/horizontal_checkbox_example.dart:52-58 | tdesign-component/example/lib/page/checkbox/vertical_checkbox_example.dart:50-56 — 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.
Swallowed exception (empty catch) tdesign-component/lib/src/util/map_ext.dart:167— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) tdesign-component/lib/src/util/string_util.dart:33— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
_TDropdownMenuState._buildOverlay (cyclomatic 42) tdesign-component/lib/src/components/dropdown_menu/t_dropdown_menu.dart:1145— _TDropdownMenuState._buildOverlay has cyclomatic complexity 42 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
TFormItem.build (cyclomatic 39) tdesign-component/lib/src/components/form/t_form_item.dart:74— TFormItem.build has cyclomatic complexity 39 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
TCheckbox.build (cyclomatic 32) tdesign-component/lib/src/components/checkbox/t_check_box.dart:100— TCheckbox.build has cyclomatic complexity 32 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
_TInputShellState.build (cyclomatic 32) tdesign-component/lib/src/components/input/t_input.dart:559— _TInputShellState.build has cyclomatic complexity 32 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
TRadio.build (cyclomatic 32) tdesign-component/lib/src/components/radio/t_radio.dart:137— TRadio.build has cyclomatic complexity 32 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ExampleCodeGenerator.run (cyclomatic 31) tdesign-component/tool/generate_example_code.dart:23— ExampleCodeGenerator.run has cyclomatic complexity 31 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
_TDropdownMenuState.didUpdateWidget (cyclomatic 31) tdesign-component/lib/src/components/dropdown_menu/t_dropdown_menu.dart:518— _TDropdownMenuState.didUpdateWidget has cyclomatic complexity 31 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
_TCellState.build (cyclomatic 30) tdesign-component/lib/src/components/cell/t_cell.dart:85— _TCellState.build has cyclomatic complexity 30 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
_TButtonState.build (cyclomatic 28) tdesign-component/lib/src/components/button/t_button.dart:139— _TButtonState.build has cyclomatic complexity 28 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
TStepsVerticalItem.build (cyclomatic 28) tdesign-component/lib/src/components/steps/t_steps_vertical_item.dart:54— TStepsVerticalItem.build has cyclomatic complexity 28 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
controllerBaseline.loadControllerThemes (cyclomatic 28) tdesign-site/site/utils/controllerBaseline.mjs:10— controllerBaseline.loadControllerThemes has cyclomatic complexity 28 (threshold 15). Most of this is not in the body itself: 11 of the 28 points are its own statements and the rest belongs to 7 function items inside it that branch (cssParts, a function literal at line 46, a function literal at line 50, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
TBadge.build (cyclomatic 27) tdesign-component/lib/src/components/badge/t_badge.dart:215— TBadge.build has cyclomatic complexity 27 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
TTag._resolveColors (cyclomatic 27) tdesign-component/lib/src/components/tag/t_tag.dart:204— TTag._resolveColors has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
TButtonResolve._resolveOutlineColors (cyclomatic 26) tdesign-component/lib/src/components/button/t_button_resolve.dart:250— TButtonResolve._resolveOutlineColors has cyclomatic complexity 26 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
RenderSliverStickyHeader.performLayout (cyclomatic 26) tdesign-component/lib/src/components/indexes/sticky_header/sticky_header_render.dart:184— RenderSliverStickyHeader.performLayout has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
_TDropdownMenuState._open (cyclomatic 25) tdesign-component/lib/src/components/dropdown_menu/t_dropdown_menu.dart:901— _TDropdownMenuState._open has cyclomatic complexity 25 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
_TInputState.build (cyclomatic 25) tdesign-component/lib/src/components/input/t_input.dart:221— _TInputState.build has cyclomatic complexity 25 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
_TIndexesListState.build (cyclomatic 24) tdesign-component/lib/src/components/indexes/t_indexes_list.dart:98— _TIndexesListState.build has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
_TRateState.build (cyclomatic 24) tdesign-component/lib/src/components/rate/t_rate.dart:120— _TRateState.build has cyclomatic complexity 24 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
TSlider.build (cyclomatic 24) tdesign-component/lib/src/components/slider/t_slider.dart:338— TSlider.build has cyclomatic complexity 24 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
TPopupOptions._validatePlacementParams (cyclomatic 23) tdesign-component/lib/src/components/popup/t_popup_options.dart:399— TPopupOptions._validatePlacementParams has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
_TTimeCounterStyle.generateStyle (cyclomatic 23) tdesign-component/lib/src/components/time_counter/t_time_counter_style.dart:53— _TTimeCounterStyle.generateStyle has cyclomatic complexity 23 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
_TIndexesState._scrollToTarget (cyclomatic 22) tdesign-component/lib/src/components/indexes/t_indexes.dart:279— _TIndexesState._scrollToTarget has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
_TCalendarBodyState._getDaysInMonth (cyclomatic 21) tdesign-component/lib/src/components/calendar/t_calendar_body.dart:509— _TCalendarBodyState._getDaysInMonth has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
_TPopoverWidgetState._getChild (cyclomatic 21) tdesign-component/lib/src/components/popover/t_popover_widget.dart:498— _TPopoverWidgetState._getChild has cyclomatic complexity 21 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
TCheckbox._buildIndicator (cyclomatic 20) tdesign-component/lib/src/components/checkbox/t_check_box.dart:282— TCheckbox._buildIndicator has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
TPopupHandle.open (cyclomatic 20) tdesign-component/lib/src/components/popup/t_popup_handle.dart:55— TPopupHandle.open has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
_THorizontalTabBarState.build (cyclomatic 20) tdesign-component/lib/src/components/tabs/t_horizontal_tab_bar.dart:873— _THorizontalTabBarState.build has cyclomatic complexity 20 (threshold 15). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
TProgress.build (cyclomatic 19) tdesign-component/lib/src/components/progress/t_progress.dart:240— TProgress.build has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This is NOT this file's highest cyclomatic complexity: _ProgressIndicatorState._buildLabelWidget (cyclomatic 24) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
TStepsHorizontalItem.build (cyclomatic 19) tdesign-component/lib/src/components/steps/t_steps_horizontal_item.dart:54— TStepsHorizontalItem.build has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
TTag.build (cyclomatic 19) tdesign-component/lib/src/components/tag/t_tag.dart:67— TTag.build has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
TTagThemeData.lerp (cyclomatic 19) tdesign-component/lib/src/components/tag/t_tag_theme_data.dart:228— TTagThemeData.lerp has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
_TTextareaState.build (cyclomatic 19) tdesign-component/lib/src/components/textarea/t_textarea.dart:181— _TTextareaState.build has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
_ExampleManifestCollector._strictModules (cyclomatic 17) tdesign-component/tool/generate_example_code.dart:436— _ExampleManifestCollector._strictModules has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
_TTabBarItemWithBadge._constructItem (cyclomatic 17) tdesign-component/lib/src/components/tabbar/t_tab_bar.dart:899— _TTabBarItemWithBadge._constructItem has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
TTagThemeData.copyWith (cyclomatic 17) tdesign-component/lib/src/components/tag/t_tag_theme_data.dart:160— TTagThemeData.copyWith has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
_ExampleCodeCollector._collect (cyclomatic 16) tdesign-component/tool/generate_example_code.dart:199— _ExampleCodeCollector._collect has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
_TSearchBarState.build (cyclomatic 16) tdesign-component/lib/src/components/search/t_search_bar.dart:165— _TSearchBarState.build has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
_TSideBarState._scrollToItem (cyclomatic 16) tdesign-component/lib/src/components/sidebar/t_sidebar.dart:119— _TSideBarState._scrollToItem has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
_TSwiperState._buildControls (cyclomatic 16) tdesign-component/lib/src/components/swiper/t_swiper.dart:856— _TSwiperState._buildControls has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
_TTabBarState._defaultContentHeight (cyclomatic 16) tdesign-component/lib/src/components/tabbar/t_tab_bar.dart:416— _TTabBarState._defaultContentHeight has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
No assertions: repository copies and runnable migration snippets are synchronized tdesign-site/site/flutter-example-docs/documentation.test.mjs:80— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
TTag._resolveColors (cognitive 62) tdesign-component/lib/src/components/tag/t_tag.dart:204— TTag._resolveColors has cognitive complexity 62 (threshold 15). Drivers by points: ternaries 15 (45 pts), if/else 11 (16 pts), match/switch 1 (nesting depth added 35). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ExampleCodeGenerator.run (cognitive 51) tdesign-component/tool/generate_example_code.dart:23— ExampleCodeGenerator.run has cognitive complexity 51 (threshold 15). Drivers by points: if/else 13 (26 pts), loops 8 (12 pts), boolean chains 7, ternaries 2 (6 pts) (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_TButtonState.build (cognitive 48) tdesign-component/lib/src/components/button/t_button.dart:139— _TButtonState.build has cognitive complexity 48 (threshold 15). Drivers by points: if/else 12 (23 pts), ternaries 10 (19 pts), boolean chains 4, match/switch 1 (2 pts) (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_TIndexesState._scrollToTarget (cognitive 42) tdesign-component/lib/src/components/indexes/t_indexes.dart:279— _TIndexesState._scrollToTarget has cognitive complexity 42 (threshold 15). Drivers by points: if/else 17 (30 pts), boolean chains 5, ternaries 2 (5 pts), loops 1 (2 pts) (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_TDropdownMenuState.didUpdateWidget (cognitive 41) tdesign-component/lib/src/components/dropdown_menu/t_dropdown_menu.dart:518— _TDropdownMenuState.didUpdateWidget has cognitive complexity 41 (threshold 15). Drivers by points: if/else 14 (24 pts), boolean chains 16, ternaries 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TFormItem.build (cognitive 40) tdesign-component/lib/src/components/form/t_form_item.dart:74— TFormItem.build has cognitive complexity 40 (threshold 15). Drivers by points: if/else 13 (17 pts), ternaries 14 (17 pts), match/switch 4, boolean chains 2 (nesting depth added 7). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
_TDropdownMenuState._buildOverlay (cognitive 38) tdesign-component/lib/src/components/dropdown_menu/t_dropdown_menu.dart:1145— _TDropdownMenuState._buildOverlay has cognitive complexity 38 (threshold 15). Drivers by points: ternaries 17, boolean chains 12, if/else 7, match/switch 2. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
_TCalendarBodyState._getDaysInMonth (cognitive 37) tdesign-component/lib/src/components/calendar/t_calendar_body.dart:509— _TCalendarBodyState._getDaysInMonth has cognitive complexity 37 (threshold 15). Drivers by points: if/else 10 (25 pts), boolean chains 6, ternaries 2 (4 pts), loops 2 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TStepsVerticalItem.build (cognitive 37) tdesign-component/lib/src/components/steps/t_steps_vertical_item.dart:54— TStepsVerticalItem.build has cognitive complexity 37 (threshold 15). Drivers by points: if/else 12 (16 pts), ternaries 9 (14 pts), boolean chains 7 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
controllerBaseline.loadControllerThemes (cognitive 36) tdesign-site/site/utils/controllerBaseline.mjs:10— controllerBaseline.loadControllerThemes has cognitive complexity 36 (threshold 15). Drivers by points: if/else 7 (16 pts), boolean chains 8, loops 4 (8 pts), ternaries 4 (nesting depth added 13). Of this number, 21 points are the body's own statements and 15 belong to 7 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_TCellState.build (cognitive 35) tdesign-component/lib/src/components/cell/t_cell.dart:85— _TCellState.build has cognitive complexity 35 (threshold 15). Drivers by points: if/else 14 (21 pts), ternaries 6 (8 pts), boolean chains 4, match/switch 2 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TCheckbox.build (cognitive 35) tdesign-component/lib/src/components/checkbox/t_check_box.dart:100— TCheckbox.build has cognitive complexity 35 (threshold 15). Drivers by points: ternaries 19 (21 pts), boolean chains 7, if/else 6 (7 pts) (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
TRadio.build (cognitive 35) tdesign-component/lib/src/components/radio/t_radio.dart:137— TRadio.build has cognitive complexity 35 (threshold 15). Drivers by points: ternaries 13 (17 pts), if/else 8 (10 pts), boolean chains 6, match/switch 2 (nesting depth added 6). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
_TInputShellState.build (cognitive 34) tdesign-component/lib/src/components/input/t_input.dart:559— _TInputShellState.build has cognitive complexity 34 (threshold 15). Drivers by points: ternaries 16 (18 pts), boolean chains 9, if/else 7 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
RenderSliverStickyHeader.performLayout (cognitive 31) tdesign-component/lib/src/components/indexes/sticky_header/sticky_header_render.dart:184— RenderSliverStickyHeader.performLayout has cognitive complexity 31 (threshold 15). Drivers by points: if/else 9 (14 pts), ternaries 4 (8 pts), boolean chains 5, match/switch 2 (4 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_TTabBarItemWithBadge._constructItem (cognitive 30) tdesign-component/lib/src/components/tabbar/t_tab_bar.dart:899— _TTabBarItemWithBadge._constructItem has cognitive complexity 30 (threshold 15). Drivers by points: ternaries 9 (20 pts), if/else 8 (10 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_ExampleManifestCollector._strictModules (cognitive 29) tdesign-component/tool/generate_example_code.dart:436— _ExampleManifestCollector._strictModules has cognitive complexity 29 (threshold 15). Drivers by points: if/else 9 (21 pts), boolean chains 5, loops 2 (3 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_TIndexesListState.build (cognitive 28) tdesign-component/lib/src/components/indexes/t_indexes_list.dart:98— _TIndexesListState.build has cognitive complexity 28 (threshold 15). Drivers by points: ternaries 9 (12 pts), boolean chains 8, if/else 6 (8 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_TRateState.build (cognitive 28) tdesign-component/lib/src/components/rate/t_rate.dart:120— _TRateState.build has cognitive complexity 28 (threshold 15). Drivers by points: ternaries 13, if/else 7 (10 pts), boolean chains 4, loops 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
_THorizontalTabBarState.build (cognitive 28) tdesign-component/lib/src/components/tabs/t_horizontal_tab_bar.dart:873— _THorizontalTabBarState.build has cognitive complexity 28 (threshold 15). Drivers by points: if/else 11 (17 pts), ternaries 6 (8 pts), boolean chains 2, loops 1 (nesting depth added 8). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
TPopupOptions._validatePlacementParams (cognitive 27) tdesign-component/lib/src/components/popup/t_popup_options.dart:399— TPopupOptions._validatePlacementParams has cognitive complexity 27 (threshold 15). Drivers by points: if/else 11 (20 pts), boolean chains 6, match/switch 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TSlider.build (cognitive 26) tdesign-component/lib/src/components/slider/t_slider.dart:338— TSlider.build has cognitive complexity 26 (threshold 15). Drivers by points: if/else 12 (13 pts), ternaries 8, boolean chains 5 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
_TTabBarState._defaultContentHeight (cognitive 26) tdesign-component/lib/src/components/tabbar/t_tab_bar.dart:416— _TTabBarState._defaultContentHeight has cognitive complexity 26 (threshold 15). Drivers by points: ternaries 8 (18 pts), boolean chains 4, loops 2 (3 pts), if/else 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_TDropdownMenuState._open (cognitive 25) tdesign-component/lib/src/components/dropdown_menu/t_dropdown_menu.dart:901— _TDropdownMenuState._open has cognitive complexity 25 (threshold 15). Drivers by points: boolean chains 14, if/else 8 (9 pts), error handling 1, ternaries 1 (nesting depth added 1). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
_TInputState.build (cognitive 25) tdesign-component/lib/src/components/input/t_input.dart:221— _TInputState.build has cognitive complexity 25 (threshold 15). Drivers by points: ternaries 20, if/else 3, boolean chains 2. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
TBadge.build (cognitive 24) tdesign-component/lib/src/components/badge/t_badge.dart:215— TBadge.build has cognitive complexity 24 (threshold 15). Drivers by points: ternaries 11 (13 pts), boolean chains 6, if/else 3, match/switch 2 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
TStepsHorizontalItem.build (cognitive 24) tdesign-component/lib/src/components/steps/t_steps_horizontal_item.dart:54— TStepsHorizontalItem.build has cognitive complexity 24 (threshold 15). Drivers by points: if/else 10 (13 pts), ternaries 5 (7 pts), boolean chains 4 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TCheckbox._buildIndicator (cognitive 23) tdesign-component/lib/src/components/checkbox/t_check_box.dart:282— TCheckbox._buildIndicator has cognitive complexity 23 (threshold 15). Drivers by points: ternaries 9 (15 pts), boolean chains 5, if/else 2, match/switch 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TTag.build (cognitive 23) tdesign-component/lib/src/components/tag/t_tag.dart:67— TTag.build has cognitive complexity 23 (threshold 15). Drivers by points: ternaries 9 (12 pts), if/else 4 (6 pts), boolean chains 5 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_TSideBarState._scrollToItem (cognitive 22) tdesign-component/lib/src/components/sidebar/t_sidebar.dart:119— _TSideBarState._scrollToItem has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (11 pts), boolean chains 6, loops 2 (3 pts), ternaries 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TSwitch._buildThumb (cognitive 22) tdesign-component/lib/src/components/switch/t_switch.dart:163— TSwitch._buildThumb has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 10 (20 pts), if/else 1, match/switch 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_ExampleCodeCollector._collect (cognitive 21) tdesign-component/tool/generate_example_code.dart:199— _ExampleCodeCollector._collect has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 4, loops 2 (3 pts), ternaries 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_DialogActions.build (cognitive 21) tdesign-component/lib/src/components/dialog/t_dialog.dart:585— _DialogActions.build has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 3 (5 pts), boolean chains 3, ternaries 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TProgress.build (cognitive 21) tdesign-component/lib/src/components/progress/t_progress.dart:240— TProgress.build has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 8, ternaries 4 (7 pts), if/else 6 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
_TSwiperState.didUpdateWidget (cognitive 21) tdesign-component/lib/src/components/swiper/t_swiper.dart:362— _TSwiperState.didUpdateWidget has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (14 pts), ternaries 3 (5 pts), boolean chains 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TButtonResolve._resolveOutlineColors (cognitive 20) tdesign-component/lib/src/components/button/t_button_resolve.dart:250— TButtonResolve._resolveOutlineColors has cognitive complexity 20 (threshold 15). Drivers by points: match/switch 5 (9 pts), if/else 6, ternaries 3 (5 pts) (nesting depth added 6). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
TPopupHandle.open (cognitive 20) tdesign-component/lib/src/components/popup/t_popup_handle.dart:55— TPopupHandle.open has cognitive complexity 20 (threshold 15). Drivers by points: if/else 12 (13 pts), boolean chains 5, ternaries 2 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
_ExampleCodeCollector._standaloneFileSource (cognitive 18) tdesign-component/tool/generate_example_code.dart:263— _ExampleCodeCollector._standaloneFileSource has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (8 pts), loops 6 (8 pts), boolean chains 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_Resolver.expression (cognitive 18) packages/css2token/lib/src/converter.dart:222— _Resolver.expression has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (13 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_TPullDownRefreshState.build (cognitive 18) tdesign-component/lib/src/components/refresh/t_pull_down_refresh.dart:403— _TPullDownRefreshState.build has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 8 (13 pts), if/else 2 (3 pts), loops 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_TSearchBarState.build (cognitive 18) tdesign-component/lib/src/components/search/t_search_bar.dart:165— _TSearchBarState.build has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 7 (8 pts), if/else 6 (7 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
_TSwiperState._buildDots (cognitive 18) tdesign-component/lib/src/components/swiper/t_swiper.dart:742— _TSwiperState._buildDots has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 5 (9 pts), boolean chains 6, if/else 2, loops 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TTagThemeData.lerp (cognitive 18) tdesign-component/lib/src/components/tag/t_tag_theme_data.dart:228— TTagThemeData.lerp has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 10, boolean chains 6, if/else 1, loops 1. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
_TUploadState._pickFiles (cognitive 18) tdesign-component/lib/src/components/upload/t_upload.dart:747— _TUploadState._pickFiles has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (12 pts), boolean chains 4, error handling 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_THorizontalTabBarState._getContentDecorateOuter (cognitive 17) tdesign-component/lib/src/components/tabs/t_horizontal_tab_bar.dart:806— _THorizontalTabBarState._getContentDecorateOuter has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 4 (12 pts), if/else 4 (5 pts) (nesting depth added 9). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
_DateTimePickerWheelState.didUpdateWidget (cognitive 16) tdesign-component/lib/src/components/date_time_picker/t_date_time_picker_wheel.dart:101— _DateTimePickerWheelState.didUpdateWidget has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 8, if/else 3 (5 pts), loops 2 (3 pts) (nesting depth added 3). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
TTagThemeData.copyWith (cognitive 16) tdesign-component/lib/src/components/tag/t_tag_theme_data.dart:160— TTagThemeData.copyWith has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 7, if/else 5, boolean chains 4. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
_TTextareaState.build (cognitive 16) tdesign-component/lib/src/components/textarea/t_textarea.dart:181— _TTextareaState.build has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 9 (10 pts), if/else 2 (3 pts), match/switch 2, boolean chains 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
TInternalInputHint.build (cognitive 16) tdesign-component/lib/src/theme/t_internal_material.dart:815— TInternalInputHint.build has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 7 (13 pts), boolean chains 1, if/else 1, match/switch 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Change coupling: t_check_box_group.dart ↔ t_radio.dart tdesign-component/lib/src/components/checkbox/t_check_box_group.dart:1— `tdesign-component/lib/src/components/checkbox/t_check_box_group.dart` and `tdesign-component/lib/src/components/radio/t_radio.dart` change together 60% of the time (6 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `f2bb756b` fix:TDRadio、TDCheckbox 单选框、多选框多列展示问题 (#841) (at that commit the files were still `tdesign-component/lib/src/components/checkbox/td_check_box_group.dart` and `tdesign-component/lib/src/components/radio/td_radio.dart`); `650de91e` 修改代码规范 (at that commit the files were still `tdesign-component/lib/src/components/checkbox/td_check_box_group.dart` and `tdesign-component/lib/src/components/radio/td_radio.dart`); `a5dabee0` radio和checkbox组件修改,样例修改 (at that commit the files were still `lib/src/components/checkbox/td_check_box_group.dart` and `lib/src/components/radio/td_radio.dart`) — run `git show` on any of them.
D4 · Code Duplication· Edited copy of a member (50 corresponding lines) · ×1
Edited copy of a member (50 corresponding lines) tdesign-component/lib/src/components/slider/t_slider.dart:908— tdesign-component/lib/src/components/slider/t_slider.dart:908-960 | tdesign-component/lib/src/components/slider/t_slider.dart:989-1038 — These two members are one piece of code written twice and then edited apart: 50 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 (41 corresponding lines) · ×1
Edited copy of a member (41 corresponding lines) tdesign-component/lib/src/components/toast/t_toast.dart:705— tdesign-component/lib/src/components/toast/t_toast.dart:705-752 | tdesign-component/lib/src/components/toast/t_toast.dart:754-794 — These two members are one piece of code written twice and then edited apart: 41 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 (36 corresponding lines) · ×1
Edited copy of a member (36 corresponding lines) tdesign-component/lib/src/components/checkbox/t_check_box.dart:429— tdesign-component/lib/src/components/checkbox/t_check_box.dart:429-464 | tdesign-component/lib/src/components/radio/t_radio.dart:376-415 — These two members are one piece of code written twice and then edited apart: 36 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 (24 corresponding lines) · ×1
Edited copy of a member (24 corresponding lines) tdesign-component/lib/src/components/slider/t_slider.dart:805— tdesign-component/lib/src/components/slider/t_slider.dart:805-832 | tdesign-component/lib/src/components/slider/t_slider.dart:856-879 — 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 copy of a member (25 corresponding lines) · ×1
Edited copy of a member (25 corresponding lines) tdesign-component/lib/src/components/slider/t_slider.dart:1079— tdesign-component/lib/src/components/slider/t_slider.dart:1079-1104 | tdesign-component/lib/src/components/slider/t_slider.dart:1122-1146 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (18 corresponding lines) · ×1
Edited copy of a member (18 corresponding lines) tdesign-component/lib/src/components/tabs/t_horizontal_tab_bar.dart:579— tdesign-component/lib/src/components/tabs/t_horizontal_tab_bar.dart:579-599 | tdesign-component/lib/src/components/tabs/t_horizontal_tab_bar.dart:1348-1365 — 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, 11+ corresponding lines) · ×1
Edited copies of one member (3 members, 11+ corresponding lines) tdesign-component/lib/src/components/date_time_picker/t_date_time_picker.dart:202— tdesign-component/lib/src/components/date_time_picker/t_date_time_picker.dart:202-215 | tdesign-component/lib/src/components/date_time_picker/t_date_time_picker_wheel.dart:316-326 | tdesign-component/lib/src/components/tree/t_tree_select.dart:466-479 — These 3 members are one piece of code written 3 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 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 10+ corresponding lines) · ×1
Edited copies of one member (4 members, 10+ corresponding lines) tdesign-component/lib/src/components/collapse/t_collapse.dart:393— tdesign-component/lib/src/components/collapse/t_collapse.dart:393-404 | tdesign-component/lib/src/components/collapse/t_collapse.dart:415-424 | tdesign-component/lib/src/components/drawer/t_drawer_content.dart:189-201 | tdesign-component/lib/src/components/rate/t_rate.dart:310-324 — 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 copies of one member (6 members, 12+ corresponding lines) · ×1
Edited copies of one member (6 members, 12+ corresponding lines) tdesign-component/lib/src/components/progress/t_progress_theme_data.dart:337— tdesign-component/lib/src/components/progress/t_progress_theme_data.dart:337-354 | tdesign-component/lib/src/components/progress/t_progress_theme_data.dart:379-390 | tdesign-component/lib/src/components/progress/t_progress_theme_data.dart:414-425 | tdesign-component/lib/src/components/tag/t_tag_theme_data.dart:422-433 | tdesign-component/lib/src/components/tag/t_tag_theme_data.dart:463-474 | tdesign-component/lib/src/components/tag/t_tag_theme_data.dart:498-509 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 12 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 (4 members, 6+ corresponding lines) · ×1
Edited copies of one member (4 members, 6+ corresponding lines) tdesign-component/lib/src/components/badge/t_badge_theme_data.dart:151— tdesign-component/lib/src/components/badge/t_badge_theme_data.dart:151-156 | tdesign-component/lib/src/components/drawer/t_drawer_theme_data.dart:280-285 | tdesign-component/lib/src/components/notice_bar/t_notice_bar_theme_data.dart:218-223 | tdesign-component/lib/src/components/tabbar/t_tab_bar_theme_data.dart:149-154 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 6 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.
Duplicated block (113 lines × 2) tdesign-component/lib/src/components/steps/t_steps_horizontal_item.dart:54— tdesign-component/lib/src/components/steps/t_steps_horizontal_item.dart:54-166 | tdesign-component/lib/src/components/steps/t_steps_vertical_item.dart:54-166 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `tdesign-component/lib/src/components/steps/t_steps_horizontal_item.dart:54` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (25–26 lines × 2) tdesign-component/lib/src/components/slider/t_slider.dart:458— tdesign-component/lib/src/components/slider/t_slider.dart:458-482 | tdesign-component/lib/src/components/slider/t_slider.dart:639-664 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `tdesign-component/lib/src/components/slider/t_slider.dart:458` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (16 lines × 3) tdesign-component/lib/src/components/image/t_image.dart:180— tdesign-component/lib/src/components/image/t_image.dart:180-195 | tdesign-component/lib/src/components/image/t_image.dart:245-260 | tdesign-component/lib/src/components/image/t_image.dart:268-283 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `tdesign-component/lib/src/components/image/t_image.dart:180` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (68 lines × 2) tdesign-component/lib/src/components/slider/t_slider_theme.dart:58— tdesign-component/lib/src/components/slider/t_slider_theme.dart:58-149 | tdesign-component/lib/src/components/switch/t_switch_theme_data.dart:49-116 — 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `tdesign-component/lib/src/components/switch/t_switch_theme_data.dart:49` calls `_lerpColor` and `tdesign-component/lib/src/components/slider/t_slider_theme.dart:56` does not — after which the two agree again for 5 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (5 lines × 3) tdesign-component/lib/src/components/avatar/t_avatar_theme_data.dart:370— tdesign-component/lib/src/components/avatar/t_avatar_theme_data.dart:370-374 | tdesign-component/lib/src/components/progress/t_progress_theme_data.dart:398-402 | tdesign-component/lib/src/components/tag/t_tag_theme_data.dart:517-521 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
Duplicated block (8 lines × 3) tdesign-component/lib/src/components/loading/t_circle_indicator.dart:57— tdesign-component/lib/src/components/loading/t_circle_indicator.dart:57-64 | tdesign-component/lib/src/components/loading/t_loading.dart:200-207 | tdesign-component/lib/src/components/loading/t_point_indicator.dart:46-53 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
D4 · Code Duplication· Near-duplicate member family (8 members, 98 shared lines) · ×1
Near-duplicate member family (8 members, 98 shared lines) tdesign-component/example/lib/page/calendar/calendar_described_example.dart:46— tdesign-component/example/lib/page/calendar/calendar_described_example.dart:46-172 | tdesign-component/example/lib/page/calendar/calendar_double_described_example.dart:101-227 | tdesign-component/example/lib/page/calendar/calendar_limited_example.dart:44-170 | tdesign-component/example/lib/page/calendar/calendar_localized_example.dart:45-165 | tdesign-component/example/lib/page/calendar/calendar_multiple_example.dart:47-173 | tdesign-component/example/lib/page/calendar/calendar_range_example.dart:48-174 | tdesign-component/example/lib/page/calendar/calendar_single_example.dart:42-168 | tdesign-component/example/lib/page/calendar/calendar_switch_mode_example.dart:46-170 — These 8 members are variants of one another: a block of 98 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.
Near-duplicate member pair (36 shared lines) tdesign-component/example/lib/page/sidebar/sidebar_custom_example.dart:29— tdesign-component/example/lib/page/sidebar/sidebar_custom_example.dart:29-132 | tdesign-component/example/lib/page/sidebar/sidebar_pagination_example.dart:29-107 — These two members are variants of one another: 36 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 (14 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (14 members, 50+ identical tokens) tdesign-component/example/lib/page/popover/popover_arrow_example.dart:15— tdesign-component/example/lib/page/popover/popover_arrow_example.dart:15-36 | tdesign-component/example/lib/page/popover/popover_bottom_placements_example.dart:17-40 | tdesign-component/example/lib/page/popover/popover_bottom_placements_example.dart:42-65 | tdesign-component/example/lib/page/popover/popover_bottom_placements_example.dart:67-90 | tdesign-component/example/lib/page/popover/popover_color_presets_example.dart:10-31 | tdesign-component/example/lib/page/popover/popover_color_presets_example.dart:33-55 | tdesign-component/example/lib/page/popover/popover_color_presets_example.dart:57-79 | tdesign-component/example/lib/page/popover/popover_color_presets_example.dart:81-103 | tdesign-component/example/lib/page/popover/popover_color_presets_example.dart:105-127 | tdesign-component/example/lib/page/popover/popover_color_presets_example.dart:129-151 | tdesign-component/example/lib/page/popover/popover_no_arrow_example.dart:15-34 | tdesign-component/example/lib/page/popover/popover_top_placements_example.dart:17-40 | tdesign-component/example/lib/page/popover/popover_top_placements_example.dart:42-65 | tdesign-component/example/lib/page/popover/popover_top_placements_example.dart:67-90 — 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 (13 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (13 members, 50+ identical tokens) tdesign-component/example/lib/page/action_sheet/action_sheet_badge_grid_example.dart:19— tdesign-component/example/lib/page/action_sheet/action_sheet_badge_grid_example.dart:19-30 | tdesign-component/example/lib/page/action_sheet/action_sheet_badge_list_example.dart:19-30 | tdesign-component/example/lib/page/action_sheet/action_sheet_basic_grid_example.dart:19-30 | tdesign-component/example/lib/page/action_sheet/action_sheet_basic_list_example.dart:19-30 | tdesign-component/example/lib/page/action_sheet/action_sheet_center_list_example.dart:21-32 | tdesign-component/example/lib/page/action_sheet/action_sheet_description_grid_example.dart:20-31 | tdesign-component/example/lib/page/action_sheet/action_sheet_description_list_example.dart:20-31 | tdesign-component/example/lib/page/action_sheet/action_sheet_description_scroll_grid_example.dart:22-33 | tdesign-component/example/lib/page/action_sheet/action_sheet_icon_list_example.dart:19-30 | tdesign-component/example/lib/page/action_sheet/action_sheet_left_list_example.dart:21-32 | tdesign-component/example/lib/page/action_sheet/action_sheet_paged_grid_example.dart:20-31 | tdesign-component/example/lib/page/action_sheet/action_sheet_scroll_grid_example.dart:24-35 | tdesign-component/example/lib/page/action_sheet/action_sheet_status_icon_list_example.dart:43-54 — These 13 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 13 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 13 times.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (4 members, 50+ identical tokens) tdesign-component/example/lib/page/dialog/button_dialogs_example.dart:138— tdesign-component/example/lib/page/dialog/button_dialogs_example.dart:138-153 | tdesign-component/example/lib/page/dialog/confirm_dialogs_example.dart:68-83 | tdesign-component/example/lib/page/dialog/image_dialogs_example.dart:152-167 | tdesign-component/example/lib/page/dialog/input_dialogs_example.dart:90-105 — 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 (97 corresponding lines) · ×1
Edited copy of a member (97 corresponding lines) tdesign-component/example/lib/page/badge/badge_page.dart:22— tdesign-component/example/lib/page/badge/badge_page.dart:22-135 | tdesign-component/example/lib/page/time_counter/time_counter_page.dart:24-120 — These two members are one piece of code written twice and then edited apart: 97 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 (86 corresponding lines) · ×1
Edited copy of a member (86 corresponding lines) tdesign-component/example/lib/page/tabs/tabs_page.dart:24— tdesign-component/example/lib/page/tabs/tabs_page.dart:24-114 | tdesign-component/example/lib/page/toast/toast_page.dart:23-108 — These two members are one piece of code written twice and then edited apart: 86 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, 83+ corresponding lines) · ×1
Edited copies of one member (3 members, 83+ corresponding lines) tdesign-component/example/lib/page/input/input_page.dart:29— tdesign-component/example/lib/page/input/input_page.dart:29-127 | tdesign-component/example/lib/page/rate/rate_page.dart:22-104 | tdesign-component/example/lib/page/textarea/textarea_page.dart:20-102 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 83 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 (78 corresponding lines) · ×1
Edited copy of a member (78 corresponding lines) tdesign-component/example/lib/page/popover/popover_page.dart:48— tdesign-component/example/lib/page/popover/popover_page.dart:48-142 | tdesign-component/example/lib/page/tag/tag_page.dart:23-100 — These two members are one piece of code written twice and then edited apart: 78 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, 69+ corresponding lines) · ×1
Edited copies of one member (3 members, 69+ corresponding lines) tdesign-component/example/lib/page/avatar/avatar_page.dart:25— tdesign-component/example/lib/page/avatar/avatar_page.dart:25-93 | tdesign-component/example/lib/page/progress/progress_page.dart:19-93 | tdesign-component/example/lib/page/steps/steps_page.dart:28-113 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 69 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, 67+ corresponding lines) · ×1
Edited copies of one member (4 members, 67+ corresponding lines) tdesign-component/example/lib/page/calendar/calendar_page.dart:29— tdesign-component/example/lib/page/calendar/calendar_page.dart:29-99 | tdesign-component/example/lib/page/checkbox/checkbox_page.dart:24-94 | tdesign-component/example/lib/page/date_time_picker/date_time_picker_page.dart:24-91 | tdesign-component/example/lib/page/radio/radio_page.dart:23-89 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 67 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 (55 corresponding lines) · ×1
Edited copy of a member (55 corresponding lines) tdesign-component/example/lib/page/notice_bar/notice_bar_page.dart:19— tdesign-component/example/lib/page/notice_bar/notice_bar_page.dart:19-83 | tdesign-component/example/lib/page/upload/upload_page.dart:18-72 — These two members are one piece of code written twice and then edited apart: 55 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 (54 corresponding lines) · ×1
Edited copy of a member (54 corresponding lines) tdesign-component/example/lib/page/cascader/cascader_page.dart:23— tdesign-component/example/lib/page/cascader/cascader_page.dart:23-78 | tdesign-component/example/lib/page/stepper/stepper_page.dart:21-74 — These two members are one piece of code written twice and then edited apart: 54 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 (38 corresponding lines) · ×1
Edited copy of a member (38 corresponding lines) tdesign-component/example/lib/page/indexes/indexes_page.dart:13— tdesign-component/example/lib/page/indexes/indexes_page.dart:13-53 | tdesign-component/example/lib/page/sidebar/sidebar_page.dart:29-66 — These two members are one piece of code written twice and then edited apart: 38 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, 37+ corresponding lines) · ×1
Edited copies of one member (3 members, 37+ corresponding lines) tdesign-component/example/lib/page/collapse/collapse_page.dart:19— tdesign-component/example/lib/page/collapse/collapse_page.dart:19-62 | tdesign-component/example/lib/page/picker/picker_page.dart:19-63 | tdesign-component/example/lib/page/swipe_cell/swipe_cell_page.dart:14-50 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 37 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 28+ corresponding lines) · ×1
Edited copies of one member (3 members, 28+ corresponding lines) tdesign-component/example/lib/page/stepper/stepper_bounds_example.dart:18— tdesign-component/example/lib/page/stepper/stepper_bounds_example.dart:18-45 | tdesign-component/example/lib/page/stepper/stepper_sizes_example.dart:19-53 | tdesign-component/example/lib/page/stepper/stepper_variants_example.dart:19-50 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 28 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (34 corresponding lines) · ×1
Edited copy of a member (34 corresponding lines) tdesign-component/example/lib/page/dropdown_menu/dropdown_menu_page.dart:14— tdesign-component/example/lib/page/dropdown_menu/dropdown_menu_page.dart:14-49 | tdesign-component/example/lib/page/tree_select/tree_select_page.dart:13-46 — These two members are one piece of code written twice and then edited apart: 34 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 (31 corresponding lines) · ×1
Edited copy of a member (31 corresponding lines) tdesign-component/example/lib/page/message/message_page.dart:14— tdesign-component/example/lib/page/message/message_page.dart:14-44 | tdesign-component/example/lib/page/popup/popup_page.dart:14-46 — These two members are one piece of code written twice and then edited apart: 31 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 (26 corresponding lines) · ×1
Edited copy of a member (26 corresponding lines) tdesign-component/example/lib/page/icon/priority_demo_example.dart:12— tdesign-component/example/lib/page/icon/priority_demo_example.dart:12-41 | tdesign-component/example/lib/page/icon/theme_demo_example.dart:12-37 — These two members are one piece of code written twice and then edited apart: 26 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, 32+ corresponding lines) · ×1
Edited copies of one member (3 members, 32+ corresponding lines) tdesign-component/example/lib/page/tag/dark_show_tags_example.dart:23— tdesign-component/example/lib/page/tag/dark_show_tags_example.dart:23-55 | tdesign-component/example/lib/page/tag/dark_show_tags_example.dart:57-88 | tdesign-component/example/lib/page/tag/dark_show_tags_example.dart:90-121 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 32 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 (23 corresponding lines) · ×1
Edited copy of a member (23 corresponding lines) tdesign-component/example/lib/page/popover/popover_page.dart:389— tdesign-component/example/lib/page/popover/popover_page.dart:389-411 | tdesign-component/example/lib/page/popover/popover_page.dart:413-442 — These two members are one piece of code written twice and then edited apart: 23 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) tdesign-component/example/lib/page/input/input_align_example.dart:9— tdesign-component/example/lib/page/input/input_align_example.dart:9-34 | tdesign-component/example/lib/page/input/input_basic_example.dart:14-35 — 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 copies of one member (4 members, 17+ corresponding lines) · ×1
Edited copies of one member (4 members, 17+ corresponding lines) tdesign-component/example/lib/page/swiper/controls_swiper_example.dart:9— tdesign-component/example/lib/page/swiper/controls_swiper_example.dart:9-25 | tdesign-component/example/lib/page/swiper/dots_bar_swiper_example.dart:9-25 | tdesign-component/example/lib/page/swiper/dots_swiper_example.dart:9-25 | tdesign-component/example/lib/page/swiper/fraction_swiper_example.dart:9-30 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 17 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 copies of one member (5 members, 15+ corresponding lines) · ×1
Edited copies of one member (5 members, 15+ corresponding lines) tdesign-component/example/lib/page/calendar/calendar_limited_example.dart:15— tdesign-component/example/lib/page/calendar/calendar_limited_example.dart:15-31 | tdesign-component/example/lib/page/calendar/calendar_localized_example.dart:15-32 | tdesign-component/example/lib/page/calendar/calendar_multiple_example.dart:16-30 | tdesign-component/example/lib/page/calendar/calendar_single_example.dart:15-29 | tdesign-component/example/lib/page/calendar/calendar_switch_mode_example.dart:16-33 — These 5 members are one piece of code written 5 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 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (5 members, 13+ corresponding lines) · ×1
Edited copies of one member (5 members, 13+ corresponding lines) tdesign-component/example/lib/page/slider/slider_labeled_example.dart:13— tdesign-component/example/lib/page/slider/slider_labeled_example.dart:13-29 | tdesign-component/example/lib/page/slider/slider_range_example.dart:13-25 | tdesign-component/example/lib/page/slider/slider_scale_example.dart:13-30 | tdesign-component/example/lib/page/slider/slider_scale_range_example.dart:19-37 | tdesign-component/example/lib/page/slider/slider_single_example.dart:13-25 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 13 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 copy of a member (19 corresponding lines) · ×1
Edited copy of a member (19 corresponding lines) tdesign-component/example/lib/page/stepper/stepper_base_example.dart:17— tdesign-component/example/lib/page/stepper/stepper_base_example.dart:17-36 | tdesign-component/example/lib/page/stepper/stepper_disabled_example.dart:10-28 — 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 copies of one member (4 members, 18+ corresponding lines) · ×1
Edited copies of one member (4 members, 18+ corresponding lines) tdesign-component/example/lib/page/toast/fail_toast_example.dart:9— tdesign-component/example/lib/page/toast/fail_toast_example.dart:9-26 | tdesign-component/example/lib/page/toast/success_toast_example.dart:9-26 | tdesign-component/example/lib/page/toast/vertical_icon_toast_example.dart:9-27 | tdesign-component/example/lib/page/toast/warning_toast_example.dart:9-26 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 18 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 copies of one member (3 members, 15+ corresponding lines) · ×1
Edited copies of one member (3 members, 15+ corresponding lines) tdesign-component/example/lib/page/popover/popover_bottom_placements_example.dart:109— tdesign-component/example/lib/page/popover/popover_bottom_placements_example.dart:109-123 | tdesign-component/example/lib/page/popover/popover_right_placements_example.dart:118-132 | tdesign-component/example/lib/page/popover/popover_top_placements_example.dart:109-123 — These 3 members are one piece of code written 3 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 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) tdesign-component/example/lib/page/button/disable_primary_fill_button_example.dart:59— tdesign-component/example/lib/page/button/disable_primary_fill_button_example.dart:59-75 | tdesign-component/example/lib/page/button/primary_fill_button_example.dart:62-79 | tdesign-component/example/lib/page/button/rectangle_icon_button_example.dart:45-59 | tdesign-component/example/lib/page/tag/dark_show_tags_example.dart:123-140 — 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 (16 corresponding lines) · ×1
Edited copy of a member (16 corresponding lines) tdesign-component/example/lib/page/button/large_button_example.dart:52— tdesign-component/example/lib/page/button/large_button_example.dart:52-67 | tdesign-component/example/lib/page/button/primary_ghost_button_example.dart:42-58 — These two members are one piece of code written twice and then edited apart: 16 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, 13+ corresponding lines) · ×1
Edited copies of one member (3 members, 13+ corresponding lines) tdesign-component/example/lib/page/picker/picker_area_example.dart:14— tdesign-component/example/lib/page/picker/picker_area_example.dart:14-26 | tdesign-component/example/lib/page/picker/picker_base_example.dart:14-26 | tdesign-component/example/lib/page/picker/picker_time_example.dart:14-26 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 14+ corresponding lines) · ×1
Edited copies of one member (3 members, 14+ corresponding lines) tdesign-component/example/lib/page/backtop/backtop_circle_trigger_example.dart:11— tdesign-component/example/lib/page/backtop/backtop_circle_trigger_example.dart:11-24 | tdesign-component/example/lib/page/backtop/backtop_half_round_trigger_example.dart:11-24 | tdesign-component/example/lib/page/toast/hide_toast_example.dart:9-23 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 14 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) tdesign-component/example/lib/page/tabs/tabs_item_with_line_example.dart:9— tdesign-component/example/lib/page/tabs/tabs_item_with_line_example.dart:9-17 | tdesign-component/example/lib/page/tabs/tabs_item_with_size_large_example.dart:9-20 | tdesign-component/example/lib/page/tabs/tabs_item_with_size_small_example.dart:9-17 | tdesign-component/example/lib/page/tabs/tabs_item_with_status_example.dart:9-16 | tdesign-component/example/lib/page/tabs/tabs_item_with_tag_example.dart:9-20 — 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 (3 members, 8+ corresponding lines) · ×1
Edited copies of one member (3 members, 8+ corresponding lines) tdesign-component/example/lib/page/date_time_picker/date_time_picker_title_example.dart:16— tdesign-component/example/lib/page/date_time_picker/date_time_picker_title_example.dart:16-23 | tdesign-component/example/lib/page/date_time_picker/date_time_picker_week_example.dart:15-22 | tdesign-component/example/lib/page/date_time_picker/date_time_picker_without_title_example.dart:16-24 — 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 (3 members, 9+ corresponding lines) · ×1
Edited copies of one member (3 members, 9+ corresponding lines) tdesign-component/example/lib/page/action_sheet/action_sheet_center_list_example.dart:9— tdesign-component/example/lib/page/action_sheet/action_sheet_center_list_example.dart:9-19 | tdesign-component/example/lib/page/action_sheet/action_sheet_icon_list_example.dart:9-17 | tdesign-component/example/lib/page/action_sheet/action_sheet_left_list_example.dart:9-19 — 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.
Duplicated block (35 lines × 8) tdesign-component/example/lib/page/calendar/calendar_described_example.dart:221— tdesign-component/example/lib/page/calendar/calendar_described_example.dart:221-255 | tdesign-component/example/lib/page/calendar/calendar_double_described_example.dart:277-311 | tdesign-component/example/lib/page/calendar/calendar_limited_example.dart:219-253 | tdesign-component/example/lib/page/calendar/calendar_localized_example.dart:216-250 | tdesign-component/example/lib/page/calendar/calendar_multiple_example.dart:222-256 | tdesign-component/example/lib/page/calendar/calendar_range_example.dart:223-257 | tdesign-component/example/lib/page/calendar/calendar_single_example.dart:217-251 | tdesign-component/example/lib/page/calendar/calendar_switch_mode_example.dart:219-253 — before extracting anything, compare `tdesign-component/example/lib/page/calendar/calendar_described_example.dart` and `tdesign-component/example/lib/page/calendar/calendar_double_described_example.dart` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 150 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 (53 lines × 8) tdesign-component/example/lib/page/calendar/calendar_described_example.dart:46— tdesign-component/example/lib/page/calendar/calendar_described_example.dart:46-98 | tdesign-component/example/lib/page/calendar/calendar_double_described_example.dart:101-153 | tdesign-component/example/lib/page/calendar/calendar_limited_example.dart:44-96 | tdesign-component/example/lib/page/calendar/calendar_localized_example.dart:45-97 | tdesign-component/example/lib/page/calendar/calendar_multiple_example.dart:47-99 | tdesign-component/example/lib/page/calendar/calendar_range_example.dart:48-100 | tdesign-component/example/lib/page/calendar/calendar_single_example.dart:42-94 | tdesign-component/example/lib/page/calendar/calendar_switch_mode_example.dart:46-98 — before extracting anything, compare `tdesign-component/example/lib/page/calendar/calendar_described_example.dart` and `tdesign-component/example/lib/page/calendar/calendar_double_described_example.dart` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 150 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `tdesign-component/example/lib/page/calendar/calendar_described_example.dart:46` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `tdesign-component/example/lib/page/calendar/calendar_described_example.dart:44` calls `DateTime` and `tdesign-component/example/lib/page/calendar/calendar_range_example.dart:46` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (31–32 lines × 8) tdesign-component/example/lib/page/calendar/calendar_described_example.dart:129— tdesign-component/example/lib/page/calendar/calendar_described_example.dart:129-160 | tdesign-component/example/lib/page/calendar/calendar_double_described_example.dart:184-215 | tdesign-component/example/lib/page/calendar/calendar_limited_example.dart:127-158 | tdesign-component/example/lib/page/calendar/calendar_localized_example.dart:129-159 | tdesign-component/example/lib/page/calendar/calendar_multiple_example.dart:130-161 | tdesign-component/example/lib/page/calendar/calendar_range_example.dart:131-162 | tdesign-component/example/lib/page/calendar/calendar_single_example.dart:125-156 | tdesign-component/example/lib/page/calendar/calendar_switch_mode_example.dart:127-158 — before extracting anything, compare `tdesign-component/example/lib/page/calendar/calendar_described_example.dart` and `tdesign-component/example/lib/page/calendar/calendar_double_described_example.dart` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 150 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `tdesign-component/example/lib/page/calendar/calendar_described_example.dart:129` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (22 lines × 3) tdesign-component/example/lib/page/action_sheet/action_sheet_center_list_example.dart:34— tdesign-component/example/lib/page/action_sheet/action_sheet_center_list_example.dart:34-55 | tdesign-component/example/lib/page/action_sheet/action_sheet_icon_list_example.dart:32-53 | tdesign-component/example/lib/page/action_sheet/action_sheet_left_list_example.dart:34-55 — before extracting anything, compare `tdesign-component/example/lib/page/action_sheet/action_sheet_center_list_example.dart` and `tdesign-component/example/lib/page/action_sheet/action_sheet_icon_list_example.dart` 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 (21 lines × 3) tdesign-component/example/lib/page/sidebar/icon_side_bar_example.dart:39— tdesign-component/example/lib/page/sidebar/icon_side_bar_example.dart:39-59 | tdesign-component/example/lib/page/sidebar/navigator_side_bar_example.dart:50-70 | tdesign-component/example/lib/page/sidebar/style_side_bar_example.dart:49-69 — before extracting anything, compare `tdesign-component/example/lib/page/sidebar/icon_side_bar_example.dart` and `tdesign-component/example/lib/page/sidebar/navigator_side_bar_example.dart` as WHOLE FILES: 89% 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 (20 lines × 7) tdesign-component/example/lib/page/link/basic_links_example.dart:26— tdesign-component/example/lib/page/link/basic_links_example.dart:26-45 | tdesign-component/example/lib/page/link/color_preset_links_example.dart:52-71 | tdesign-component/example/lib/page/link/disabled_links_example.dart:56-75 | tdesign-component/example/lib/page/link/link_sizes_example.dart:45-64 | tdesign-component/example/lib/page/link/prefix_links_example.dart:30-49 | tdesign-component/example/lib/page/link/suffix_links_example.dart:30-49 | tdesign-component/example/lib/page/link/underline_links_example.dart:26-45 — before extracting anything, compare `tdesign-component/example/lib/page/link/basic_links_example.dart` and `tdesign-component/example/lib/page/link/color_preset_links_example.dart` as WHOLE FILES: 82% 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 (19–20 lines × 6) tdesign-component/example/lib/page/action_sheet/action_sheet_badge_grid_example.dart:38— tdesign-component/example/lib/page/action_sheet/action_sheet_badge_grid_example.dart:38-56 | tdesign-component/example/lib/page/action_sheet/action_sheet_basic_grid_example.dart:42-61 | tdesign-component/example/lib/page/action_sheet/action_sheet_description_grid_example.dart:43-62 | tdesign-component/example/lib/page/action_sheet/action_sheet_description_scroll_grid_example.dart:93-112 | tdesign-component/example/lib/page/action_sheet/action_sheet_paged_grid_example.dart:80-99 | tdesign-component/example/lib/page/action_sheet/action_sheet_scroll_grid_example.dart:57-76 — before extracting anything, compare `tdesign-component/example/lib/page/action_sheet/action_sheet_badge_grid_example.dart` and `tdesign-component/example/lib/page/action_sheet/action_sheet_basic_grid_example.dart` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 80 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `tdesign-component/example/lib/page/action_sheet/action_sheet_badge_grid_example.dart:38` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (19–20 lines × 2) tdesign-component/example/lib/page/sidebar/sidebar_anchor_example.dart:176— tdesign-component/example/lib/page/sidebar/sidebar_anchor_example.dart:176-195 | tdesign-component/example/lib/page/sidebar/sidebar_custom_example.dart:75-93 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `tdesign-component/example/lib/page/sidebar/sidebar_custom_example.dart:75` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 9) tdesign-component/example/lib/page/skeleton/avatar_skeleton_example.dart:9— tdesign-component/example/lib/page/skeleton/avatar_skeleton_example.dart:9-24 | tdesign-component/example/lib/page/skeleton/cell_skeleton_example.dart:9-24 | tdesign-component/example/lib/page/skeleton/combine_skeleton_example.dart:9-24 | tdesign-component/example/lib/page/skeleton/flashed_skeleton_example.dart:9-24 | tdesign-component/example/lib/page/skeleton/gradient_skeleton_example.dart:9-24 | tdesign-component/example/lib/page/skeleton/grid_skeleton_example.dart:9-24 | tdesign-component/example/lib/page/skeleton/image_skeleton_example.dart:9-24 | tdesign-component/example/lib/page/skeleton/paragraph_skeleton_example.dart:9-24 | tdesign-component/example/lib/page/skeleton/text_skeleton_example.dart:9-24 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 9 call sites, so a change lands once.
Duplicated block (16 lines × 5) tdesign-component/example/lib/page/upload/upload_message_file_example.dart:49— tdesign-component/example/lib/page/upload/upload_message_file_example.dart:49-64 | tdesign-component/example/lib/page/upload/upload_multiple_example.dart:48-63 | tdesign-component/example/lib/page/upload/upload_single_example.dart:27-42 | tdesign-component/example/lib/page/upload/upload_status_example.dart:55-70 | tdesign-component/example/lib/page/upload/upload_tile_example.dart:49-64 — before extracting anything, compare `tdesign-component/example/lib/page/upload/upload_message_file_example.dart` and `tdesign-component/example/lib/page/upload/upload_multiple_example.dart` as WHOLE FILES: 82% 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (16 lines × 4) tdesign-component/example/lib/page/dialog/button_dialogs_example.dart:138— tdesign-component/example/lib/page/dialog/button_dialogs_example.dart:138-153 | tdesign-component/example/lib/page/dialog/confirm_dialogs_example.dart:68-83 | tdesign-component/example/lib/page/dialog/image_dialogs_example.dart:152-167 | tdesign-component/example/lib/page/dialog/input_dialogs_example.dart:90-105 — before extracting anything, compare `tdesign-component/example/lib/page/dialog/button_dialogs_example.dart` and `tdesign-component/example/lib/page/dialog/confirm_dialogs_example.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 38 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (15 lines × 3) tdesign-component/example/lib/page/calendar/calendar_page.dart:32— tdesign-component/example/lib/page/calendar/calendar_page.dart:32-46 | tdesign-component/example/lib/page/date_time_picker/date_time_picker_page.dart:26-40 | tdesign-component/example/lib/page/picker/picker_page.dart:22-36 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `tdesign-component/example/lib/page/calendar/calendar_page.dart:32` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13–14 lines × 2) tdesign-component/example/lib/page/skeleton/cell_skeleton_example.dart:32— tdesign-component/example/lib/page/skeleton/cell_skeleton_example.dart:32-44 | tdesign-component/example/lib/page/skeleton/cell_skeleton_example.dart:62-75 — both copies are in the same file, so extract the 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 `tdesign-component/example/lib/page/skeleton/cell_skeleton_example.dart:32` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 12) tdesign-component/example/lib/page/popover/popover_bottom_placements_example.dart:18— tdesign-component/example/lib/page/popover/popover_bottom_placements_example.dart:18-30 | tdesign-component/example/lib/page/popover/popover_bottom_placements_example.dart:43-55 | tdesign-component/example/lib/page/popover/popover_bottom_placements_example.dart:68-80 | tdesign-component/example/lib/page/popover/popover_color_presets_example.dart:11-23 | tdesign-component/example/lib/page/popover/popover_color_presets_example.dart:34-46 | tdesign-component/example/lib/page/popover/popover_color_presets_example.dart:58-70 | tdesign-component/example/lib/page/popover/popover_color_presets_example.dart:82-94 | tdesign-component/example/lib/page/popover/popover_color_presets_example.dart:106-118 | tdesign-component/example/lib/page/popover/popover_color_presets_example.dart:130-142 | tdesign-component/example/lib/page/popover/popover_top_placements_example.dart:18-30 | tdesign-component/example/lib/page/popover/popover_top_placements_example.dart:43-55 | tdesign-component/example/lib/page/popover/popover_top_placements_example.dart:68-80 — before extracting anything, compare `tdesign-component/example/lib/page/popover/popover_bottom_placements_example.dart` and `tdesign-component/example/lib/page/popover/popover_top_placements_example.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 37 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `tdesign-component/example/lib/page/popover/popover_bottom_placements_example.dart:18` 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (13 lines × 6) tdesign-component/example/lib/page/action_sheet/action_sheet_badge_grid_example.dart:99— tdesign-component/example/lib/page/action_sheet/action_sheet_badge_grid_example.dart:99-111 | tdesign-component/example/lib/page/action_sheet/action_sheet_basic_grid_example.dart:87-99 | tdesign-component/example/lib/page/action_sheet/action_sheet_description_grid_example.dart:88-100 | tdesign-component/example/lib/page/action_sheet/action_sheet_description_scroll_grid_example.dart:155-167 | tdesign-component/example/lib/page/action_sheet/action_sheet_paged_grid_example.dart:65-77 | tdesign-component/example/lib/page/action_sheet/action_sheet_scroll_grid_example.dart:119-131 — before extracting anything, compare `tdesign-component/example/lib/page/action_sheet/action_sheet_badge_grid_example.dart` and `tdesign-component/example/lib/page/action_sheet/action_sheet_basic_grid_example.dart` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 80 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, `tdesign-component/example/lib/page/action_sheet/action_sheet_paged_grid_example.dart:61` calls `_showSelection`, `showText` and `tdesign-component/example/lib/page/action_sheet/action_sheet_basic_grid_example.dart:85` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (13 lines × 3) tdesign-component/example/lib/page/fab/fab_draggable_example.dart:24— tdesign-component/example/lib/page/fab/fab_draggable_example.dart:24-36 | tdesign-component/example/lib/page/fab/fab_icon_only_example.dart:18-30 | tdesign-component/example/lib/page/fab/fab_icon_text_example.dart:22-34 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
Duplicated block (12 lines × 13) tdesign-component/example/lib/page/action_sheet/action_sheet_badge_grid_example.dart:19— tdesign-component/example/lib/page/action_sheet/action_sheet_badge_grid_example.dart:19-30 | tdesign-component/example/lib/page/action_sheet/action_sheet_badge_list_example.dart:19-30 | tdesign-component/example/lib/page/action_sheet/action_sheet_basic_grid_example.dart:19-30 | tdesign-component/example/lib/page/action_sheet/action_sheet_basic_list_example.dart:19-30 | tdesign-component/example/lib/page/action_sheet/action_sheet_center_list_example.dart:21-32 | tdesign-component/example/lib/page/action_sheet/action_sheet_description_grid_example.dart:20-31 | tdesign-component/example/lib/page/action_sheet/action_sheet_description_list_example.dart:20-31 | tdesign-component/example/lib/page/action_sheet/action_sheet_description_scroll_grid_example.dart:22-33 | tdesign-component/example/lib/page/action_sheet/action_sheet_icon_list_example.dart:19-30 | tdesign-component/example/lib/page/action_sheet/action_sheet_left_list_example.dart:21-32 | tdesign-component/example/lib/page/action_sheet/action_sheet_paged_grid_example.dart:20-31 | tdesign-component/example/lib/page/action_sheet/action_sheet_scroll_grid_example.dart:24-35 | tdesign-component/example/lib/page/action_sheet/action_sheet_status_icon_list_example.dart:43-54 — before extracting anything, compare `tdesign-component/example/lib/page/action_sheet/action_sheet_badge_grid_example.dart` and `tdesign-component/example/lib/page/action_sheet/action_sheet_basic_grid_example.dart` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 80 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 14) tdesign-component/example/lib/page/popover/popover_arrow_example.dart:19— tdesign-component/example/lib/page/popover/popover_arrow_example.dart:19-28 | tdesign-component/example/lib/page/popover/popover_bottom_placements_example.dart:22-31 | tdesign-component/example/lib/page/popover/popover_bottom_placements_example.dart:47-56 | tdesign-component/example/lib/page/popover/popover_bottom_placements_example.dart:72-81 | tdesign-component/example/lib/page/popover/popover_color_presets_example.dart:15-24 | tdesign-component/example/lib/page/popover/popover_color_presets_example.dart:38-47 | tdesign-component/example/lib/page/popover/popover_color_presets_example.dart:62-71 | tdesign-component/example/lib/page/popover/popover_color_presets_example.dart:86-95 | tdesign-component/example/lib/page/popover/popover_color_presets_example.dart:110-119 | tdesign-component/example/lib/page/popover/popover_color_presets_example.dart:134-143 | tdesign-component/example/lib/page/popover/popover_no_arrow_example.dart:17-26 | tdesign-component/example/lib/page/popover/popover_top_placements_example.dart:22-31 | tdesign-component/example/lib/page/popover/popover_top_placements_example.dart:47-56 | tdesign-component/example/lib/page/popover/popover_top_placements_example.dart:72-81 — before extracting anything, compare `tdesign-component/example/lib/page/popover/popover_bottom_placements_example.dart` and `tdesign-component/example/lib/page/popover/popover_top_placements_example.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 37 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `tdesign-component/example/lib/page/popover/popover_arrow_example.dart:19` 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `tdesign-component/example/lib/page/popover/popover_color_presets_example.dart:36` calls `all` and `tdesign-component/example/lib/page/popover/popover_arrow_example.dart:17` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8 lines × 9) tdesign-component/example/lib/page/calendar/calendar_described_example.dart:176— tdesign-component/example/lib/page/calendar/calendar_described_example.dart:176-183 | tdesign-component/example/lib/page/calendar/calendar_double_described_example.dart:231-238 | tdesign-component/example/lib/page/calendar/calendar_inline_example.dart:57-64 | tdesign-component/example/lib/page/calendar/calendar_limited_example.dart:174-181 | tdesign-component/example/lib/page/calendar/calendar_localized_example.dart:169-176 | tdesign-component/example/lib/page/calendar/calendar_multiple_example.dart:177-184 | tdesign-component/example/lib/page/calendar/calendar_range_example.dart:178-185 | tdesign-component/example/lib/page/calendar/calendar_single_example.dart:172-179 | tdesign-component/example/lib/page/calendar/calendar_switch_mode_example.dart:174-181 — before extracting anything, compare `tdesign-component/example/lib/page/calendar/calendar_described_example.dart` and `tdesign-component/example/lib/page/calendar/calendar_double_described_example.dart` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 150 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 3) tdesign-component/example/lib/page/sidebar/sidebar_anchor_example.dart:139— tdesign-component/example/lib/page/sidebar/sidebar_anchor_example.dart:139-145 | tdesign-component/example/lib/page/sidebar/sidebar_custom_example.dart:32-38 | tdesign-component/example/lib/page/sidebar/sidebar_pagination_example.dart:32-38 — before extracting anything, compare `tdesign-component/example/lib/page/sidebar/sidebar_custom_example.dart` and `tdesign-component/example/lib/page/sidebar/sidebar_pagination_example.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 36 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `tdesign-component/example/lib/page/sidebar/sidebar_anchor_example.dart:139` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 7) tdesign-component/example/lib/page/calendar/calendar_described_example.dart:35— tdesign-component/example/lib/page/calendar/calendar_described_example.dart:35-42 | tdesign-component/example/lib/page/calendar/calendar_double_described_example.dart:90-97 | tdesign-component/example/lib/page/calendar/calendar_limited_example.dart:33-40 | tdesign-component/example/lib/page/calendar/calendar_localized_example.dart:34-41 | tdesign-component/example/lib/page/calendar/calendar_multiple_example.dart:32-39 | tdesign-component/example/lib/page/calendar/calendar_single_example.dart:31-38 | tdesign-component/example/lib/page/calendar/calendar_switch_mode_example.dart:35-42 — before extracting anything, compare `tdesign-component/example/lib/page/calendar/calendar_described_example.dart` and `tdesign-component/example/lib/page/calendar/calendar_double_described_example.dart` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 150 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 8) tdesign-component/example/lib/page/rate/rate_action_example.dart:72— tdesign-component/example/lib/page/rate/rate_action_example.dart:72-80 | tdesign-component/example/lib/page/rate/rate_basic_example.dart:45-53 | tdesign-component/example/lib/page/rate/rate_color_example.dart:78-86 | tdesign-component/example/lib/page/rate/rate_count_example.dart:45-53 | tdesign-component/example/lib/page/rate/rate_custom_example.dart:53-61 | tdesign-component/example/lib/page/rate/rate_show_text_example.dart:93-101 | tdesign-component/example/lib/page/rate/rate_size_example.dart:64-72 | tdesign-component/example/lib/page/rate/rate_third_party_icon_example.dart:49-57 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 8 call sites, so a change lands once.
Duplicated block (8 lines × 4) tdesign-component/example/lib/page/swipe_cell/swipe_cell_swiper_cell_example.dart:57— tdesign-component/example/lib/page/swipe_cell/swipe_cell_swiper_cell_example.dart:57-64 | tdesign-component/example/lib/page/swipe_cell/swipe_cell_swiper_icon_cell_example.dart:51-58 | tdesign-component/example/lib/page/swipe_cell/swipe_cell_swiper_right_cell_example.dart:18-25 | tdesign-component/example/lib/page/swipe_cell/swipe_cell_swiper_right_left_cell_example.dart:21-28 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 4 call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11 lines × 4) tdesign-component/example/lib/page/switch/switch_basic_example.dart:45— tdesign-component/example/lib/page/switch/switch_basic_example.dart:45-55 | tdesign-component/example/lib/page/switch/switch_color_example.dart:50-60 | tdesign-component/example/lib/page/switch/switch_label_example.dart:61-71 | tdesign-component/example/lib/page/switch/switch_sizes_example.dart:63-73 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 4 call sites, so a change lands once.
Duplicated block (9 lines × 4) tdesign-component/example/lib/page/action_sheet/action_sheet_badge_grid_example.dart:9— tdesign-component/example/lib/page/action_sheet/action_sheet_badge_grid_example.dart:9-17 | tdesign-component/example/lib/page/action_sheet/action_sheet_badge_list_example.dart:9-17 | tdesign-component/example/lib/page/action_sheet/action_sheet_basic_grid_example.dart:9-17 | tdesign-component/example/lib/page/action_sheet/action_sheet_basic_list_example.dart:9-17 — before extracting anything, compare `tdesign-component/example/lib/page/action_sheet/action_sheet_badge_grid_example.dart` and `tdesign-component/example/lib/page/action_sheet/action_sheet_basic_grid_example.dart` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 80 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 4) tdesign-component/example/lib/page/date_time_picker/date_time_picker_date_example.dart:15— tdesign-component/example/lib/page/date_time_picker/date_time_picker_date_example.dart:15-21 | tdesign-component/example/lib/page/date_time_picker/date_time_picker_minute_example.dart:16-22 | tdesign-component/example/lib/page/date_time_picker/date_time_picker_month_example.dart:16-22 | tdesign-component/example/lib/page/date_time_picker/date_time_picker_second_example.dart:16-22 — before extracting anything, compare `tdesign-component/example/lib/page/date_time_picker/date_time_picker_date_example.dart` and `tdesign-component/example/lib/page/date_time_picker/date_time_picker_minute_example.dart` 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 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.
Duplicated block (6 lines × 3) tdesign-component/example/lib/page/message/message_styles_example.dart:43— tdesign-component/example/lib/page/message/message_styles_example.dart:43-48 | tdesign-component/example/lib/page/message/message_types_example.dart:58-63 | tdesign-component/example/lib/page/message/message_types_example.dart:106-112 — before extracting anything, compare `tdesign-component/example/lib/page/message/message_styles_example.dart` and `tdesign-component/example/lib/page/message/message_types_example.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 41 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 6) tdesign-component/example/lib/page/radius/radius_circle_example.dart:9— tdesign-component/example/lib/page/radius/radius_circle_example.dart:9-17 | tdesign-component/example/lib/page/radius/radius_default_example.dart:9-16 | tdesign-component/example/lib/page/radius/radius_extra_large_example.dart:9-16 | tdesign-component/example/lib/page/radius/radius_large_example.dart:9-16 | tdesign-component/example/lib/page/radius/radius_round_example.dart:9-17 | tdesign-component/example/lib/page/radius/radius_small_example.dart:9-16 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 6 call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 3) tdesign-component/example/lib/page/shadows/shadows_base_example.dart:9— tdesign-component/example/lib/page/shadows/shadows_base_example.dart:9-17 | tdesign-component/example/lib/page/shadows/shadows_middle_example.dart:9-17 | tdesign-component/example/lib/page/shadows/shadows_top_example.dart:9-17 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 5) tdesign-component/example/lib/page/swiper/cards_swiper_example.dart:56— tdesign-component/example/lib/page/swiper/cards_swiper_example.dart:56-62 | tdesign-component/example/lib/page/swiper/controls_swiper_example.dart:27-33 | tdesign-component/example/lib/page/swiper/dots_bar_swiper_example.dart:27-33 | tdesign-component/example/lib/page/swiper/dots_swiper_example.dart:27-33 | tdesign-component/example/lib/page/swiper/fraction_swiper_example.dart:32-38 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 5 call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
No lint script — test ✓ · lint ✗ · typecheck ✓ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
R6 · Tooling· Type errors in this package cannot fail any build or CI step · ×1
Type errors in this package cannot fail any build or CI step tdesign-site/package.json:9— `tdesign-site` is TypeScript, but a type error in it cannot fail anything this repository runs: its `site` script (`pnpm test:theme && pnpm test:example-code && cd site && vite build`) compiles TypeScript with a transpile-only tool that strips types without checking them, and no script, config or CI step of the package runs `tsc --noEmit` or another type checker over it. Add a type check that can fail — a `typecheck` script running `tsc --noEmit` (or `vue-tsc`/`svelte-check`) that CI or the workspace pipeline runs, or a build step that checks before it bundles.
R6 · Tooling· A linter is configured here, but no build or CI step runs it · ×1
A linter is configured here, but no build or CI step runs it tdesign-site/.eslintrc.js:1— `tdesign-site` configures a linter in `.eslintrc.js`, but no package script, bundler plugin, task runner or CI step in this repository runs a linter, so the rules it sets are enforced nowhere. Run it where it can fail: a `lint` script that CI runs, a linter plugin in the build, or a CI step.
Unused dependency '@tdesign/site-components' tdesign-site/package.json:17— Declared in tdesign-site/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency '@tdesign/theme-generator' tdesign-site/package.json:18— Declared in tdesign-site/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'gray-matter' tdesign-site/package.json:27— Declared in tdesign-site/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'prismjs' tdesign-site/package.json:30— Declared in tdesign-site/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'vite-plugin-tdoc' tdesign-site/package.json:33— Declared in tdesign-site/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'vue-router' tdesign-site/package.json:35— Declared in tdesign-site/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Duplicated predicate tdesign-component/lib/src/components/steps/t_steps_horizontal_item.dart:261— `activeIndex == index && mode != TStepsMode.display` appears character-identically in 2 files — tdesign-component/lib/src/components/steps/t_steps_horizontal_item.dart, tdesign-component/lib/src/components/steps/t_steps_vertical_item.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate tdesign-component/lib/src/components/steps/t_steps_horizontal_item.dart:196— `activeIndex > index || mode == TStepsMode.display` appears character-identically in 2 files — tdesign-component/lib/src/components/steps/t_steps_horizontal_item.dart, tdesign-component/lib/src/components/steps/t_steps_vertical_item.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate tdesign-component/lib/src/components/progress/t_progress_theme_data.dart:344— `beginTransition == null && endTransition == null && ((begin == null && end == null) || (begin != null && end != null))` appears character-identically in 2 files — tdesign-component/lib/src/components/progress/t_progress_theme_data.dart, tdesign-component/lib/src/components/tag/t_tag_theme_data.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate tdesign-component/lib/src/components/input/t_input.dart:56— `controller == null || initialValue == null` appears character-identically in 3 files — tdesign-component/lib/src/components/input/t_input.dart, tdesign-component/lib/src/components/search/t_search_bar.dart, tdesign-component/lib/src/components/textarea/t_textarea.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate tdesign-component/lib/src/components/date_time_picker/t_date_time_picker_wheel.dart:213— `controller.hasClients && controller.position.isScrollingNotifier.value` appears character-identically in 2 files — tdesign-component/lib/src/components/date_time_picker/t_date_time_picker_wheel.dart, tdesign-component/lib/src/components/picker/t_picker.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate tdesign-component/lib/src/components/input/t_input.dart:61— `maxCharacter == null || maxCharacter >= 0` appears character-identically in 2 files — tdesign-component/lib/src/components/input/t_input.dart, tdesign-component/lib/src/components/textarea/t_textarea.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate tdesign-component/lib/src/components/input/t_input.dart:59— `maxLength == null || maxCharacter == null` appears character-identically in 3 files — tdesign-component/lib/src/components/input/t_input.dart, tdesign-component/lib/src/components/search/t_search_bar.dart, tdesign-component/lib/src/components/textarea/t_textarea.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate tdesign-component/lib/src/components/fab/t_fab_drag.dart:288— `renderObject is RenderBox && renderObject.hasSize` appears character-identically in 3 files — tdesign-component/lib/src/components/fab/t_fab_drag.dart, tdesign-component/lib/src/components/notice_bar/t_notice_bar.dart, tdesign-component/lib/src/components/swipe_cell/t_swipe_cell.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate tdesign-component/lib/src/components/dropdown_menu/t_dropdown_menu.dart:1130— `renderObject is! RenderBox || !renderObject.hasSize` appears character-identically in 2 files — tdesign-component/lib/src/components/dropdown_menu/t_dropdown_menu.dart, tdesign-component/lib/src/components/swipe_cell/t_swipe_cell.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate tdesign-component/lib/src/components/tag/t_tag_theme_data.dart:105— `squareBorderRadius == null || squareBorderRadius >= 0` appears character-identically in 2 files — tdesign-component/lib/src/components/tag/t_tag_theme_data.dart, tdesign-component/lib/src/components/time_counter/t_time_counter_theme_data.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate tdesign-component/lib/src/components/image_viewer/t_image_viewer.dart:501— `states.contains(WidgetState.hovered) || states.contains(WidgetState.focused)` appears character-identically in 2 files — tdesign-component/lib/src/components/image_viewer/t_image_viewer.dart, tdesign-component/lib/src/theme/t_internal_material.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate tdesign-component/lib/src/components/steps/t_steps_horizontal_item.dart:135— `status == TStepsStatus.error && activeIndex == index` appears character-identically in 2 files — tdesign-component/lib/src/components/steps/t_steps_horizontal_item.dart, tdesign-component/lib/src/components/steps/t_steps_vertical_item.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate tdesign-component/lib/src/components/popover/t_popover_widget.dart:846— `widget.onTap != null || widget.onLongPress != null` appears character-identically in 2 files — tdesign-component/lib/src/components/popover/t_popover_widget.dart, tdesign-component/lib/src/components/progress/t_progress.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Orphaned file tdesign-component/lib/src/components/indexes/sticky_header/sticky_header_render.dart: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 tdesign-component/lib/src/components/indexes/sticky_header/layout_builder_hook.dart: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 tdesign-component/lib/src/components/indexes/sticky_header/sticky_header_widget.dart: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 tdesign-component/lib/src/util/map_ext.dart: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 tdesign-component/lib/src/components/loading/t_activity_indicator.dart: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 tdesign-component/lib/src/util/list_ext.dart: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 tdesign-component/lib/src/components/loading/t_point_indicator.dart: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.
Fat interface: AppLocalizations (67 abstract methods) tdesign-component/example/lib/l10n/app_localizations.dart:13— `AppLocalizations` declares 67 abstract methods: `uploading`, `uploadSelect`, `uploadPending`, `uploadFailed`, `uploadRetry`, `uploadSuccess`, `components`, `setting`, `about`, `version`, `publishDate`, `defaultTheme`, `greenTheme`, `redTheme`, `darkTheme`, `cancel`, `confirm`, `switchClose`, `switchOpen`, `knew`, `loading`, `loadingWithPoint`, `other`, `refreshing`, `releaseRefresh`, `pullToRefresh`, `completeRefresh`, `reset`, `days`, `hours`, `minutes`, `seconds`, `milliseconds`, `yearLabel`, `monthLabel`, `dateLabel`, `weeks`, `sunday`, `monday`, `tuesday`, and 27 more. Counted over its public methods with no body, once per name; concrete methods and `_`-private members are not counted, because no implementer that extends it is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Fat interface: TResourceDelegate (53 abstract methods) tdesign-component/lib/src/theme/resource_delegate.dart:72— `TResourceDelegate` declares 53 abstract methods: `open`, `close`, `badgeZero`, `cancel`, `confirm`, `other`, `reset`, `loading`, `loadingWithPoint`, `knew`, `refreshing`, `releaseRefresh`, `pullToRefresh`, `completeRefresh`, `days`, `hours`, `minutes`, `seconds`, `milliseconds`, `yearLabel`, `monthLabel`, `dateLabel`, `weeksLabel`, `sunday`, `monday`, `tuesday`, `wednesday`, `thursday`, `friday`, `saturday`, `year`, `january`, `february`, `march`, `april`, `may`, `june`, `july`, `august`, `september`, and 13 more. Counted over its public methods with no body, once per name; concrete methods and `_`-private members are not counted, because no implementer that extends it is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 36 significant file(s) lose their only recent owner: tdesign-component/lib/src/components/tabbar/t_tab_bar.dart, tdesign-component/tool/component_test_manifest.dart, tdesign-component/lib/src/components/swiper/t_swiper.dart, tdesign-component/lib/src/components/dialog/t_dialog.dart, tdesign-component/lib/src/components/button/t_button_resolve.dart, tdesign-component/lib/src/components/image_viewer/t_image_viewer.dart, packages/css2token/lib/src/converter.dart, tdesign-component/lib/src/components/badge/t_badge.dart (+28 more). Pair on, review, or document these before any departure.
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion tdesign-component/pubspec.yaml:1— `tdesign-component` (62329 LoC, 424 module-visible types across 60 directories) overshoots its size bounds. 1 of 3 build unit(s) (npm, pub) overshoot their size bounds, lowering Project Cohesion to 3.3/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
D34 · Knowledge Freshness· Further orphaned files (smaller) · ×1
Further orphaned files (smaller) — 7 smaller file(s) also have no living knowledge — folded into the freshness score and metrics rather than raised one row each — most significant first: tdesign-component/lib/src/components/indexes/sticky_header/sticky_header_render.dart, tdesign-component/lib/src/components/indexes/sticky_header/layout_builder_hook.dart, tdesign-component/lib/src/components/indexes/sticky_header/sticky_header_widget.dart, tdesign-component/lib/src/util/map_ext.dart, tdesign-component/lib/src/components/loading/t_activity_indicator.dart, tdesign-component/lib/src/util/list_ext.dart, tdesign-component/lib/src/components/loading/t_point_indicator.dart (9 orphaned of 188 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 188 of the 267 production source files in this repository met that bar). Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
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.
No SAST REDACTED:4— No static application security testing detected. For this repository's stack, add the Dart analyzer's security lints plus `semgrep --config=auto` as a CI step. What was searched, so you can tell an absence from a miss: the 16 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
No dependency-update automation tdesign-site/package.json:16— `tdesign-site/package.json` 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`.
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.
trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
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. semgrep could not parse 2 file(s) — `scripts/documentation.mjs`, `tdesign-site/site/scripts/md-to-vue.ts` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
Run 01a1ebf1-0973-7408-bdc2-c2b4ef55ca08 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 63 · Warnings: 468 · Recommendations: 31 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 17-11-2026 @ 23:56 UTC.
Downloadable artifacts
Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.