Public report — Fyrox, published 29 Sep 2026.
Concrete security findings (which rule fired, in which file, on which line; CVE IDs, secret matches,
dependency versions) are REDACTED in this version; ask the repo owner for the full report.
Public
Codebase surveyMeasured under the Code Assurance Index · rubric rubric-2026.09.17 (frozen) · verify this surveyFiledcd_05c30d8813544d4ea3190fa5a6a4815c
Filed 29 September 2026, 05:06 UTC
Public
Large · 258,805 LoC · 24 projects · rebuild ~1.9 person-years · weakest lens: Event Sourcing (49%)
Findings by grade
37 critical1262 serious9 minor54 could not be resolved — could be critical — see Limitations
This survey was produced by
Watchdog
Producer
Canine Development
Analyzer
Watchdog engine 1.0.0
Measured
29 September 2026, 04:45 UTC
A measurement, not a certificate. The Code Assurance Index does not certify,
approve or guarantee this codebase; it records a reproducible number and the evidence it was computed from. The
standard is authored by Canine Development, who also build Watchdog — its only implementation today. That is said
here so the number is checked rather than believed.
Grounded in facts. Every number here is computed, not narrated — reproducible, tool-backed, and traceable to a line of code. How to trust this ▸
1292findings with an exact file:lineof 1308 — the remainder are repo-wide signals (a dimension-level measurement, not a single line); open any file:line and verify
33/120dimensions across the health lenses258805 LoC · 24 projects — wide & deep
The system holds an adequate standing with a health score of 60%, indicating a workable asset that carries real operational risk. While the architecture is robust and performance is excellent, the overall reliability is compromised by significant gaps in maturity and event sourcing logic. This balance means the business can continue operations, but at a cost of increased maintenance friction and potential stability issues that will grow if left unaddressed.
The codebase is substantial, comprising nearly 260,000 lines of production code with a rebuild cost estimated at €280,000. This represents a large investment in business logic that is currently undervalued by its technical debt. The sheer size of the asset means that even small inefficiencies compound quickly, making the cost of change higher than it would be in a smaller, cleaner system. Protecting this investment requires immediate attention to the weakest areas to prevent further erosion of value.
The primary risk lies in the event sourcing layer, which scores poorly at 49%. This weakness creates a velocity tax on every change, adding an estimated 4–8% overhead to development efforts in affected areas. This hidden cost drains engineering capacity and slows delivery speed, effectively paying a premium for the privilege of maintaining the system. Without intervention, this drag will continue to accumulate, reducing the team’s ability to respond to market needs.
A second critical issue is the lack of operational maturity, reflected in a 63% score. New team members will struggle to onboard without clear documentation or standardized decision records. This knowledge gap increases the risk of human error and extends the time required to resolve incidents. Strengthening these foundational practices is essential for long-term sustainability and reducing dependency on specific individuals.
The system’s strengths include a solid architectural foundation and perfect performance metrics, which provide a stable base for future improvements. The most impactful first step is to fix the event sourcing logic, which pays for itself within months by reducing the annual drag on engineering time. Focusing here offers the highest leverage, stabilizing the core logic and freeing up resources for broader maturity improvements.
How the score is built — each lens's share of the headlineWidth is the lens's weight in the worst-heaviest fold (the weakest area pulls hardest); colour is that lens's own band. A lens fixes the score in proportion to its width.
D22 · Inconsistent naming for setting a path. AssetItemBuilder uses 'with_path', while the AssetSelector builders use 'with_selected_asset_path'. Given that AssetItem represents a file/resource and the selector selects one, 'with_path' is the more generic and consistent term for setting a location.
D22 · Redundant methods with overlapping intent. 'push' and 'push_command' both add a command to the group. One likely accepts a generic type C and the other a concrete Command, but this creates confusion for users on which to use.
D22 · Inconsistent removal API. 'remove' takes an ID and returns a boxed trait object, while 'remove_typed' takes no arguments (implying it removes the specific type T) and returns the concrete type. This splits the removal logic between ID-based and Type-based removal without a clear pattern (e.g., 'remove_by_id' vs 'remove_by_type').
D22 · Inconsistent method signatures for UI message handling. The parameters vary significantly: some include 'engine', some 'sender', some 'editor_selection', some 'entry', and some none. This makes it difficult to implement a unified message dispatch system or understand the required context for each component.
A full-fidelity diff against the previous run's complete recorded findings — line-move tolerant: a finding that only shifted line counts as unchanged, only genuinely new titles/files surface here.
0.8× (at 60% quality) — the last 20% of quality is most of the work
Size & shape
Large · effort split not classified (source measured from disk; the effort-tier breakdown is a C#-only syntax walk)
This codebase represents roughly ~1.9 person-years of build effort (about ~€280,000 to rebuild). Its weakest lens is Event Sourcing at 49% — the part of that asset most exposed by the findings below.
How we model this: boilerplate at a scaffolding rate + logic × domain Standard (×1.0) — standard service × a 0.8× quality factor, at €60–95/h; indicative, ±~30% · size measured directly from source · effort from total production LoC as straight-line logic (the tier split is a C#-only syntax walk), a conservative lower bound. Indicative only — most sensitive to the hourly rate and the domain tier (both tunable in config).
Top priorities
The highest-leverage moves; the full ranked list is in the Roadmap below.
1
Stamp clock/random values into the event in the command; the recovery fold must be a pure function of the event.
The top-ranked fix costs roughly 3–10 engineer-days once. Not doing it costs about 7–42.2 engineer-days every year, paid as drag on the ~78,325 lines this team changes annually — a bill that arrives whether or not anyone books it. On those figures the fix breaks even in roughly 1–17 months and is free after that. Method, stated so this is not read as a quotation: debt from the ranked task's effort band; interest = annual changed lines (measured, annualised from the 90-day window) ÷ an ASSUMED 150–400 lines per engineer-day × the 4–8% drag implied by the code-quality signals; breaking point = debt ÷ annual interest. A modelled planning range built from measured inputs and one named assumption — not a quotation, a valuation, or a certified figure.
Evidence: D15 churn: 19,313 line(s) changed over a 90-day window ⇒ ~78,325/year · D1/D2/D4 code quality: averaging 6.6/10 ⇒ a 4–8% drag on each change · top-ranked remediation: Medium effort ⇒ about 3–10 engineer-day(s)
→ Do the top-ranked fix now if this code will still be yours in 17 months.
Value concentrated against a weak lens · Medium · Value at risk
This is a Large asset (~1.9 person-years to rebuild), and its weakest lens is Event Sourcing at 49%. The operational and business risk on an asset this size concentrates there — that's where remediation buys the most protection.
→ Direct remediation budget at Event Sourcing first — highest risk-reduction per euro on an asset this size.
Highest-leverage move · Medium · Leverage
Of everything flagged, the best return on effort is: Stamp clock/random values into the event in the command; the recovery fold must be a pure function of the event. The rest can wait behind it.
Evidence: priority ranking: top of 5 ranked by impact/effort
→ Stamp clock/random values into the event in the command; the recovery fold must be a pure function of the event.
A velocity tax on every change · Medium · Economics
The code-quality signals (complexity, duplication, cohesion) average 6.6/10, which acts as a tax on every change in the weaker areas: modifications there plausibly cost on the order of 4–8% more than in clean code, and the tax compounds as the codebase grows. (A modelled estimate, not a measured fact.)
Evidence: D1/D2/D4 code quality: averaging 6.6/10 across the code-quality signals actually measured
→ Pay it down where churn is highest — the hotspots — not everywhere; that's where the tax is actually paid.
Architecture — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways — a layering smell or cycle. A clean layered graph has none.
Architecture — module dependency matrix
Rows and columns are the same modules, ordered so that a module only depends on ones above it. A cell means the row depends on the column, and its number is how many type pairs create that dependency. Read one thing: is anything above the diagonal? A mark there is a dependency cycle. (A cycle is all this shows — an unusual but cycle-free dependency sits below the diagonal like any other.)
627 modules, 3711 dependencies. 4 dependency cycles across 256 modules, marked above the diagonal.
Showing the 40 most-connected modules; 587 more are not drawn.
Module dependency matrix. The row depends on the column; the number is how many type pairs create the dependency. A cell above the diagonal is part of a dependency cycle.
fyroxed_base.plugins.collider uses fyrox_core.reflect.impls. Changing fyrox_core.reflect.impls can break fyroxed_base.plugins.collider, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
36→9 fyroxed_base.plugins.collider depends on fyrox_core.pool.handle✕
Type pairs
4 distinct (type in fyroxed_base.plugins.collider → type in fyrox_core.pool.handle) references.
fyrox_impl.scene.tilemap.tileset uses fyrox_core.reflect.impls. Changing fyrox_core.reflect.impls can break fyrox_impl.scene.tilemap.tileset, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
39→8 fyrox_impl.scene.tilemap.tileset depends on fyrox_resource.manager✕
Type pairs
2 distinct (type in fyrox_impl.scene.tilemap.tileset → type in fyrox_resource.manager) references.
fyrox_impl.scene.tilemap.tileset uses fyrox_resource.manager. Changing fyrox_resource.manager can break fyrox_impl.scene.tilemap.tileset, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
39→15 fyrox_impl.scene.tilemap.tileset depends on fyrox_core.color✕
Type pairs
3 distinct (type in fyrox_impl.scene.tilemap.tileset → type in fyrox_core.color) references.
fyrox_impl.scene.tilemap.tileset uses fyroxed_base.asset.selector. Changing fyroxed_base.asset.selector can break fyrox_impl.scene.tilemap.tileset, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
39→38 fyrox_impl.scene.tilemap.tileset depends on fyrox_animation✕
Type pairs
1 distinct (type in fyrox_impl.scene.tilemap.tileset → type in fyrox_animation) reference.
fyrox_impl.scene.tilemap.tileset uses fyrox_impl.scene.tilemap. Changing fyrox_impl.scene.tilemap can break fyrox_impl.scene.tilemap.tileset, not the reverse.
Position
Above the diagonal — a cycle. Neither module can be changed, tested or deployed independently until one of these dependencies goes.
40→2 fyrox_impl.scene.tilemap depends on fyrox_core.visitor✕
Type pairs
2 distinct (type in fyrox_impl.scene.tilemap → type in fyrox_core.visitor) references.
fyrox_impl.scene.tilemap uses fyrox_impl.scene.tilemap.tileset. Changing fyrox_impl.scene.tilemap.tileset can break fyrox_impl.scene.tilemap, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
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
A03:2021 — Injection
31
High / Critical
A02:2021 — Cryptographic Failures
2
High / Critical
Roadmap
First, ensure deterministic event handling by stamping clock and random values into commands so recovery is a pure function of the event. Next, improve onboarding and architectural clarity by adding a quick-start section to the README and documenting significant design decisions in a dedicated ADR structure. Finally, address the single missing ADR and resolve the leaked secret in the release keystore to secure the project.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Stamp clock/random values into the event in the command; the recovery fold must be a pure function of the event.
Record significant decisions one document per decision — dated, stating the context, the decision and its consequences — and keep them together wherever your design docs already live (a conventional `docs/adr/` tree, with each file named `NNNN-title` in whatever markup those docs already use, is the most discoverable form).
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 — 37
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 — 1262
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 — 9
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 54
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
Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 28 of 33 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 5 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.8 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
Every figure here is one of three kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact; ◐ Advisory — an LLM prose judgement. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.
What we checked — 33 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, 1292 of 1308 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
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.
D6 Cohesion (LCOM4) — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
D8 Code Coverage — not measured this run — Watchdog 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: test source is present (.rs) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo. To have real coverage read, produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
D11 Test Reliability — not measured this run — Watchdog 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 source is present (.rs) and this repository declares a Cargo test suite (repository root, 161 test files), but it was not re-run: no test result was produced. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
D12 Dependency Hygiene — not measured this run — Watchdog 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 — 78 direct Cargo declaration(s) were read, but the outdated signal needs crates.io, and no committed Cargo.lock resolves them to versions, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
D14 License Compliance — not measured this run — Watchdog 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 declares Cargo manifests but commits no Cargo.lock, so the set of crates it actually ships is not resolvable from the checkout: its declarations carry version RANGES, and grading whichever release happens to be newest today would be a verdict about a dependency graph this repository has not pinned. Commit the lock and this dimension grades the closure against crates.io. NOT a finding that this repository's licences are compliant: this dimension asserts nothing about its licensing in either direction.
D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (94 contributor(s) across 8478 commit(s) sampled, automation and bot accounts excluded). One of them holds 91% of the history; the other 93 hold 0.1% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
D30 Dependency Vulnerabilities — not measured this run — Watchdog 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. Osv: the scanner produced no output at all, so no dependency was actually scanned. 'osv-scanner' exited 128 and produced no findings, and that exit code has no documented repo-side meaning — so this run measured nothing, and nothing here is a statement about the repository.
D43 Malicious Dependencies — not measured this run — Watchdog 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. Osv: the scanner produced no output at all, so no dependency was actually scanned. 'osv-scanner' exited 128 and produced no findings, and that exit code has no documented repo-side meaning — so this run measured nothing, and nothing here is a statement about the repository.
D44 Platform End-of-Life — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a Dockerfile) is simply not read here yet.
AX1 Captive dependencies — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
AX2 Stateful singletons — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
AX6 Interface segregation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
AXB1 Runtime evidence locked — no reproducible boot — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, or a Dockerfile. None was found, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. Watchdog then boots it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
C1 Data Protection — not measured this run — Watchdog 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. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
C2 Access Controls — not measured this run — Watchdog 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. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
C3 Audit Trail — not measured this run — Watchdog 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. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
C4 Data Retention — not measured this run — Watchdog 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. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
C5 Data-Subject Rights — not measured this run — Watchdog 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. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
ED5 Idempotency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check finds retry-prone mutations by walking the repository's declared types, and NONE was loaded on this run, so it had nothing to look at. That is a limit of the analyzer's reach — it reads .NET projects — not a finding that this repository has no command handlers or message consumers.
GD1 Unfinished & placeholder code — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
IC1 Incompleteness & stubs — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
P10 Library API & versioning — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads NuGet packaging and C# public API only, and no .NET project was loaded for this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
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.
PF1 Benchmark discipline — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
PF2 Allocation hygiene — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
S1 Web-Security Posture — not measured this run — Watchdog 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. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
X1 Async correctness — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X10 Duplicated predicate — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X12 Unreachable branch — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X13 Undrained process stream — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X14 Bypassable address classification — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X15 Unvalidated length from an untrusted reader — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X16 Unfloored truncation loop — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X17 Uncapped recursion over a caller-supplied document — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X18 Disposal-pattern correctness — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X19 Unrestored process-global state — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X2 Cancellation propagation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X20 Mistyped argument guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X21 Side-effecting pattern guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X22 Contradicted release guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X23 Unguarded diagnostic materialisation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X24 Document value interpolated into markup unescaped — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X25 Inert configuration knob — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X26 Unsynchronised callback handoff — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X27 Collection changed while being enumerated — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X28 Index access outside its own emptiness guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X29 Per-element action decided by a fixed element — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X3 Exception handling — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X30 Support guard that admits what it rejects — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X32 Type resolved by simple name across every loaded assembly — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X4 Structured logging — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X5 Nullable reference types — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X6 Hand-rolled structured-format parsing — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X7 Silent fallback defaults — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — 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.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
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.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement. Its critique rows are drawn from a closed category vocabulary and each row means the same thing in every run, so two scans can be compared row by row; the SET that fires is still a sample, and does not repeat exactly. Measured on one frozen input, six scans at one engine SHA: 2-5 critique rows per scan, 8 distinct rows across the six, 3 of those 8 seen in only one scan. So a D19 row is evidence about the documentation, but a COUNT of D19 rows is not a quantity — never read a change in it as an improvement or a regression.
D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
D22 Internal API Consistency: API-surface coherence is an LLM judgement over a sample of the public surface — consistency of intent across the whole API is approximated, not exhaustively verified.
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").
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
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: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
The LLM boundary
LLM-set scores this run (5): D19, D21, D22, D26, M4 (model: Local LLM). For these, a model reads a bounded sample and sets the numeric score; each names its own sample and method on its card. They are sampled and advisory by design: they vary at the margins between runs and are never a deterministic measurement. Every other score in this report is tool-computed at confidence 1.0.
What it measures: How tangled the control flow is — methods with many branches are hard to test and change.
Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.
137 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was TextBox::handle_routed_message at 99. A further 25 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 fyrox_impl::utils::translate_key_to_ui at 195 — they are counted neither in the figure above nor in this dimension's score. 12 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold functions was excluded, so the exclusion is disclosed nowhere in the file itself: fyrox-impl/src/utils/mod.rs (fyrox_impl::utils::translate_key_to_ui at 195), fyrox-ui/src/message.rs (KeyCode::to_char at 73), fyrox-core/src/visitor/reader/binary.rs (BinaryReader::read_field at 54), fyrox-core/src/visitor/writer/binary.rs (BinaryWriter::write_field at 53), fyrox-impl/src/renderer/cache/texture.rs (fyrox_impl::renderer::cache::texture::convert_pixel_kind at 27), and 7 more not listed here. They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
+ 95 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 10 fyrox_impl finding(s) in Cyclomatic Complexity — start with mod.rs (5), bundle.rs, ascii.rs. — One of this dimension's main actionable groups (10 warning-level).
Resolve the 5 Editor finding(s) in Cyclomatic Complexity — start with lib.rs (5). — One of this dimension's main actionable groups (5 warning-level).
Resolve the 4 PaletteWidget finding(s) in Cyclomatic Complexity — start with palette.rs (4). — One of this dimension's main actionable groups (4 warning-level).
Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
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.
+ 202 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 14 fyrox_impl finding(s) in Cognitive Complexity — start with mod.rs (8), ui_renderer.rs, ascii.rs. — One of this dimension's main actionable groups (14 warning-level).
Resolve the 9 UserInterface finding(s) in Cognitive Complexity — start with lib.rs (9). — One of this dimension's main actionable groups (9 warning-level).
Resolve the 8 PaletteWidget finding(s) in Cognitive Complexity — start with palette.rs (8). — One of this dimension's main actionable groups (8 warning-level).
Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes7.6 / 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.
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 91 MethodTooLong finding(s) in God Classes — start with mod.rs (25), menu.rs (5), lib.rs (4). — One of this dimension's main actionable groups (91 warning-level).
Resolve the 80 FileTooLong finding(s) in God Classes — start with mod.rs (32), lib.rs (6), tileset.rs (2). — One of this dimension's main actionable groups (80 warning-level).
Resolve the 45 ClassTooLong finding(s) in God Classes — start with mod.rs (15), lib.rs (3), manager.rs (2). — One of this dimension's main actionable groups (45 warning-level).
Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Copy-pasted code that should be shared instead.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.
405 duplicated block group(s) detected. A further 20 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted. 2 of the 425 are in trees this repository does not ship — vendored, example/demo, 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.
+ 101 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 38 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with mod.rs (10), rigidbody.rs (5), autotile.rs (3). — One of this dimension's main actionable groups (38 warning-level).
Resolve the 32 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with mod.rs (4), cuboid.rs (2), property.rs (2). — One of this dimension's main actionable groups (32 warning-level).
Resolve the 27 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with mod.rs (8), colliders_tab.rs (3), ragdoll.rs. — One of this dimension's main actionable groups (27 warning-level).
Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling8.9 / 10Strong✓ 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.
24 production modules (Cargo), 0 dependency cycle(s), 1 unstable depended-on module(s). Read from the build's own module declarations; 2 module(s) off the main sequence, with abstractness counted on 20 of the 24 (the rest declare no modelled class or interface, export only macros, or have no source directory of their own).
Off the main sequence: fyrox-math · ×2
Unstable project fyrox-impl
What to do
Resolve the 2 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (2 warning-level).
Resolve the 1 Unstable project fyrox-impl finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D9 · Test Distribution10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the test suite has a healthy mix of unit / integration / end-to-end tests.
Method: Test projects classified (Unit/Integration/BDD/E2E) from compiled metadata; test methods counted exhaustively across projects with placement-agnostic disk fallback. Deterministic.
701 test methods: 668 unit, 33 integration, 0 BDD, 0 e2e. The Rust suite contributes 701 `#[test]` function(s) across 161 file(s) declaring at least one; its unit/integration split is Cargo's own — 8 of those file(s) are integration-test targets under a crate's tests/ directory, and the rest are #[test] functions compiled into the crate they test.
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.
Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Enforce Secret Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d13_recommendation.md · top locations in Appendix A, every location in findings.md.
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: editor/src/scene_viewer/mod.rs (7×55=385); editor/src/plugins/absm/canvas.rs (6×45=270); fyrox-ui/src/formatted_text.rs (4×26=104) Repeated repair below the complexity floor: fyrox-ui/src/inspector/editors/inspectable.rs (3 of 5 changes were fixes); fyrox-core-derive/src/reflect.rs (3 of 4 changes were fixes); editor/src/plugins/inspector/editors/dyntype.rs (3 of 4 changes were fixes)
Resolve the 5 Hotspot finding(s) in Churn × Complexity Hotspots — start with mod.rs (2), canvas.rs, formatted_text.rs. — One of this dimension's main actionable groups (5 warning-level).
Resolve the 3 Repeated repair finding(s) in Churn × Complexity Hotspots — start with inspectable.rs, reflect.rs, dyntype.rs. — One of this dimension's main actionable groups (3 warning-level).
Detailed fixes: d15_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.
103 deducted task-comment markers across 258805 LoC (0.0/KLoC) → score 9.9. 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.
TodoComment repeated across 16 fileseditor/src/lib.rs:21
XxxCommentfyrox-material/src/shader/mod.rs:410
What to do
Resolve the 72 TodoComment finding(s) in Explicit Debt — start with mod.rs (19), lib.rs (8), geometry.rs (3). — One of this dimension's main actionable groups (72 warning-level).
Resolve the 4 FixmeComment finding(s) in Explicit Debt — start with mod.rs (2), impls.rs (2). — One of this dimension's main actionable groups (4 warning-level).
Resolve the 4 HackComment finding(s) in Explicit Debt — start with mod.rs (4). — One of this dimension's main actionable groups (4 warning-level).
Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
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: Judged by language model at low temperature (0.0-0.1) on a deterministic doc sample (READMEs plus first 25 architecture docs), with two-pass stability filtering. Advisory, sampled.
The repository's root README is excellent with an overview, licensing badge, CI status, learning materials link, community, examples, support, and a strong sponsor section. The editor-standalone README gives installation and a warning about the unsupported standalone version. Each directory's README documents itself (editor/, fyrox-animation/, fyrox-core-, etc.) rather than the repository root, so no repository-wide overview/usage/contribution guidance is claimed by those docs. There are two clipped trailing sections but the visible content is complete for each document. The repository's README files are mostly focused on the engine's architecture and design (Architecture.md is a detailed work-in-progress document), with no overview of what the project does or how to use it. The root README is thin but present; its scope is best judged by the directory-level documentation rather than this single file.
Documentation: contradicts the codetemplate-core/src/android/README.md
What to do
Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d19_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D20 · ADR Quality0.0 / 10Critical✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Per-ADR judgment by language model at low temperature with two-pass stability; confidence is share of ADRs evaluated; enforcement-field presence detected deterministically. Advisory.
What it measures: Whether names — types, methods, variables — are clear and consistent.
Method: Judged by language model at low temperature (0.0-0.1) on a deterministic random symbol sample (fixed size, not exhaustive), with disclosed confidence band. Advisory, sampled.
0 naming inconsistencies across 0 sampled symbols.
✓ On the Gold path — maintain.
Detailed fixes: d21_recommendation.md.
Do you agree with this assessment?
D22 · Internal API ConsistencyStrong◐ Sampled · advisory
What it measures: Whether the internal API surface is consistent and coherent.
Method: Judged by language model at low temperature over a sample of the public API surface (IsPackable or .Contracts types). Sampled, advisory; confidence discounted by model uncertainty.
4 API inconsistencies across a 400-member sample of 1943 exposed types.
Inconsistent naming for setting a path. AssetItemBuilder uses 'with_path', while the AssetSelector builders use 'with_selected_asset_path'. Given that AssetItem represents a file/resource and the selector selects one, 'with_path' is the more generic and consistent term for setting a location.
Redundant methods with overlapping intent. 'push' and 'push_command' both add a command to the group. One likely accepts a generic type C and the other a concrete Command, but this creates confusion for users on which to use.
Inconsistent removal API. 'remove' takes an ID and returns a boxed trait object, while 'remove_typed' takes no arguments (implying it removes the specific type T) and returns the concrete type. This splits the removal logic between ID-based and Type-based removal without a clear pattern (e.g., 'remove_by_id' vs 'remove_by_type').
Inconsistent method signatures for UI message handling. The parameters vary significantly: some include 'engine', some 'sender', some 'editor_selection', some 'entry', and some none. This makes it difficult to implement a unified message dispatch system or understand the required context for each component.
What to do
Resolve the 1 Inconsistent naming for setting a path. AssetItemBuilder uses… finding(s) in Internal API Consistency. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Redundant methods with overlapping intent. 'push' and 'push_command'… finding(s) in Internal API Consistency. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Inconsistent removal API. 'remove' takes an ID and returns a boxed trait… finding(s) in Internal API Consistency. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d22_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).
31 finding(s): 0 critical, 31 high, 0 medium, 0 low. 29 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 1 file(s) — `fyrox-core/src/safelock.rs` (lines 38–39) — 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.
REDACTED
REDACTED
What to do
Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
No action in Static Analysis (SAST) — all 29 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 (29 issue-level, 0 of them charged here).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
11 of 595 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is fyrox-impl/src/scene/tilemap/tile_rect.rs. Counted over 595 of the 646 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 tile_rect.rs, autotile.rs. — One of this dimension's main actionable groups (2 issue-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 Boundary-crossing change coupling finding(s) in Change Coupling — start with lib.rs. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 7 Change coupling finding(s) in Change Coupling — start with selection.rs (2), enumeration.rs, mod.rs. — One of this dimension's main actionable groups (7 warning-level).
Resolve the 5 Change coupling clique finding(s) in Change Coupling — start with directional.rs, gbuffer.rs, move_mode.rs. — One of this dimension's main actionable groups (5 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
What to do
The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
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 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 · Event Sourcing — Whether the recovery-replay fold is deterministic — state derived purely from each event's own fields, no clock/random/IO on the replay path.
Method: Roslyn syntax scan (event-sourcing gated): Apply/When folds checked for forbidden tokens (DateTime.Now, Guid.NewGuid, Random, IO), stripped of comments/strings. Deterministic, hard fact per fold.
`StateAction.apply` folds a domain event but reads a clock/random source (`Instant::now`/`Utc::now`/`rand`/`Uuid::new_v4`) on the replay path — a replay must derive state PURELY from the event's own fields, or two replays of the same log diverge. Stamp the timestamp/id into the event in the COMMAND, then read it from the event in the fold. — fyrox-animation/src/machine/state.rs:109
What to do
Stamp clock/random values into the event in the command; the recovery fold must be a pure function of the event.
Other · Event Sourcing — Whether domain events stay immutable (private fields, set once) rather than carrying mutable state.
Method: Roslyn scan (event-sourcing gated): persisted events checked for public setters; immutability verified per property/field. Deterministic, hard fact.
Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
447 code files changed in the last 6 months but the README was not touched — it may no longer reflect the system.
What to do
Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
Add a 'Testing' section to the root README — how to run the test suite.
Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
Add a README to the 11 of 24 project(s) that lack one — worth up to 0.9 pts.
Review the README against recent changes; refresh the parts that drifted.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no 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 significant decisions one document per decision — dated, stating the context, the decision and its consequences — and keep them together wherever your design docs already live (a conventional `docs/adr/` tree, with each file named `NNNN-title` in whatever markup those docs already use, is the most discoverable form).
Maturity · Maturity — Whether the README actually describes the code that exists (LLM-judged, advisory).
Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.
Only 14/15 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `template`.
What to do
Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
Consider OpenTelemetry tracing/metrics (opentelemetry with tracing-opentelemetry) and a health-check endpoint (a /health route on your axum/actix router) for operability.
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.
What to do
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
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 the language model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin) or inside a Java method returning a Reactor Mono/Flux — 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?
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.
X9 Subsumed condition operand — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 5 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) 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. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) 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. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) 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. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 81 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 (11 DOM element(s) < 25) — too little surface to assess accessibility.
AC2 Forms & labels — Frontend below the scale floor (11 DOM element(s) < 25) — too little surface to assess accessibility.
AC3 Page structure — Frontend below the scale floor (11 DOM element(s) < 25) — too little surface to assess accessibility.
AC4 Keyboard semantics — Frontend below the scale floor (11 DOM element(s) < 25) — too little surface to assess accessibility.
AC5 ARIA correctness — Frontend below the scale floor (11 DOM element(s) < 25) — too little surface to assess accessibility.
AC6 Visual & motion safety — Frontend below the scale floor (11 DOM element(s) < 25) — too little surface to assess accessibility.
AC7 A11y enforcement — Frontend below the scale floor (11 DOM element(s) < 25) — too little surface to assess accessibility.
AX1 Captive dependencies — not analysed — these correctness checks read a source model 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
AX2 Stateful singletons — not analysed — these correctness checks read a source model 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
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
AX6 Interface segregation — not assessed — interface segregation is computed over a type surface 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
AX8 Test isolation — no test/production split to check
AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) 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. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) 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. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
D10 Test Quality — ~3137 lines of test source are present (.rs) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
D11 Test Reliability — Test reliability not included — the .rs suite was found but not re-run
D12 Dependency Hygiene — Not scored — 78 direct Cargo declaration(s) were read, but the outdated signal needs crates.io, and no committed Cargo.lock resolves them to versions, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
D14 License Compliance — Crate licences not graded — this Cargo repository commits no Cargo.lock
D16 Bus Factor — single-maintainer repository — bus factor is not applicable
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.
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. 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 — No inline comments to assess — comment value is not applicable here.
D25 ADR Conformance — no ADRs to check
D27 Navigability — symbol resolution incomplete — too few calls resolved to assess navigability
D30 Dependency Vulnerabilities — Scanner failed to run — not a clean result
D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
D36 Supply-chain Provenance & Signing — The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
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.
D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
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.
D43 Malicious Dependencies — Scanner failed to run — not a clean result
D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
D6 Cohesion (LCOM4) — D6 reads a CS/VB/GO/SCALA/SWIFT/DART/JAVA/PY/KT/TS/TSX/MTS/CTS/JS/JSX/MJS/CJS/PHP class graph only — this repository's production source is .rs, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
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 included — suite not readable by the collector
DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 157 value object(s); 5 domain event(s); its domain events are published by services or handlers — no domain entity raises one
ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
ED5 Idempotency — This check finds retry-prone mutations (command handlers and message/event consumers) by walking the repository's declared types, and none was loaded here, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
GD1 Unfinished & placeholder code — no source files were read — this check reads C# syntax, and none was loaded for this repository. That is a limit of the analyzer, not a finding about your code.
IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model 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
P10 Library API & versioning — not analysed — these correctness checks read a source model 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
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'.
P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript, Rust 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 — no coverage report found on disk — produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
PF1 Benchmark discipline — not analysed — these correctness checks read a source model 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
PF2 Allocation hygiene — not analysed — these correctness checks read a source model 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
S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) 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. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
X1 Async correctness — not analysed — these correctness checks read a source model 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
X10 Duplicated predicate — not analysed — these correctness checks read a source model 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
X12 Unreachable branch — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X13 Undrained process stream — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X14 Bypassable address classification — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X15 Unvalidated length from an untrusted reader — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X16 Unfloored truncation loop — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X17 Uncapped recursion over a caller-supplied document — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X18 Disposal-pattern correctness — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X19 Unrestored process-global state — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X2 Cancellation propagation — not analysed — these correctness checks read a source model 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
X20 Mistyped argument guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X21 Side-effecting pattern guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X22 Contradicted release guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X23 Unguarded diagnostic materialisation — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X24 Document value interpolated into markup unescaped — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X25 Inert configuration knob — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X26 Unsynchronised callback handoff — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X27 Collection changed while being enumerated — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X28 Index access outside its own emptiness guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X29 Per-element action decided by a fixed element — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X3 Exception handling — not analysed — these correctness checks read a source model 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
X30 Support guard that admits what it rejects — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X32 Type resolved by simple name across every loaded assembly — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X4 Structured logging — not analysed — these correctness checks read a source model 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
X5 Nullable reference types — not analysed — these correctness checks read a source model 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
X6 Hand-rolled structured-format parsing — not analysed — these correctness checks read a source model 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
X7 Silent fallback defaults — not analysed — these correctness checks read a source model 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
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 fyrox-impl/src/scene/tilemap/tile_rect.rs— No living knowledge remains for this large file — its last meaningful change has decayed away, so if it breaks, no one currently understands it. It does carry its own tests, so the behaviour is pinned even though the understanding is gone: schedule a read-through, using those tests as the specification, before the next change lands here.
Orphaned knowledge fyrox-impl/src/scene/tilemap/autotile.rs— 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.
Boundary-crossing change coupling: lib.rs ↔ executor.rs editor/src/lib.rs— `editor/src/lib.rs` (context editor) and `fyrox-impl/src/engine/executor.rs` (context fyrox-impl) sit in DIFFERENT parts of the tree yet change together 51% of the time (27 of the 53 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) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 27 shared commits counted here, the most recent 3 are `66d1b34f` pass dyn type constructors when deserializing scenes/uis; `f433968e` process file system events on every frame; `b40bc9ce` migrate to latest winit + glutin — run `git show` on any of them.
Non-deterministic recovery fold: StateAction.apply fyrox-animation/src/machine/state.rs:109— `StateAction.apply` folds a domain event but reads a clock/random source (`Instant::now`/`Utc::now`/`rand`/`Uuid::new_v4`) on the replay path — a replay must derive state PURELY from the event's own fields, or two replays of the same log diverge. Stamp the timestamp/id into the event in the COMMAND, then read it from the event in the fold.
MethodTooLong: DeferredLightRenderer.render fyrox-impl/src/renderer/light.rs:254— MethodTooLong — render runs 616 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 516 over it, 6.16× 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: RagdollPreset.create_and_send_command editor/src/plugins/ragdoll.rs:481— MethodTooLong — create_and_send_command runs 415 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 315 over it, 4.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: ProjectManager.new project-manager/src/manager.rs:338— MethodTooLong — new runs 389 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 289 over it, 3.89× 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: CurveEditor.handle_routed_message fyrox-ui/src/curve/mod.rs:574— MethodTooLong — handle_routed_message runs 305 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 205 over it, 3.05× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: UserInterface.process_os_event fyrox-ui/src/lib.rs:2776— MethodTooLong — process_os_event runs 286 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 186 over it, 2.86× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: TextBox.handle_routed_message fyrox-ui/src/text_box.rs:1128— MethodTooLong — handle_routed_message runs 282 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 182 over it, 2.82× 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: Toolbar.new editor/src/plugins/animation/toolbar.rs:402— MethodTooLong — new runs 265 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 165 over it, 2.65× 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: Window.handle_routed_message fyrox-ui/src/window.rs:393— MethodTooLong — handle_routed_message runs 262 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 162 over it, 2.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: PropertyEditorDefinitionContainer.with_default_editors fyrox-ui/src/inspector/editors/mod.rs:452— MethodTooLong — with_default_editors runs 259 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 159 over it, 2.59× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Renderer.render_scene_observer fyrox-impl/src/renderer/mod.rs:964— MethodTooLong — render_scene_observer runs 255 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 155 over it, 2.55× 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: SceneViewer.new editor/src/scene_viewer/mod.rs:286— MethodTooLong — new runs 236 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 136 over it, 2.36× 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: TileSetEditor.new editor/src/plugins/tilemap/tileset.rs:208— MethodTooLong — new runs 233 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 133 over it, 2.33× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Tile.handle_routed_message fyrox-ui/src/dock/tile.rs:461— MethodTooLong — handle_routed_message runs 229 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 129 over it, 2.29× 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: PropertiesTab.new editor/src/plugins/tilemap/properties_tab.rs:252— MethodTooLong — new runs 223 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 123 over it, 2.23× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: WgpuFrameBuffer.do_draw fyrox-graphics-wgpu/src/framebuffer.rs:489— MethodTooLong — do_draw runs 222 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 122 over it, 2.22× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: TileMapPanel.new editor/src/plugins/tilemap/panel.rs:167— MethodTooLong — new runs 214 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 114 over it, 2.14× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: GlGraphicsServer.new fyrox-graphics-gl/src/server.rs:591— MethodTooLong — new runs 196 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 96 over it, 1.96× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ScriptProcessor.handle_scripts fyrox-impl/src/engine/mod.rs:642— MethodTooLong — handle_scripts runs 193 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 93 over it, 1.93× 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: ExportWindow.new editor/src/export/mod.rs:98— MethodTooLong — new runs 191 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 91 over it, 1.91× 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: WgpuFrameBuffer.get_or_create_pipeline fyrox-graphics-wgpu/src/framebuffer.rs:253— MethodTooLong — get_or_create_pipeline runs 185 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 85 over it, 1.85× 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: UserInterface.poll_single_message fyrox-ui/src/lib.rs:2354— MethodTooLong — poll_single_message runs 176 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 76 over it, 1.76× 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: GlTexture.set_data fyrox-graphics-gl/src/texture.rs:397— MethodTooLong — set_data runs 175 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 75 over it, 1.75× 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: AssetBrowser.handle_ui_message editor/src/asset/mod.rs:631— MethodTooLong — handle_ui_message runs 171 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) 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: UiRenderer.render fyrox-impl/src/renderer/ui_renderer.rs:289— MethodTooLong — render runs 171 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) 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: CurveEditorBuilder.build fyrox-ui/src/curve/mod.rs:1829— MethodTooLong — build runs 171 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) 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.
FileTooLong: src/lib.rs fyrox-ui/src/lib.rs— FileTooLong — 2393 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 74% of them inside a single declaration: UserInterface (12 blocks, 736-4038). The bar is 500 significant lines; this is 1893 over it, 4.79× 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: engine/mod.rs fyrox-impl/src/engine/mod.rs— FileTooLong — 1791 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 1291 over it, 3.58× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: terrain/mod.rs fyrox-impl/src/scene/terrain/mod.rs— FileTooLong — 1630 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 1130 over it, 3.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: tilemap/palette.rs editor/src/plugins/tilemap/palette.rs— FileTooLong — 1582 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 66% of them inside a single declaration: PaletteWidget (4 blocks, 173-1977). The bar is 500 significant lines; this is 1082 over it, 3.16× 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: curve/mod.rs fyrox-ui/src/curve/mod.rs— FileTooLong — 1336 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 60% of them inside a single declaration: CurveEditor (4 blocks, 426-1731). The bar is 500 significant lines; this is 836 over it, 2.67× 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: physics/mod.rs fyrox-impl/src/scene/graph/physics/mod.rs— FileTooLong — 1291 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 791 over it, 2.58× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: tilemap/tileset.rs fyrox-impl/src/scene/tilemap/tileset.rs— FileTooLong — 1273 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 773 over it, 2.55× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: animation/track.rs editor/src/plugins/animation/track.rs— FileTooLong — 1264 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 63% of them inside a single declaration: TrackList (2 blocks, 610-1741). The bar is 500 significant lines; this is 764 over it, 2.53× 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: graph/mod.rs fyrox-impl/src/scene/graph/mod.rs— FileTooLong — 1252 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 88% of them inside a single declaration: Graph (10 blocks, 130-2201). The bar is 500 significant lines; this is 752 over it, 2.50× 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: src/lib.rs fyrox-texture/src/lib.rs— FileTooLong — 1200 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 700 over it, 2.40× 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: src/manager.rs fyrox-resource/src/manager.rs— FileTooLong — 1123 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 623 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: src/widget.rs fyrox-ui/src/widget.rs— FileTooLong — 1107 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 607 over it, 2.21× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: inspector/mod.rs fyrox-ui/src/inspector/mod.rs— FileTooLong — 1069 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 569 over it, 2.14× 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: src/text_box.rs fyrox-ui/src/text_box.rs— FileTooLong — 1054 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 71% of them inside a single declaration: TextBox (5 blocks, 432-1536). The bar is 500 significant lines; this is 554 over it, 2.11× 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: src/manager.rs project-manager/src/manager.rs— FileTooLong — 1009 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 79% of them inside a single declaration: ProjectManager (2 blocks, 132-1333). The bar is 500 significant lines; this is 509 over it, 2.02× 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: renderer/mod.rs fyrox-impl/src/renderer/mod.rs— FileTooLong — 986 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 64% of them inside a single declaration: Renderer (2 blocks, 414-1511). The bar is 500 significant lines; this is 486 over it, 1.97× 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: physics/mod.rs fyrox-impl/src/scene/dim2/physics/mod.rs— FileTooLong — 966 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 65% of them inside a single declaration: PhysicsWorld (6 blocks, 467-1519). The bar is 500 significant lines; this is 466 over it, 1.93× 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: plugins/ragdoll.rs editor/src/plugins/ragdoll.rs— FileTooLong — 959 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 64% of them inside a single declaration: RagdollPreset (3 blocks, 79-1011). The bar is 500 significant lines; this is 459 over it, 1.92× 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: tilemap/tile_inspector.rs editor/src/plugins/tilemap/tile_inspector.rs— FileTooLong — 955 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 455 over it, 1.91× 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: tilemap/mod.rs fyrox-impl/src/scene/tilemap/mod.rs— FileTooLong — 950 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 450 over it, 1.90× 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: mesh/surface.rs fyrox-impl/src/scene/mesh/surface.rs— FileTooLong — 928 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 64% of them inside a single declaration: SurfaceData (4 blocks, 225-1066). The bar is 500 significant lines; this is 428 over it, 1.86× 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: src/lib.rs fyrox-graph/src/lib.rs— FileTooLong — 927 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 427 over it, 1.85× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: dock/tile.rs fyrox-ui/src/dock/tile.rs— FileTooLong — 926 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 68% of them inside a single declaration: Tile (4 blocks, 264-1216). The bar is 500 significant lines; this is 426 over it, 1.85× 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: scene/mod.rs editor/src/scene/mod.rs— FileTooLong — 921 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 73% of them inside a single declaration: GameScene (3 blocks, 134-1130). The bar is 500 significant lines; this is 421 over it, 1.84× 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: src/server.rs fyrox-graphics-gl/src/server.rs— FileTooLong — 921 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 65% of them inside a single declaration: GlGraphicsServer (3 blocks, 515-1549). The bar is 500 significant lines; this is 421 over it, 1.84× 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.
TodoComment editor/src/asset/selection.rs:119— // TODO: Add multi-selection support. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment editor/src/asset/preview/mod.rs:395— // TODO: This is a hack, refactor `render_scene` method to accept render data from — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment editor/src/asset/preview/mod.rs:652— // TODO: Implement. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment editor/src/interaction/gizmo/scale_gizmo.rs:300— // TODO: Still may behave weird. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment editor/src/plugins/absm/canvas.rs:621— // TODO: Check if other mode is active. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment editor/src/plugins/animation/toolbar.rs:679— // TODO: Here we allow importing only FBX and GLTF files, but they can contain — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment editor/src/plugins/inspector/mod.rs:141— // TODO: Remove duplicated code. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment editor/src/plugins/inspector/mod.rs:516— // TODO: This could work incorrectly in case of multiselection of objects — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment editor/src/plugins/inspector/editors/mod.rs:763— // TODO: Add generic property editors too (NumericUpDown<T>, etc.). — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment editor/src/plugins/inspector/editors/handle.rs:249— // TODO: Do type check here. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment editor/src/plugins/tilemap/palette.rs:1372— // TODO: Allow users to drag-and-drop materials into a palette to create — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment editor/src/plugins/tilemap/interaction_mode.rs:819— // TODO: Is there a better way to make a grid? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment editor/src/scene/property.rs:238— // TODO: Here we just using `Debug` impl to obtain string representation for keys. This is — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment fyrox-core/src/reflect/mod.rs:358— // TODO: Here we just using `Debug` impl to obtain string representation for keys. This is — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment editor/src/scene/property.rs:248— // TODO: This is unreliable mechanism. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment fyrox-core/src/reflect/mod.rs:368— // TODO: This is unreliable mechanism. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment editor/src/scene/container.rs:582— // TODO: Maybe set it to the previous one? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment editor/src/ui_scene/utils.rs:128— // todo: add more icons — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment fyrox-build-tools/src/export/pc.rs:39— // TODO: This should be replaced with `--out-dir` flag to cargo when it is stabilized. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment fyrox-build-tools/src/export/mod.rs:304— // TODO: This is should be checked for usefulness. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment fyrox-core/src/io.rs:182— // TODO: Is directory checking possible on wasm? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment fyrox-core/src/reflect/set.rs:40— // TODO: combine uuids — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment fyrox-core/src/reflect/map.rs:55— // TODO: combine uuids — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment fyrox-core/src/reflect/array.rs:69— // TODO: combine uuids. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment fyrox-graphics-wgpu/src/server.rs:336— // TODO: Force `msaa_sample_count` to 1 in the wgpu backend. Full MSAA support requires creating multisampled render targets and resolve targets, which is a larger feature. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
ClassTooLong: UserInterface fyrox-ui/src/lib.rs:736— ClassTooLong — 1762 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 95 methods, 12 blocks, lines 736-4038. The bar is 400 significant lines; this is 1362 over it, 4.41× 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: Graph fyrox-impl/src/scene/graph/mod.rs:130— ClassTooLong — 1106 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 73 methods, 10 blocks, lines 130-2201. The bar is 400 significant lines; this is 706 over it, 2.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.
ClassTooLong: PaletteWidget editor/src/plugins/tilemap/palette.rs:173— ClassTooLong — 1041 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 49 methods, 4 blocks, lines 173-1977. The bar is 400 significant lines; this is 641 over it, 2.60× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Engine fyrox-impl/src/engine/mod.rs:316— ClassTooLong — 946 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 34 methods, 3 blocks, lines 316-2884. The bar is 400 significant lines; this is 546 over it, 2.37× 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: Terrain fyrox-impl/src/scene/terrain/mod.rs:1037— ClassTooLong — 854 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 64 methods, 8 blocks, lines 1037-2604. The bar is 400 significant lines; this is 454 over it, 2.14× 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: ProjectManager project-manager/src/manager.rs:132— ClassTooLong — 802 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 26 methods, 2 blocks, lines 132-1333. The bar is 400 significant lines; this is 402 over it, 2.01× 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: TrackList editor/src/plugins/animation/track.rs:610— ClassTooLong — 798 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 8 methods, 2 blocks, lines 610-1741. The bar is 400 significant lines; this is 398 over it, 2.00× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: CurveEditor fyrox-ui/src/curve/mod.rs:426— ClassTooLong — 797 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 24 methods, 4 blocks, lines 426-1731. The bar is 400 significant lines; this is 397 over it, 1.99× 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: SceneDrawingContext fyrox-impl/src/scene/debug.rs:90— ClassTooLong — 752 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 21 methods, 4 blocks, lines 90-1114. The bar is 400 significant lines; this is 352 over it, 1.88× 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: TextBox fyrox-ui/src/text_box.rs:432— ClassTooLong — 746 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 33 methods, 5 blocks, lines 432-1536. The bar is 400 significant lines; this is 346 over it, 1.87× 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: DeferredLightRenderer fyrox-impl/src/renderer/light.rs:74— ClassTooLong — 742 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 3 methods, 2 blocks, lines 74-1079. The bar is 400 significant lines; this is 342 over it, 1.86× 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: PhysicsWorld fyrox-impl/src/scene/graph/physics/mod.rs:916— ClassTooLong — 683 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 21 methods, 5 blocks, lines 916-2043. The bar is 400 significant lines; this is 283 over it, 1.71× 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: GameScene editor/src/scene/mod.rs:134— ClassTooLong — 670 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 7 methods, 3 blocks, lines 134-1130. The bar is 400 significant lines; this is 270 over it, 1.68× 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: ResourceManagerState fyrox-resource/src/manager.rs:87— ClassTooLong — 665 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 53 methods, 2 blocks, lines 87-2093. The bar is 400 significant lines; this is 265 over it, 1.66× 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: Color fyrox-core/src/color.rs:37— ClassTooLong — 633 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 15 methods, 13 blocks, lines 37-983. The bar is 400 significant lines; this is 233 over it, 1.58× 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: WgpuFrameBuffer fyrox-graphics-wgpu/src/framebuffer.rs:202— ClassTooLong — 631 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 4 methods, 3 blocks, lines 202-1058. The bar is 400 significant lines; this is 231 over it, 1.58× 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: Tile fyrox-ui/src/dock/tile.rs:264— ClassTooLong — 630 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 9 methods, 4 blocks, lines 264-1216. The bar is 400 significant lines; this is 230 over it, 1.58× 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: AssetBrowser editor/src/asset/mod.rs:119— ClassTooLong — 628 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 17 methods, 2 blocks, lines 119-1081. The bar is 400 significant lines; this is 228 over it, 1.57× 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: Renderer fyrox-impl/src/renderer/mod.rs:414— ClassTooLong — 627 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 23 methods, 2 blocks, lines 414-1511. The bar is 400 significant lines; this is 227 over it, 1.57× 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: PhysicsWorld fyrox-impl/src/scene/dim2/physics/mod.rs:467— ClassTooLong — 624 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 21 methods, 6 blocks, lines 467-1519. The bar is 400 significant lines; this is 224 over it, 1.56× 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: Widget fyrox-ui/src/widget.rs:572— ClassTooLong — 617 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 110 methods, 2 blocks, lines 572-1655. The bar is 400 significant lines; this is 217 over it, 1.54× 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: RagdollPreset editor/src/plugins/ragdoll.rs:79— ClassTooLong — 610 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 5 methods, 3 blocks, lines 79-1011. The bar is 400 significant lines; this is 210 over it, 1.53× 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: FormattedText fyrox-ui/src/formatted_text.rs:264— ClassTooLong — 608 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 72 methods, 2 blocks, lines 264-1205. The bar is 400 significant lines; this is 208 over it, 1.52× 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: Pool fyrox-core/src/pool/mod.rs:69— ClassTooLong — 603 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 52 methods, 15 blocks, lines 69-1481. The bar is 400 significant lines; this is 203 over it, 1.51× 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: Toolbar editor/src/plugins/animation/toolbar.rs:81— ClassTooLong — 603 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 7 methods, 2 blocks, lines 81-1146. The bar is 400 significant lines; this is 203 over it, 1.51× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Duplicated block (9 lines × 2) editor/src/export/mod.rs:285— editor/src/export/mod.rs:285-293 | editor/src/scene/dialog.rs:69-77 — 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 (9 lines × 2) editor/src/interaction/gizmo/move_gizmo.rs:346— editor/src/interaction/gizmo/move_gizmo.rs:346-354 | editor/src/interaction/gizmo/scale_gizmo.rs:261-269 — before extracting anything, compare `editor/src/interaction/gizmo/move_gizmo.rs` and `editor/src/interaction/gizmo/scale_gizmo.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 44 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) editor/src/interaction/navmesh/mod.rs:270— editor/src/interaction/navmesh/mod.rs:270-278 | editor/src/interaction/navmesh/mod.rs:436-444 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) editor/src/plugins/absm/connection.rs:94— editor/src/plugins/absm/connection.rs:94-102 | editor/src/plugins/absm/transition.rs:136-144 — 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 (9 lines × 2) editor/src/plugins/absm/mod.rs:297— editor/src/plugins/absm/mod.rs:297-305 | editor/src/plugins/absm/mod.rs:309-317 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) editor/src/plugins/animation/toolbar.rs:431— editor/src/plugins/animation/toolbar.rs:431-439 | editor/src/plugins/animation/toolbar.rs:553-561 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) editor/src/plugins/collider/cone.rs:116— editor/src/plugins/collider/cone.rs:116-124 | editor/src/plugins/collider/cylinder.rs:118-127 — before extracting anything, compare `editor/src/plugins/collider/cone.rs` and `editor/src/plugins/collider/cylinder.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 31 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) editor/src/plugins/tilemap/colliders_tab.rs:171— editor/src/plugins/tilemap/colliders_tab.rs:171-179 | editor/src/plugins/tilemap/properties_tab.rs:291-299 — before extracting anything, compare `editor/src/plugins/tilemap/colliders_tab.rs` and `editor/src/plugins/tilemap/properties_tab.rs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 157 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) editor/src/plugins/tilemap/commands.rs:842— editor/src/plugins/tilemap/commands.rs:842-850 | editor/src/plugins/tilemap/commands.rs:993-1001 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) editor/src/scene/container.rs:147— editor/src/scene/container.rs:147-155 | editor/src/scene/container.rs:183-191 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) editor/src/scene/property.rs:101— editor/src/scene/property.rs:101-109 | editor/src/scene/selector.rs:219-227 — before extracting anything, compare `editor/src/scene/property.rs` and `editor/src/scene/selector.rs` as WHOLE FILES: this scan already matched 5 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 (9 lines × 2) fyrox-core/src/pool/mod.rs:912— fyrox-core/src/pool/mod.rs:912-920 | fyrox-core/src/pool/mod.rs:959-967 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) fyrox-graph/src/lib.rs:1517— fyrox-graph/src/lib.rs:1517-1525 | fyrox-graph/src/lib.rs:1585-1593 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) fyrox-impl/src/resource/fbx/mod.rs:450— fyrox-impl/src/resource/fbx/mod.rs:450-458 | fyrox-impl/src/resource/fbx/mod.rs:463-471 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) fyrox-impl/src/scene/dim2/physics/mod.rs:625— fyrox-impl/src/scene/dim2/physics/mod.rs:625-633 | fyrox-impl/src/scene/graph/physics/mod.rs:1067-1075 — before extracting anything, compare `fyrox-impl/src/scene/dim2/physics/mod.rs` and `fyrox-impl/src/scene/graph/physics/mod.rs` as WHOLE FILES: this scan already matched 34 separate duplicated blocks between them, totalling at least 555 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 (9 lines × 2) fyrox-impl/src/scene/dim2/rigidbody.rs:163— fyrox-impl/src/scene/dim2/rigidbody.rs:163-171 | fyrox-impl/src/scene/rigidbody.rs:247-255 — before extracting anything, compare `fyrox-impl/src/scene/dim2/rigidbody.rs` and `fyrox-impl/src/scene/rigidbody.rs` as WHOLE FILES: this scan already matched 9 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. 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 (9 lines × 2) fyrox-impl/src/scene/dim2/rigidbody.rs:201— fyrox-impl/src/scene/dim2/rigidbody.rs:201-209 | fyrox-impl/src/scene/rigidbody.rs:290-298 — before extracting anything, compare `fyrox-impl/src/scene/dim2/rigidbody.rs` and `fyrox-impl/src/scene/rigidbody.rs` as WHOLE FILES: this scan already matched 9 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. 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 (9 lines × 2) fyrox-impl/src/scene/dim2/rigidbody.rs:211— fyrox-impl/src/scene/dim2/rigidbody.rs:211-219 | fyrox-impl/src/scene/rigidbody.rs:302-310 — before extracting anything, compare `fyrox-impl/src/scene/dim2/rigidbody.rs` and `fyrox-impl/src/scene/rigidbody.rs` as WHOLE FILES: this scan already matched 9 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. 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 (9 lines × 2) fyrox-impl/src/scene/dim2/rigidbody.rs:662— fyrox-impl/src/scene/dim2/rigidbody.rs:662-670 | fyrox-impl/src/scene/rigidbody.rs:838-846 — before extracting anything, compare `fyrox-impl/src/scene/dim2/rigidbody.rs` and `fyrox-impl/src/scene/rigidbody.rs` as WHOLE FILES: this scan already matched 9 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. 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 (9 lines × 2) fyrox-impl/src/scene/mesh/surface.rs:420— fyrox-impl/src/scene/mesh/surface.rs:420-428 | fyrox-impl/src/scene/mesh/surface.rs:458-466 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) fyrox-impl/src/scene/particle_system/emitter/base.rs:103— fyrox-impl/src/scene/particle_system/emitter/base.rs:103-111 | fyrox-impl/src/scene/particle_system/emitter/base.rs:430-438 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) fyrox-impl/src/scene/terrain/mod.rs:2273— fyrox-impl/src/scene/terrain/mod.rs:2273-2281 | fyrox-impl/src/scene/terrain/mod.rs:2300-2308 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) fyrox-impl/src/scene/terrain/mod.rs:2277— fyrox-impl/src/scene/terrain/mod.rs:2277-2285 | fyrox-impl/src/scene/terrain/mod.rs:2309-2317 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) fyrox-impl/src/scene/tilemap/mod.rs:596— fyrox-impl/src/scene/tilemap/mod.rs:596-604 | fyrox-impl/src/scene/tilemap/mod.rs:607-615 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) fyrox-ui/src/matrix.rs:142— fyrox-ui/src/matrix.rs:142-150 | fyrox-ui/src/vec.rs:178-186 — before extracting anything, compare `fyrox-ui/src/matrix.rs` and `fyrox-ui/src/vec.rs` 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 (7 lines × 2) editor/src/plugins/absm/command/mod.rs:196— editor/src/plugins/absm/command/mod.rs:196-202 | editor/src/plugins/animation/command/mod.rs:56-62 — 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 (7 lines × 2) editor/src/plugins/absm/mod.rs:723— editor/src/plugins/absm/mod.rs:723-729 | editor/src/plugins/absm/mod.rs:738-744 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) editor/src/plugins/collider/cuboid.rs:79— editor/src/plugins/collider/cuboid.rs:79-85 | editor/src/plugins/collider/cuboid2d.rs:75-81 — 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) editor/src/plugins/collider/cuboid.rs:129— editor/src/plugins/collider/cuboid.rs:129-135 | editor/src/plugins/collider/cuboid2d.rs:117-123 — 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) editor/src/plugins/ragdoll.rs:738— editor/src/plugins/ragdoll.rs:738-744 | editor/src/plugins/ragdoll.rs:774-780 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) editor/src/plugins/tilemap/autotile.rs:272— editor/src/plugins/tilemap/autotile.rs:272-278 | editor/src/plugins/tilemap/autotile.rs:644-650 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) editor/src/plugins/tilemap/tile_inspector.rs:597— editor/src/plugins/tilemap/tile_inspector.rs:597-603 | editor/src/plugins/tilemap/tile_inspector.rs:671-677 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) editor/src/scene/property.rs:312— editor/src/scene/property.rs:312-318 | editor/src/scene/selector.rs:304-310 — before extracting anything, compare `editor/src/scene/property.rs` and `editor/src/scene/selector.rs` as WHOLE FILES: this scan already matched 5 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 (7 lines × 2) fyrox-animation/src/machine/node/blendspace.rs:132— fyrox-animation/src/machine/node/blendspace.rs:132-138 | fyrox-animation/src/machine/node/blendspace.rs:167-173 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) fyrox-autotile/src/auto.rs:174— fyrox-autotile/src/auto.rs:174-180 | fyrox-autotile/src/auto.rs:184-190 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) fyrox-impl/src/renderer/convolution.rs:97— fyrox-impl/src/renderer/convolution.rs:97-103 | fyrox-impl/src/renderer/convolution.rs:180-186 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) fyrox-impl/src/resource/gltf/surface.rs:490— fyrox-impl/src/resource/gltf/surface.rs:490-496 | fyrox-impl/src/resource/gltf/surface.rs:535-541 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) fyrox-impl/src/scene/debug.rs:605— fyrox-impl/src/scene/debug.rs:605-611 | fyrox-impl/src/scene/debug.rs:614-620 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) fyrox-impl/src/scene/dim2/rigidbody.rs:518— fyrox-impl/src/scene/dim2/rigidbody.rs:518-524 | fyrox-impl/src/scene/rigidbody.rs:659-665 — before extracting anything, compare `fyrox-impl/src/scene/dim2/rigidbody.rs` and `fyrox-impl/src/scene/rigidbody.rs` as WHOLE FILES: this scan already matched 9 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. 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 (7 lines × 2) fyrox-impl/src/scene/tilemap/tileset.rs:389— fyrox-impl/src/scene/tilemap/tileset.rs:389-395 | fyrox-impl/src/scene/tilemap/tileset.rs:422-428 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) fyrox-ui/src/color/mod.rs:135— fyrox-ui/src/color/mod.rs:135-141 | fyrox-ui/src/color/mod.rs:416-422 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) fyrox-ui/src/formatted_text/textwrapper.rs:99— fyrox-ui/src/formatted_text/textwrapper.rs:99-105 | fyrox-ui/src/formatted_text/textwrapper.rs:161-167 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) fyrox-ui/src/image.rs:244— fyrox-ui/src/image.rs:244-250 | fyrox-ui/src/image.rs:260-266 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) fyrox-ui/src/key.rs:284— fyrox-ui/src/key.rs:284-290 | fyrox-ui/src/key.rs:483-489 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) editor/src/plugins/collider/capsule.rs:41— editor/src/plugins/collider/capsule.rs:41-47 | editor/src/plugins/collider/capsule2d.rs:41-47 — 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) editor/src/plugins/collider/triangle.rs:41— editor/src/plugins/collider/triangle.rs:41-47 | editor/src/plugins/collider/triangle2d.rs:41-47 — 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) fyrox-impl/src/scene/tilemap/brush.rs:322— fyrox-impl/src/scene/tilemap/brush.rs:322-328 | fyrox-impl/src/scene/tilemap/tileset.rs:2014-2020 — 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) fyrox-ui/src/draw.rs:927— fyrox-ui/src/draw.rs:927-933 | fyrox-ui/src/vector_image.rs:106-112 — 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) editor/src/plugins/inspector/editors/handle.rs:486— editor/src/plugins/inspector/editors/handle.rs:486-493 | fyrox-ui/src/inspector/editors/rect.rs:89-95 — 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 (7 lines × 2) editor/src/plugins/inspector/editors/triangle_buffer.rs:75— editor/src/plugins/inspector/editors/triangle_buffer.rs:75-81 | editor/src/plugins/inspector/editors/vertex_buffer.rs:75-81 — 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.
TooManyMethods: Widget fyrox-ui/src/widget.rs:572— TooManyMethods — 110 methods. The bar is 30 methods; this is 80 over it, 3.67× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: UserInterface fyrox-ui/src/lib.rs:736— TooManyMethods — 95 methods. The bar is 30 methods; this is 65 over it, 3.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Base fyrox-impl/src/scene/base.rs:389— TooManyMethods — 76 methods. The bar is 30 methods; this is 46 over it, 2.53× 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: Graph fyrox-impl/src/scene/graph/mod.rs:130— TooManyMethods — 73 methods. The bar is 30 methods; this is 43 over it, 2.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.
TooManyMethods: FormattedText fyrox-ui/src/formatted_text.rs:264— TooManyMethods — 72 methods. The bar is 30 methods; this is 42 over it, 2.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: Terrain fyrox-impl/src/scene/terrain/mod.rs:1037— TooManyMethods — 64 methods. The bar is 30 methods; this is 34 over it, 2.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: TileSet fyrox-impl/src/scene/tilemap/tileset.rs:1337— 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: ResourceManagerState fyrox-resource/src/manager.rs:87— 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: Pool fyrox-core/src/pool/mod.rs:69— TooManyMethods — 52 methods. The bar is 30 methods; this is 22 over it, 1.73× 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: PaletteWidget editor/src/plugins/tilemap/palette.rs:173— TooManyMethods — 49 methods. The bar is 30 methods; this is 19 over it, 1.63× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Animation fyrox-animation/src/lib.rs:269— TooManyMethods — 49 methods. The bar is 30 methods; this is 19 over it, 1.63× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: OptionTileSet fyrox-impl/src/scene/tilemap/tileset.rs:859— TooManyMethods — 47 methods. The bar is 30 methods; this is 17 over it, 1.57× 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: RigidBody fyrox-impl/src/scene/rigidbody.rs:175— TooManyMethods — 46 methods. The bar is 30 methods; this is 16 over it, 1.53× 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: WidgetBuilder fyrox-ui/src/widget.rs:1688— TooManyMethods — 46 methods. The bar is 30 methods; this is 16 over it, 1.53× 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: SoundSource fyrox-sound/src/source.rs:81— TooManyMethods — 41 methods. The bar is 30 methods; this is 11 over it, 1.37× 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: MachineLayer fyrox-animation/src/machine/layer.rs:86— TooManyMethods — 40 methods. The bar is 30 methods; this is 10 over it, 1.33× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: RigidBody fyrox-impl/src/scene/dim2/rigidbody.rs:98— TooManyMethods — 38 methods. The bar is 30 methods; this is 8 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.
TooManyMethods: Texture fyrox-texture/src/lib.rs:258— TooManyMethods — 37 methods. The bar is 30 methods; this is 7 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.
TooManyMethods: TileEditorState editor/src/plugins/tilemap/tile_inspector.rs:97— TooManyMethods — 35 methods. The bar is 30 methods; this is 5 over it, 1.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Engine fyrox-impl/src/engine/mod.rs:316— 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: Camera fyrox-impl/src/scene/camera.rs:359— 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: ResourceManager fyrox-resource/src/manager.rs:123— 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: TextBox fyrox-ui/src/text_box.rs:432— 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: SpriteSheetAnimation fyrox-animation/src/spritesheet/mod.rs:165— TooManyMethods — 32 methods. The bar is 30 methods; this is 2 over it, 1.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Visitor fyrox-core/src/visitor/mod.rs:312— TooManyMethods — 32 methods. The bar is 30 methods; this is 2 over it, 1.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Duplicated block (10 lines × 2) editor/src/plugins/ragdoll.rs:717— editor/src/plugins/ragdoll.rs:717-726 | editor/src/plugins/ragdoll.rs:753-762 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) editor/src/plugins/tilemap/colliders_tab.rs:128— editor/src/plugins/tilemap/colliders_tab.rs:128-137 | editor/src/plugins/tilemap/macro_tab.rs:135-144 — before extracting anything, compare `editor/src/plugins/tilemap/colliders_tab.rs` and `editor/src/plugins/tilemap/macro_tab.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 113 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 2) editor/src/plugins/tilemap/colliders_tab.rs:122— editor/src/plugins/tilemap/colliders_tab.rs:122-131 | editor/src/plugins/tilemap/properties_tab.rs:147-156 — before extracting anything, compare `editor/src/plugins/tilemap/colliders_tab.rs` and `editor/src/plugins/tilemap/properties_tab.rs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 157 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 2) editor/src/plugins/tilemap/colliders_tab.rs:149— editor/src/plugins/tilemap/colliders_tab.rs:149-158 | editor/src/plugins/tilemap/properties_tab.rs:253-262 — before extracting anything, compare `editor/src/plugins/tilemap/colliders_tab.rs` and `editor/src/plugins/tilemap/properties_tab.rs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 157 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 2) editor/src/plugins/tilemap/interaction_mode.rs:514— editor/src/plugins/tilemap/interaction_mode.rs:514-523 | editor/src/plugins/tilemap/interaction_mode.rs:698-707 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) editor/src/plugins/tilemap/palette.rs:1558— editor/src/plugins/tilemap/palette.rs:1558-1567 | editor/src/plugins/tilemap/palette.rs:1603-1612 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) editor/src/plugins/tilemap/panel.rs:359— editor/src/plugins/tilemap/panel.rs:359-368 | editor/src/plugins/tilemap/properties_tab.rs:265-274 — 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) editor/src/ui_scene/menu.rs:234— editor/src/ui_scene/menu.rs:234-243 | editor/src/world/menu.rs:395-404 — 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 (10 lines × 2) fyrox-animation/src/container.rs:191— fyrox-animation/src/container.rs:191-200 | fyrox-animation/src/container.rs:216-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 (10 lines × 2) fyrox-graphics-wgpu/src/framebuffer.rs:952— fyrox-graphics-wgpu/src/framebuffer.rs:952-961 | fyrox-graphics-wgpu/src/read_buffer.rs:124-133 — 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) fyrox-impl/src/resource/gltf/animation.rs:518— fyrox-impl/src/resource/gltf/animation.rs:518-527 | fyrox-impl/src/resource/gltf/animation.rs:583-592 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) fyrox-impl/src/scene/collider.rs:971— fyrox-impl/src/scene/collider.rs:971-980 | fyrox-impl/src/scene/dim2/collider.rs:627-636 — before extracting anything, compare `fyrox-impl/src/scene/collider.rs` and `fyrox-impl/src/scene/dim2/collider.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 93 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 (10 lines × 2) fyrox-impl/src/scene/dim2/physics/mod.rs:743— fyrox-impl/src/scene/dim2/physics/mod.rs:743-752 | fyrox-impl/src/scene/graph/physics/mod.rs:1186-1195 — before extracting anything, compare `fyrox-impl/src/scene/dim2/physics/mod.rs` and `fyrox-impl/src/scene/graph/physics/mod.rs` as WHOLE FILES: this scan already matched 34 separate duplicated blocks between them, totalling at least 555 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 (10 lines × 2) fyrox-impl/src/scene/dim2/physics/mod.rs:1125— fyrox-impl/src/scene/dim2/physics/mod.rs:1125-1134 | fyrox-impl/src/scene/graph/physics/mod.rs:1623-1632 — before extracting anything, compare `fyrox-impl/src/scene/dim2/physics/mod.rs` and `fyrox-impl/src/scene/graph/physics/mod.rs` as WHOLE FILES: this scan already matched 34 separate duplicated blocks between them, totalling at least 555 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 (10 lines × 2) fyrox-impl/src/scene/dim2/physics/mod.rs:1480— fyrox-impl/src/scene/dim2/physics/mod.rs:1480-1489 | fyrox-impl/src/scene/graph/physics/mod.rs:2002-2011 — before extracting anything, compare `fyrox-impl/src/scene/dim2/physics/mod.rs` and `fyrox-impl/src/scene/graph/physics/mod.rs` as WHOLE FILES: this scan already matched 34 separate duplicated blocks between them, totalling at least 555 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 (10 lines × 2) fyrox-impl/src/scene/graph/mod.rs:503— fyrox-impl/src/scene/graph/mod.rs:503-512 | fyrox-ui/src/lib.rs:1290-1299 — 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 (10 lines × 2) fyrox-impl/src/scene/graph/mod.rs:577— fyrox-impl/src/scene/graph/mod.rs:577-586 | fyrox-impl/src/scene/graph/mod.rs:615-624 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) fyrox-ui/src/bit.rs:299— fyrox-ui/src/bit.rs:299-308 | fyrox-ui/src/bit.rs:311-320 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) fyrox-ui/src/input.rs:161— fyrox-ui/src/input.rs:161-170 | fyrox-ui/src/messagebox.rs:245-254 — 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) fyrox-ui/src/messagebox.rs:342— fyrox-ui/src/messagebox.rs:342-351 | fyrox-ui/src/messagebox.rs:386-395 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) fyrox-impl/src/scene/dim2/physics/mod.rs:777— fyrox-impl/src/scene/dim2/physics/mod.rs:777-786 | fyrox-impl/src/scene/graph/physics/mod.rs:1220-1229 — before extracting anything, compare `fyrox-impl/src/scene/dim2/physics/mod.rs` and `fyrox-impl/src/scene/graph/physics/mod.rs` as WHOLE FILES: this scan already matched 34 separate duplicated blocks between them, totalling at least 555 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 (10 lines × 2) fyrox-impl/src/scene/dim2/physics/mod.rs:825— fyrox-impl/src/scene/dim2/physics/mod.rs:825-834 | fyrox-impl/src/scene/graph/physics/mod.rs:1268-1277 — before extracting anything, compare `fyrox-impl/src/scene/dim2/physics/mod.rs` and `fyrox-impl/src/scene/graph/physics/mod.rs` as WHOLE FILES: this scan already matched 34 separate duplicated blocks between them, totalling at least 555 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 (10 lines × 2) fyrox-impl/src/scene/dim2/physics/mod.rs:988— fyrox-impl/src/scene/dim2/physics/mod.rs:988-997 | fyrox-impl/src/scene/graph/physics/mod.rs:1428-1437 — before extracting anything, compare `fyrox-impl/src/scene/dim2/physics/mod.rs` and `fyrox-impl/src/scene/graph/physics/mod.rs` as WHOLE FILES: this scan already matched 34 separate duplicated blocks between them, totalling at least 555 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 (10 lines × 2) fyrox-graphics-gl/src/server.rs:1361— fyrox-graphics-gl/src/server.rs:1361-1370 | fyrox-graphics-wgpu/src/server.rs:608-617 — 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 (10 lines × 2) editor/src/interaction/gizmo/scale_gizmo.rs:136— editor/src/interaction/gizmo/scale_gizmo.rs:136-145 | editor/src/interaction/terrain.rs:253-262 — 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 (6 lines × 2) editor/src/lib.rs:701— editor/src/lib.rs:701-706 | editor/src/lib.rs:724-729 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) editor/src/plugins/tilemap/colliders_tab.rs:312— editor/src/plugins/tilemap/colliders_tab.rs:312-317 | editor/src/plugins/tilemap/properties_tab.rs:619-624 — before extracting anything, compare `editor/src/plugins/tilemap/colliders_tab.rs` and `editor/src/plugins/tilemap/properties_tab.rs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 157 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 2) editor/src/scene/property.rs:378— editor/src/scene/property.rs:378-383 | editor/src/scene/selector.rs:256-261 — before extracting anything, compare `editor/src/scene/property.rs` and `editor/src/scene/selector.rs` as WHOLE FILES: this scan already matched 5 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 (6 lines × 2) fyrox-core-derive/src/reflect.rs:207— fyrox-core-derive/src/reflect.rs:207-212 | fyrox-core-derive/src/reflect.rs:324-329 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) fyrox-graphics-gl/src/texture.rs:358— fyrox-graphics-gl/src/texture.rs:358-363 | fyrox-graphics-wgpu/src/texture.rs:450-456 — 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 (6 lines × 2) fyrox-impl/src/renderer/bundle.rs:1194— fyrox-impl/src/renderer/bundle.rs:1194-1199 | fyrox-impl/src/renderer/bundle.rs:1259-1264 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) fyrox-impl/src/renderer/light_volume.rs:127— fyrox-impl/src/renderer/light_volume.rs:127-132 | fyrox-impl/src/renderer/light_volume.rs:187-192 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) fyrox-impl/src/renderer/ui_renderer.rs:145— fyrox-impl/src/renderer/ui_renderer.rs:145-150 | fyrox-impl/src/renderer/ui_renderer.rs:155-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 (6 lines × 2) fyrox-impl/src/scene/debug.rs:1057— fyrox-impl/src/scene/debug.rs:1057-1062 | fyrox-impl/src/scene/debug.rs:1065-1070 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) fyrox-impl/src/scene/dim2/physics/mod.rs:253— fyrox-impl/src/scene/dim2/physics/mod.rs:253-258 | fyrox-impl/src/scene/graph/physics/mod.rs:376-381 — before extracting anything, compare `fyrox-impl/src/scene/dim2/physics/mod.rs` and `fyrox-impl/src/scene/graph/physics/mod.rs` as WHOLE FILES: this scan already matched 34 separate duplicated blocks between them, totalling at least 555 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 (6 lines × 2) fyrox-impl/src/scene/dim2/physics/mod.rs:1004— fyrox-impl/src/scene/dim2/physics/mod.rs:1004-1009 | fyrox-impl/src/scene/graph/physics/mod.rs:1444-1449 — before extracting anything, compare `fyrox-impl/src/scene/dim2/physics/mod.rs` and `fyrox-impl/src/scene/graph/physics/mod.rs` as WHOLE FILES: this scan already matched 34 separate duplicated blocks between them, totalling at least 555 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 (6 lines × 2) fyrox-impl/src/scene/tilemap/mod.rs:201— fyrox-impl/src/scene/tilemap/mod.rs:201-206 | fyrox-impl/src/scene/tilemap/mod.rs:246-251 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) fyrox-impl/src/scene/tilemap/tileset.rs:399— fyrox-impl/src/scene/tilemap/tileset.rs:399-404 | fyrox-impl/src/scene/tilemap/tileset.rs:432-437 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) fyrox-ui/src/bit.rs:326— fyrox-ui/src/bit.rs:326-331 | fyrox-ui/src/bit.rs:352-357 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) fyrox-ui/src/scroll_bar.rs:270— fyrox-ui/src/scroll_bar.rs:270-275 | fyrox-ui/src/scroll_bar.rs:292-297 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) fyrox-ui/src/utils.rs:150— fyrox-ui/src/utils.rs:150-155 | fyrox-ui/src/utils.rs:178-183 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) fyrox-ui/src/wrap_panel.rs:191— fyrox-ui/src/wrap_panel.rs:191-196 | fyrox-ui/src/wrap_panel.rs:209-214 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) fyrox-impl/src/scene/collider.rs:963— fyrox-impl/src/scene/collider.rs:963-968 | fyrox-impl/src/scene/dim2/collider.rs:619-624 — before extracting anything, compare `fyrox-impl/src/scene/collider.rs` and `fyrox-impl/src/scene/dim2/collider.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 93 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 (6 lines × 2) fyrox-impl/src/scene/dim2/rectangle.rs:289— fyrox-impl/src/scene/dim2/rectangle.rs:289-294 | fyrox-impl/src/scene/sprite.rs:291-296 — before extracting anything, compare `fyrox-impl/src/scene/dim2/rectangle.rs` and `fyrox-impl/src/scene/sprite.rs` as WHOLE FILES: this scan already matched 3 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. 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 (6 lines × 2) editor/src/plugins/absm/state_graph/mod.rs:73— editor/src/plugins/absm/state_graph/mod.rs:73-78 | editor/src/plugins/absm/state_viewer/mod.rs:108-113 — `editor/src/plugins/absm/state_graph/mod.rs` and `editor/src/plugins/absm/state_viewer/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 46 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (6 lines × 2) fyrox-impl/src/scene/animation/mod.rs:83— fyrox-impl/src/scene/animation/mod.rs:83-88 | fyrox-ui/src/animation.rs:83-88 — 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 (6 lines × 2) fyrox-impl/src/scene/collider.rs:1019— fyrox-impl/src/scene/collider.rs:1019-1024 | fyrox-impl/src/scene/dim2/collider.rs:675-680 — before extracting anything, compare `fyrox-impl/src/scene/collider.rs` and `fyrox-impl/src/scene/dim2/collider.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 93 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 (6 lines × 2) editor/src/plugins/tilemap/commands.rs:1065— editor/src/plugins/tilemap/commands.rs:1065-1070 | editor/src/plugins/tilemap/commands.rs:1100-1105 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) editor/src/mesh.rs:227— editor/src/mesh.rs:227-232 | editor/src/mesh.rs:245-250 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) editor/src/interaction/gizmo/move_gizmo.rs:253— editor/src/interaction/gizmo/move_gizmo.rs:253-258 | editor/src/interaction/gizmo/scale_gizmo.rs:193-198 — before extracting anything, compare `editor/src/interaction/gizmo/move_gizmo.rs` and `editor/src/interaction/gizmo/scale_gizmo.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 44 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 2) editor/src/audio/preview.rs:183— editor/src/audio/preview.rs:183-195 | editor/src/particle.rs:226-238 — 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 (13 lines × 2) editor/src/interaction/move_mode.rs:229— editor/src/interaction/move_mode.rs:229-241 | editor/src/scene/mod.rs:660-672 — 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 (13 lines × 2) editor/src/plugins/absm/mod.rs:249— editor/src/plugins/absm/mod.rs:249-261 | editor/src/plugins/animation/mod.rs:322-334 — `editor/src/plugins/absm/mod.rs` and `editor/src/plugins/animation/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 6 separate duplicated blocks between them, totalling at least 68 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (13 lines × 2) editor/src/plugins/absm/state_graph/mod.rs:201— editor/src/plugins/absm/state_graph/mod.rs:201-213 | editor/src/plugins/absm/state_viewer/mod.rs:297-309 — `editor/src/plugins/absm/state_graph/mod.rs` and `editor/src/plugins/absm/state_viewer/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 46 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (13 lines × 2) editor/src/plugins/tilemap/tile_inspector.rs:623— editor/src/plugins/tilemap/tile_inspector.rs:623-635 | editor/src/plugins/tilemap/tile_inspector.rs:697-709 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) fyrox-core/src/visitor/reader/ascii.rs:356— fyrox-core/src/visitor/reader/ascii.rs:356-368 | fyrox-core/src/visitor/reader/binary.rs:228-240 — 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 (13 lines × 2) fyrox-impl/src/resource/gltf/animation.rs:494— fyrox-impl/src/resource/gltf/animation.rs:494-506 | fyrox-impl/src/resource/gltf/animation.rs:629-641 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) fyrox-impl/src/resource/gltf/animation.rs:620— fyrox-impl/src/resource/gltf/animation.rs:620-632 | fyrox-impl/src/resource/gltf/animation.rs:651-663 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) fyrox-impl/src/scene/collider.rs:1112— fyrox-impl/src/scene/collider.rs:1112-1124 | fyrox-impl/src/scene/dim2/collider.rs:770-782 — before extracting anything, compare `fyrox-impl/src/scene/collider.rs` and `fyrox-impl/src/scene/dim2/collider.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 93 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 2) fyrox-impl/src/scene/dim2/physics/mod.rs:603— fyrox-impl/src/scene/dim2/physics/mod.rs:603-615 | fyrox-impl/src/scene/graph/physics/mod.rs:1045-1057 — before extracting anything, compare `fyrox-impl/src/scene/dim2/physics/mod.rs` and `fyrox-impl/src/scene/graph/physics/mod.rs` as WHOLE FILES: this scan already matched 34 separate duplicated blocks between them, totalling at least 555 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 2) fyrox-impl/src/scene/graph/physics/mod.rs:580— fyrox-impl/src/scene/graph/physics/mod.rs:580-592 | fyrox-impl/src/scene/graph/physics/mod.rs:669-681 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) fyrox-impl/src/scene/tilemap/mod.rs:209— fyrox-impl/src/scene/tilemap/mod.rs:209-221 | fyrox-impl/src/scene/tilemap/mod.rs:254-266 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) fyrox-ui/src/inspector/editors/cell.rs:152— fyrox-ui/src/inspector/editors/cell.rs:152-164 | fyrox-ui/src/inspector/editors/style.rs:624-636 — 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 (13 lines × 2) fyrox-ui/src/inspector/editors/hashmap/dialog.rs:231— fyrox-ui/src/inspector/editors/hashmap/dialog.rs:231-243 | fyrox-ui/src/inspector/editors/style.rs:251-263 — 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 (13 lines × 2) fyrox-ui/src/inspector/editors/hashmap/mod.rs:392— fyrox-ui/src/inspector/editors/hashmap/mod.rs:392-404 | fyrox-ui/src/inspector/editors/hashmap/mod.rs:429-441 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) fyrox-ui/src/inspector/editors/immutable_string.rs:56— fyrox-ui/src/inspector/editors/immutable_string.rs:56-68 | fyrox-ui/src/inspector/editors/string.rs:52-64 — 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 (13 lines × 2) project-manager/src/manager.rs:200— project-manager/src/manager.rs:200-212 | project-manager/src/manager.rs:214-226 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) fyrox-impl/src/scene/tilemap/tileset.rs:78— fyrox-impl/src/scene/tilemap/tileset.rs:78-90 | fyrox-ui/src/style/resource.rs:57-69 — 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 (13 lines × 2) fyrox-impl/src/resource/curve/mod.rs:47— fyrox-impl/src/resource/curve/mod.rs:47-59 | fyrox-impl/src/scene/tilemap/brush.rs:70-82 — 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 (13 lines × 2) fyrox-impl/src/renderer/shadow/point.rs:80— fyrox-impl/src/renderer/shadow/point.rs:80-92 | fyrox-impl/src/renderer/shadow/spot.rs:65-77 — 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 (13 lines × 2) fyrox-build-tools/src/lib.rs:117— fyrox-build-tools/src/lib.rs:117-129 | fyrox-build-tools/src/lib.rs:244-256 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) fyrox-impl/src/scene/collider.rs:1049— fyrox-impl/src/scene/collider.rs:1049-1061 | fyrox-impl/src/scene/dim2/collider.rs:707-719 — before extracting anything, compare `fyrox-impl/src/scene/collider.rs` and `fyrox-impl/src/scene/dim2/collider.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 93 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 2) fyrox-impl/src/scene/mesh/surface.rs:576— fyrox-impl/src/scene/mesh/surface.rs:576-588 | fyrox-impl/src/scene/mesh/surface.rs:591-603 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) editor/src/audio/preview.rs:316— editor/src/audio/preview.rs:316-323 | editor/src/particle.rs:329-336 — 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 (8 lines × 2) editor/src/interaction/rotate_mode.rs:201— editor/src/interaction/rotate_mode.rs:201-208 | editor/src/interaction/scale_mode.rs:193-200 — before extracting anything, compare `editor/src/interaction/rotate_mode.rs` and `editor/src/interaction/scale_mode.rs` as WHOLE FILES: this scan already matched 7 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 (8 lines × 2) editor/src/lib.rs:686— editor/src/lib.rs:686-693 | editor/src/lib.rs:709-716 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) editor/src/plugins/absm/state_graph/mod.rs:369— editor/src/plugins/absm/state_graph/mod.rs:369-379 | editor/src/plugins/absm/state_graph/mod.rs:476-483 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) editor/src/plugins/absm/state_viewer/mod.rs:637— editor/src/plugins/absm/state_viewer/mod.rs:637-644 | editor/src/plugins/absm/state_viewer/mod.rs:654-661 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) editor/src/plugins/tilemap/autotile.rs:222— editor/src/plugins/tilemap/autotile.rs:222-229 | editor/src/plugins/tilemap/wfc.rs:269-276 — before extracting anything, compare `editor/src/plugins/tilemap/autotile.rs` and `editor/src/plugins/tilemap/wfc.rs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 142 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) editor/src/plugins/tilemap/autotile.rs:581— editor/src/plugins/tilemap/autotile.rs:581-588 | editor/src/plugins/tilemap/wfc.rs:557-564 — before extracting anything, compare `editor/src/plugins/tilemap/autotile.rs` and `editor/src/plugins/tilemap/wfc.rs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 142 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) editor/src/plugins/tilemap/autotile.rs:878— editor/src/plugins/tilemap/autotile.rs:878-885 | editor/src/plugins/tilemap/wfc.rs:891-898 — before extracting anything, compare `editor/src/plugins/tilemap/autotile.rs` and `editor/src/plugins/tilemap/wfc.rs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 142 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) editor/src/plugins/tilemap/collider_editor.rs:255— editor/src/plugins/tilemap/collider_editor.rs:255-262 | editor/src/plugins/tilemap/tile_prop_editor.rs:398-405 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (8 lines × 2) editor/src/plugins/tilemap/palette.rs:1500— editor/src/plugins/tilemap/palette.rs:1500-1507 | editor/src/plugins/tilemap/palette.rs:1514-1521 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) editor/src/plugins/tilemap/properties_tab.rs:308— editor/src/plugins/tilemap/properties_tab.rs:308-315 | editor/src/plugins/tilemap/properties_tab.rs:458-465 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) editor/src/scene/property.rs:526— editor/src/scene/property.rs:526-533 | editor/src/scene/selector.rs:466-473 — before extracting anything, compare `editor/src/scene/property.rs` and `editor/src/scene/selector.rs` as WHOLE FILES: this scan already matched 5 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 (8 lines × 2) fyrox-animation/src/machine/node/blend.rs:198— fyrox-animation/src/machine/node/blend.rs:198-205 | fyrox-animation/src/machine/node/blend.rs:213-220 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) fyrox-impl/src/renderer/gbuffer.rs:283— fyrox-impl/src/renderer/gbuffer.rs:283-290 | fyrox-impl/src/renderer/gbuffer.rs:296-303 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) fyrox-impl/src/scene/debug.rs:589— fyrox-impl/src/scene/debug.rs:589-596 | fyrox-impl/src/scene/mesh/surface.rs:560-567 — 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 (8 lines × 2) fyrox-impl/src/scene/dim2/rigidbody.rs:173— fyrox-impl/src/scene/dim2/rigidbody.rs:173-180 | fyrox-impl/src/scene/rigidbody.rs:259-266 — before extracting anything, compare `fyrox-impl/src/scene/dim2/rigidbody.rs` and `fyrox-impl/src/scene/rigidbody.rs` as WHOLE FILES: this scan already matched 9 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. 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 (8 lines × 2) fyrox-impl/src/scene/dim2/rigidbody.rs:672— fyrox-impl/src/scene/dim2/rigidbody.rs:672-679 | fyrox-impl/src/scene/rigidbody.rs:850-857 — before extracting anything, compare `fyrox-impl/src/scene/dim2/rigidbody.rs` and `fyrox-impl/src/scene/rigidbody.rs` as WHOLE FILES: this scan already matched 9 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. 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 (8 lines × 2) fyrox-ui/src/draw.rs:364— fyrox-ui/src/draw.rs:364-371 | fyrox-ui/src/draw.rs:441-448 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) fyrox-ui/src/draw.rs:426— fyrox-ui/src/draw.rs:426-433 | fyrox-ui/src/draw.rs:459-466 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) fyrox-ui/src/lib.rs:1353— fyrox-ui/src/lib.rs:1353-1360 | fyrox-ui/src/lib.rs:1386-1393 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) fyrox-impl/src/scene/dim2/physics/mod.rs:538— fyrox-impl/src/scene/dim2/physics/mod.rs:538-545 | fyrox-impl/src/scene/graph/physics/mod.rs:979-986 — before extracting anything, compare `fyrox-impl/src/scene/dim2/physics/mod.rs` and `fyrox-impl/src/scene/graph/physics/mod.rs` as WHOLE FILES: this scan already matched 34 separate duplicated blocks between them, totalling at least 555 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 (8 lines × 2) fyrox-ui/src/text.rs:411— fyrox-ui/src/text.rs:411-418 | fyrox-ui/src/text_box.rs:1106-1113 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (8 lines × 2) editor/src/interaction/rotate_mode.rs:60— editor/src/interaction/rotate_mode.rs:60-67 | editor/src/interaction/scale_mode.rs:57-64 — before extracting anything, compare `editor/src/interaction/rotate_mode.rs` and `editor/src/interaction/scale_mode.rs` as WHOLE FILES: this scan already matched 7 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 (5 lines × 2) editor/src/audio/preview.rs:299— editor/src/audio/preview.rs:299-303 | editor/src/particle.rs:307-312 — 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) editor/src/interaction/gizmo/move_gizmo.rs:214— editor/src/interaction/gizmo/move_gizmo.rs:214-219 | editor/src/interaction/gizmo/move_gizmo.rs:221-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 (5 lines × 2) fyrox-core/src/reflect/mod.rs:932— fyrox-core/src/reflect/mod.rs:932-936 | fyrox-core/src/reflect/mod.rs:962-966 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) fyrox-impl/src/resource/gltf/surface.rs:510— fyrox-impl/src/resource/gltf/surface.rs:510-514 | fyrox-impl/src/resource/gltf/surface.rs:564-571 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) fyrox-impl/src/scene/debug.rs:600— fyrox-impl/src/scene/debug.rs:600-604 | fyrox-impl/src/scene/mesh/surface.rs:571-575 — 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) fyrox-impl/src/scene/debug.rs:1019— fyrox-impl/src/scene/debug.rs:1019-1023 | fyrox-impl/src/scene/debug.rs:1030-1034 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) fyrox-impl/src/scene/dim2/physics/mod.rs:1154— fyrox-impl/src/scene/dim2/physics/mod.rs:1154-1158 | fyrox-impl/src/scene/graph/physics/mod.rs:1652-1656 — before extracting anything, compare `fyrox-impl/src/scene/dim2/physics/mod.rs` and `fyrox-impl/src/scene/graph/physics/mod.rs` as WHOLE FILES: this scan already matched 34 separate duplicated blocks between them, totalling at least 555 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) fyrox-impl/src/scene/node/mod.rs:146— fyrox-impl/src/scene/node/mod.rs:146-150 | fyrox-ui/src/control.rs:167-171 — 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) fyrox-impl/src/scene/tilemap/tileset.rs:610— fyrox-impl/src/scene/tilemap/tileset.rs:610-614 | fyrox-impl/src/scene/tilemap/tileset.rs:1480-1484 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) fyrox-ui/src/inspector/editors/array.rs:130— fyrox-ui/src/inspector/editors/array.rs:130-134 | fyrox-ui/src/inspector/editors/collection.rs:228-232 — before extracting anything, compare `fyrox-ui/src/inspector/editors/array.rs` and `fyrox-ui/src/inspector/editors/collection.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 76 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 (5 lines × 2) fyrox-ui/src/inspector/editors/texture_slice.rs:156— fyrox-ui/src/inspector/editors/texture_slice.rs:156-160 | fyrox-ui/src/inspector/editors/texture_slice.rs:163-167 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) editor/src/plugins/absm/mod.rs:838— editor/src/plugins/absm/mod.rs:838-842 | editor/src/plugins/animation/mod.rs:990-994 — `editor/src/plugins/absm/mod.rs` and `editor/src/plugins/animation/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 6 separate duplicated blocks between them, totalling at least 68 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (5 lines × 2) editor/src/plugins/tilemap/autotile.rs:931— editor/src/plugins/tilemap/autotile.rs:931-935 | editor/src/plugins/tilemap/wfc.rs:944-948 — before extracting anything, compare `editor/src/plugins/tilemap/autotile.rs` and `editor/src/plugins/tilemap/wfc.rs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 142 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) editor/src/plugins/tilemap/autotile.rs:960— editor/src/plugins/tilemap/autotile.rs:960-964 | editor/src/plugins/tilemap/wfc.rs:973-977 — before extracting anything, compare `editor/src/plugins/tilemap/autotile.rs` and `editor/src/plugins/tilemap/wfc.rs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 142 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) editor/src/plugins/tilemap/colliders_tab.rs:266— editor/src/plugins/tilemap/colliders_tab.rs:266-270 | editor/src/plugins/tilemap/properties_tab.rs:503-507 — before extracting anything, compare `editor/src/plugins/tilemap/colliders_tab.rs` and `editor/src/plugins/tilemap/properties_tab.rs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 157 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 (5 lines × 2) fyrox-impl/src/scene/dim2/physics/mod.rs:811— fyrox-impl/src/scene/dim2/physics/mod.rs:811-815 | fyrox-impl/src/scene/graph/physics/mod.rs:1254-1258 — before extracting anything, compare `fyrox-impl/src/scene/dim2/physics/mod.rs` and `fyrox-impl/src/scene/graph/physics/mod.rs` as WHOLE FILES: this scan already matched 34 separate duplicated blocks between them, totalling at least 555 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) fyrox-impl/src/scene/dim2/physics/mod.rs:817— fyrox-impl/src/scene/dim2/physics/mod.rs:817-821 | fyrox-impl/src/scene/graph/physics/mod.rs:1260-1264 — before extracting anything, compare `fyrox-impl/src/scene/dim2/physics/mod.rs` and `fyrox-impl/src/scene/graph/physics/mod.rs` as WHOLE FILES: this scan already matched 34 separate duplicated blocks between them, totalling at least 555 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) fyrox-ui/src/button.rs:127— fyrox-ui/src/button.rs:127-131 | fyrox-ui/src/toggle.rs:60-64 — 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 (5 lines × 2) fyrox-graphics-gl/src/server.rs:1380— fyrox-graphics-gl/src/server.rs:1380-1390 | fyrox-graphics-wgpu/src/server.rs:626-630 — 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) fyrox-graphics-wgpu/src/buffer.rs:106— fyrox-graphics-wgpu/src/buffer.rs:106-110 | fyrox-graphics-wgpu/src/texture.rs:482-486 — 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 (5 lines × 2) editor/src/plugins/absm/mod.rs:823— editor/src/plugins/absm/mod.rs:823-827 | editor/src/plugins/animation/mod.rs:979-983 — `editor/src/plugins/absm/mod.rs` and `editor/src/plugins/animation/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 6 separate duplicated blocks between them, totalling at least 68 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (5 lines × 2) editor/src/plugins/tilemap/palette.rs:584— editor/src/plugins/tilemap/palette.rs:584-588 | editor/src/plugins/tilemap/palette.rs:615-619 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) fyrox-ui/src/style/mod.rs:377— fyrox-ui/src/style/mod.rs:377-381 | fyrox-ui/src/style/mod.rs:442-446 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) editor/src/asset/preview/mod.rs:527— editor/src/asset/preview/mod.rs:527-537 | editor/src/asset/preview/mod.rs:570-580 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) editor/src/interaction/gizmo/move_gizmo.rs:181— editor/src/interaction/gizmo/move_gizmo.rs:181-191 | editor/src/interaction/gizmo/rotate_gizmo.rs:101-111 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (11 lines × 2) editor/src/plugins/collider/cone.rs:96— editor/src/plugins/collider/cone.rs:96-106 | editor/src/plugins/collider/cylinder.rs:97-108 — before extracting anything, compare `editor/src/plugins/collider/cone.rs` and `editor/src/plugins/collider/cylinder.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 31 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 2) editor/src/plugins/inspector/editors/dyntype.rs:115— editor/src/plugins/inspector/editors/dyntype.rs:115-125 | editor/src/plugins/inspector/editors/script.rs:183-193 — before extracting anything, compare `editor/src/plugins/inspector/editors/dyntype.rs` and `editor/src/plugins/inspector/editors/script.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 110 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 2) editor/src/plugins/inspector/editors/dyntype.rs:313— editor/src/plugins/inspector/editors/dyntype.rs:313-323 | editor/src/plugins/inspector/editors/script.rs:411-421 — before extracting anything, compare `editor/src/plugins/inspector/editors/dyntype.rs` and `editor/src/plugins/inspector/editors/script.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 110 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 2) editor/src/plugins/tilemap/macro_tab.rs:245— editor/src/plugins/tilemap/macro_tab.rs:245-255 | editor/src/plugins/tilemap/properties_tab.rs:301-311 — before extracting anything, compare `editor/src/plugins/tilemap/macro_tab.rs` and `editor/src/plugins/tilemap/properties_tab.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 87 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 2) editor/src/plugins/tilemap/tile_editor.rs:259— editor/src/plugins/tilemap/tile_editor.rs:259-269 | editor/src/plugins/tilemap/tile_editor.rs:296-306 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) editor/src/plugins/tilemap/tileset.rs:296— editor/src/plugins/tilemap/tileset.rs:296-306 | editor/src/plugins/tilemap/tileset.rs:310-320 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) fyrox-impl/src/resource/fbx/mod.rs:320— fyrox-impl/src/resource/fbx/mod.rs:320-330 | fyrox-impl/src/resource/gltf/material.rs:418-428 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (11 lines × 2) fyrox-impl/src/resource/gltf/animation.rs:485— fyrox-impl/src/resource/gltf/animation.rs:485-495 | fyrox-impl/src/resource/gltf/animation.rs:544-554 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) fyrox-impl/src/scene/debug.rs:709— fyrox-impl/src/scene/debug.rs:709-719 | fyrox-impl/src/scene/debug.rs:766-776 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) fyrox-impl/src/scene/dim2/physics/character.rs:129— fyrox-impl/src/scene/dim2/physics/character.rs:129-139 | fyrox-impl/src/scene/graph/physics/character.rs:207-217 — before extracting anything, compare `fyrox-impl/src/scene/dim2/physics/character.rs` and `fyrox-impl/src/scene/graph/physics/character.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 39 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 (11 lines × 2) fyrox-impl/src/scene/mesh/surface.rs:823— fyrox-impl/src/scene/mesh/surface.rs:823-833 | fyrox-impl/src/scene/mesh/surface.rs:839-849 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) fyrox-math/src/lib.rs:558— fyrox-math/src/lib.rs:558-568 | fyrox-math/src/lib.rs:598-608 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) fyrox-ui/src/file_browser/selector.rs:367— fyrox-ui/src/file_browser/selector.rs:367-377 | fyrox-ui/src/file_browser/selector.rs:417-427 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) fyrox-ui/src/inspector/editors/mod.rs:890— fyrox-ui/src/inspector/editors/mod.rs:890-900 | fyrox-ui/src/inspector/editors/mod.rs:933-943 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) fyrox-ui/src/list_view.rs:356— fyrox-ui/src/list_view.rs:356-366 | fyrox-ui/src/scroll_panel.rs:287-297 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (11 lines × 2) editor/src/plugins/collider/ball.rs:56— editor/src/plugins/collider/ball.rs:56-66 | editor/src/plugins/collider/ball2d.rs:56-66 — before extracting anything, compare `editor/src/plugins/collider/ball.rs` and `editor/src/plugins/collider/ball2d.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 31 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 2) editor/src/plugins/collider/ball.rs:86— editor/src/plugins/collider/ball.rs:86-96 | editor/src/plugins/collider/ball2d.rs:86-96 — before extracting anything, compare `editor/src/plugins/collider/ball.rs` and `editor/src/plugins/collider/ball2d.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 31 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 2) editor/src/plugins/tilemap/autotile.rs:346— editor/src/plugins/tilemap/autotile.rs:346-356 | editor/src/plugins/tilemap/wfc.rs:381-391 — before extracting anything, compare `editor/src/plugins/tilemap/autotile.rs` and `editor/src/plugins/tilemap/wfc.rs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 142 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 2) fyrox-ui/src/test.rs:99— fyrox-ui/src/test.rs:99-109 | fyrox-ui/src/test.rs:133-143 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) editor/src/interaction/gizmo/move_gizmo.rs:98— editor/src/interaction/gizmo/move_gizmo.rs:98-111 | editor/src/interaction/gizmo/scale_gizmo.rs:81-94 — before extracting anything, compare `editor/src/interaction/gizmo/move_gizmo.rs` and `editor/src/interaction/gizmo/scale_gizmo.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 44 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) editor/src/interaction/rotate_mode.rs:176— editor/src/interaction/rotate_mode.rs:176-189 | editor/src/interaction/scale_mode.rs:168-181 — before extracting anything, compare `editor/src/interaction/rotate_mode.rs` and `editor/src/interaction/scale_mode.rs` as WHOLE FILES: this scan already matched 7 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 (14 lines × 2) editor/src/plugins/absm/state_graph/context.rs:236— editor/src/plugins/absm/state_graph/context.rs:236-249 | editor/src/plugins/absm/state_viewer/context.rs:253-266 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (14 lines × 2) editor/src/scene/mod.rs:596— editor/src/scene/mod.rs:596-609 | editor/src/ui_scene/mod.rs:178-191 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (14 lines × 2) fyrox-impl/src/engine/mod.rs:2411— fyrox-impl/src/engine/mod.rs:2411-2424 | fyrox-impl/src/engine/mod.rs:2439-2452 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) fyrox-impl/src/scene/accel.rs:98— fyrox-impl/src/scene/accel.rs:98-111 | fyrox-math/src/octree.rs:83-96 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (14 lines × 2) fyrox-impl/src/scene/accel.rs:125— fyrox-impl/src/scene/accel.rs:125-138 | fyrox-math/src/octree.rs:110-123 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (14 lines × 2) fyrox-impl/src/scene/collider.rs:1182— fyrox-impl/src/scene/collider.rs:1182-1195 | fyrox-impl/src/scene/dim2/collider.rs:840-853 — before extracting anything, compare `fyrox-impl/src/scene/collider.rs` and `fyrox-impl/src/scene/dim2/collider.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 93 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 (14 lines × 2) fyrox-impl/src/scene/dim2/joint.rs:348— fyrox-impl/src/scene/dim2/joint.rs:348-361 | fyrox-impl/src/scene/joint.rs:407-420 — before extracting anything, compare `fyrox-impl/src/scene/dim2/joint.rs` and `fyrox-impl/src/scene/joint.rs` 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. 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 (14 lines × 2) fyrox-impl/src/scene/dim2/joint.rs:420— fyrox-impl/src/scene/dim2/joint.rs:420-433 | fyrox-impl/src/scene/joint.rs:479-492 — before extracting anything, compare `fyrox-impl/src/scene/dim2/joint.rs` and `fyrox-impl/src/scene/joint.rs` 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. 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 (14 lines × 2) fyrox-impl/src/scene/dim2/physics/character.rs:144— fyrox-impl/src/scene/dim2/physics/character.rs:144-157 | fyrox-impl/src/scene/graph/physics/character.rs:222-235 — before extracting anything, compare `fyrox-impl/src/scene/dim2/physics/character.rs` and `fyrox-impl/src/scene/graph/physics/character.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 39 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 (14 lines × 2) fyrox-impl/src/scene/dim2/physics/mod.rs:709— fyrox-impl/src/scene/dim2/physics/mod.rs:709-722 | fyrox-impl/src/scene/graph/physics/mod.rs:1151-1164 — before extracting anything, compare `fyrox-impl/src/scene/dim2/physics/mod.rs` and `fyrox-impl/src/scene/graph/physics/mod.rs` as WHOLE FILES: this scan already matched 34 separate duplicated blocks between them, totalling at least 555 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 (14 lines × 2) fyrox-impl/src/scene/dim2/physics/mod.rs:927— fyrox-impl/src/scene/dim2/physics/mod.rs:927-940 | fyrox-impl/src/scene/graph/physics/mod.rs:1367-1380 — before extracting anything, compare `fyrox-impl/src/scene/dim2/physics/mod.rs` and `fyrox-impl/src/scene/graph/physics/mod.rs` as WHOLE FILES: this scan already matched 34 separate duplicated blocks between them, totalling at least 555 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 (14 lines × 2) fyrox-ui/src/matrix.rs:52— fyrox-ui/src/matrix.rs:52-65 | fyrox-ui/src/vec.rs:56-69 — before extracting anything, compare `fyrox-ui/src/matrix.rs` and `fyrox-ui/src/vec.rs` 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 (14 lines × 2) fyrox-ui/src/utils.rs:239— fyrox-ui/src/utils.rs:239-252 | fyrox-ui/src/utils.rs:289-302 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) fyrox-impl/src/scene/dim2/physics/mod.rs:969— fyrox-impl/src/scene/dim2/physics/mod.rs:969-982 | fyrox-impl/src/scene/graph/physics/mod.rs:1409-1422 — before extracting anything, compare `fyrox-impl/src/scene/dim2/physics/mod.rs` and `fyrox-impl/src/scene/graph/physics/mod.rs` as WHOLE FILES: this scan already matched 34 separate duplicated blocks between them, totalling at least 555 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 (14 lines × 2) fyrox-impl/src/scene/dim2/physics/character.rs:169— fyrox-impl/src/scene/dim2/physics/character.rs:169-182 | fyrox-impl/src/scene/graph/physics/character.rs:247-260 — before extracting anything, compare `fyrox-impl/src/scene/dim2/physics/character.rs` and `fyrox-impl/src/scene/graph/physics/character.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 39 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 (14 lines × 2) fyrox-ui/src/curve/mod.rs:1970— fyrox-ui/src/curve/mod.rs:1970-1983 | fyrox-ui/src/inspector/mod.rs:1511-1524 — 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.
fyrox_impl::resource::fbx::create_materials (cognitive 110) fyrox-impl/src/resource/fbx/mod.rs:292— fyrox_impl::resource::fbx::create_materials has cognitive complexity 110 (threshold 15). Drivers by points: if/else 21 (78 pts), loops 4 (19 pts), boolean chains 7, match/switch 1 (6 pts) (nesting depth added 77). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
fyrox_impl::resource::fbx::convert_mesh (cognitive 67) fyrox-impl/src/resource/fbx/mod.rs:486— fyrox_impl::resource::fbx::convert_mesh has cognitive complexity 67 (threshold 15). Drivers by points: if/else 9 (42 pts), loops 7 (20 pts), match/switch 1 (5 pts) (nesting depth added 50). 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.
fyrox_impl::renderer::ui_renderer::write_uniform_blocks (cognitive 46) fyrox-impl/src/renderer/ui_renderer.rs:114— fyrox_impl::renderer::ui_renderer::write_uniform_blocks has cognitive complexity 46 (threshold 15). Drivers by points: match/switch 6 (24 pts), loops 4 (13 pts), if/else 4 (9 pts) (nesting depth added 32). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
fyrox_impl::resource::fbx::convert (cognitive 44) fyrox-impl/src/resource/fbx/mod.rs:809— fyrox_impl::resource::fbx::convert has cognitive complexity 44 (threshold 15). Drivers by points: loops 9 (29 pts), if/else 6 (15 pts) (nesting depth added 29). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
fyrox_impl::resource::fbx::document::ascii::read_ascii (cognitive 37) fyrox-impl/src/resource/fbx/document/ascii.rs:31— fyrox_impl::resource::fbx::document::ascii::read_ascii has cognitive complexity 37 (threshold 15). Drivers by points: if/else 13 (26 pts), boolean chains 6, loops 3 (5 pts) (nesting depth added 15). 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.
fyrox_impl::resource::fbx::document::binary::read_binary_node (cognitive 28) fyrox-impl/src/resource/fbx/document/binary.rs:99— fyrox_impl::resource::fbx::document::binary::read_binary_node has cognitive complexity 28 (threshold 15). Drivers by points: if/else 15 (23 pts), loops 2 (3 pts), match/switch 1 (2 pts) (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.
fyrox_impl::renderer::bundle::write_with_material (cognitive 26) fyrox-impl/src/renderer/bundle.rs:238— fyrox_impl::renderer::bundle::write_with_material has cognitive complexity 26 (threshold 15). Drivers by points: if/else 12 (23 pts), match/switch 1 (2 pts), loops 1 (nesting depth added 12). 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.
fyrox_impl::engine::executor::run_normal (cognitive 25) fyrox-impl/src/engine/executor.rs:310— fyrox_impl::engine::executor::run_normal has cognitive complexity 25 (threshold 15). Drivers by points: if/else 7 (12 pts), loops 3 (6 pts), match/switch 3 (6 pts), boolean chains 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.
fyrox_impl::resource::fbx::convert_model (cognitive 24) fyrox-impl/src/resource/fbx/mod.rs:669— fyrox_impl::resource::fbx::convert_model has cognitive complexity 24 (threshold 15). Drivers by points: if/else 21 (39 pts), loops 3 (10 pts), match/switch 1 (3 pts) (nesting depth added 27). 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. This shape REPEATS in the file: one other method here (fyrox_impl::resource::fbx::convert_model::fill_track) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
fyrox_impl::scene::graph::physics::make_heightfield (cognitive 23) fyrox-impl/src/scene/graph/physics/mod.rs:687— fyrox_impl::scene::graph::physics::make_heightfield has cognitive complexity 23 (threshold 15). Drivers by points: loops 6 (15 pts), if/else 4 (8 pts) (nesting depth added 13). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
fyrox_impl::resource::fbx::convert_model::fill_track (cognitive 21) fyrox-impl/src/resource/fbx/mod.rs:706— fyrox_impl::resource::fbx::convert_model::fill_track has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (13 pts), loops 2 (6 pts), match/switch 1 (2 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. This shape REPEATS in the file: one other method here (fyrox_impl::resource::fbx::convert_model) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
fyrox_impl::resource::gltf::material::search_for_path (cognitive 20) fyrox-impl/src/resource/gltf/material.rs:411— fyrox_impl::resource::gltf::material::search_for_path has cognitive complexity 20 (threshold 15). Drivers by points: if/else 4 (14 pts), loops 2 (5 pts), match/switch 1 (nesting depth added 13). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
fyrox_impl::resource::fbx::scene::link_child_with_parent_component (cognitive 18) fyrox-impl/src/resource/fbx/scene/mod.rs:185— fyrox_impl::resource::fbx::scene::link_child_with_parent_component has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (15 pts), match/switch 2 (3 pts) (nesting depth added 8). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
fyrox_impl::scene::graph::physics::make_trimesh (cognitive 16) fyrox-impl/src/scene/graph/physics/mod.rs:510— fyrox_impl::scene::graph::physics::make_trimesh has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (8 pts), loops 3 (8 pts) (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.
Duplicated block (15 lines × 2) editor/src/asset/creator.rs:142— editor/src/asset/creator.rs:142-156 | editor/src/scene/dialog.rs:131-145 — 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 (15 lines × 2) editor/src/interaction/gizmo/move_gizmo.rs:133— editor/src/interaction/gizmo/move_gizmo.rs:133-147 | editor/src/interaction/gizmo/scale_gizmo.rs:118-132 — before extracting anything, compare `editor/src/interaction/gizmo/move_gizmo.rs` and `editor/src/interaction/gizmo/scale_gizmo.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 44 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (15 lines × 2) editor/src/plugins/absm/mod.rs:942— editor/src/plugins/absm/mod.rs:942-956 | editor/src/plugins/animation/mod.rs:1096-1110 — `editor/src/plugins/absm/mod.rs` and `editor/src/plugins/animation/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 6 separate duplicated blocks between them, totalling at least 68 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (15 lines × 2) editor/src/ui_scene/interaction/mod.rs:115— editor/src/ui_scene/interaction/mod.rs:115-129 | editor/src/ui_scene/interaction/move_mode.rs:144-158 — 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 (15 lines × 2) fyrox-animation/src/machine/layer.rs:348— fyrox-animation/src/machine/layer.rs:348-362 | fyrox-animation/src/machine/layer.rs:364-378 — both copies are in the same file, so extract the 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) fyrox-build-tools/src/export/utils.rs:88— fyrox-build-tools/src/export/utils.rs:88-102 | project-manager/src/utils.rs:104-118 — 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 (15 lines × 2) fyrox-impl/src/scene/collider.rs:694— fyrox-impl/src/scene/collider.rs:694-708 | fyrox-impl/src/scene/dim2/collider.rs:350-364 — before extracting anything, compare `fyrox-impl/src/scene/collider.rs` and `fyrox-impl/src/scene/dim2/collider.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 93 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (15 lines × 2) fyrox-impl/src/scene/dim2/physics/mod.rs:756— fyrox-impl/src/scene/dim2/physics/mod.rs:756-770 | fyrox-impl/src/scene/graph/physics/mod.rs:1199-1213 — before extracting anything, compare `fyrox-impl/src/scene/dim2/physics/mod.rs` and `fyrox-impl/src/scene/graph/physics/mod.rs` as WHOLE FILES: this scan already matched 34 separate duplicated blocks between them, totalling at least 555 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (15 lines × 2) fyrox-math/src/lib.rs:140— fyrox-math/src/lib.rs:140-154 | fyrox-math/src/lib.rs:336-350 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15 lines × 2) fyrox-ui/src/canvas.rs:104— fyrox-ui/src/canvas.rs:104-118 | fyrox-ui/src/inspector/editors/texture_slice.rs:232-246 — 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 (15 lines × 2) fyrox-ui/src/inspector/editors/array.rs:255— fyrox-ui/src/inspector/editors/array.rs:255-269 | fyrox-ui/src/inspector/editors/collection.rs:399-413 — before extracting anything, compare `fyrox-ui/src/inspector/editors/array.rs` and `fyrox-ui/src/inspector/editors/collection.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 76 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (15 lines × 2) fyrox-ui/src/inspector/editors/cell.rs:84— fyrox-ui/src/inspector/editors/cell.rs:84-98 | fyrox-ui/src/inspector/editors/cell.rs:129-143 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15 lines × 2) fyrox-ui/src/nine_patch.rs:393— fyrox-ui/src/nine_patch.rs:393-407 | fyrox-ui/src/nine_patch.rs:495-509 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (17 lines × 2) editor/src/asset/dependency.rs:133— editor/src/asset/dependency.rs:133-149 | editor/src/plugins/ragdoll.rs:1113-1129 — 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 (17 lines × 2) editor/src/interaction/rotate_mode.rs:237— editor/src/interaction/rotate_mode.rs:237-253 | editor/src/interaction/scale_mode.rs:216-232 — before extracting anything, compare `editor/src/interaction/rotate_mode.rs` and `editor/src/interaction/scale_mode.rs` as WHOLE FILES: this scan already matched 7 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 (17 lines × 2) editor/src/plugins/absm/state_graph/context.rs:386— editor/src/plugins/absm/state_graph/context.rs:386-402 | editor/src/plugins/absm/state_viewer/context.rs:345-361 — 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 (17 lines × 2) editor/src/plugins/absm/state_graph/mod.rs:96— editor/src/plugins/absm/state_graph/mod.rs:96-112 | editor/src/plugins/absm/state_viewer/mod.rs:184-200 — `editor/src/plugins/absm/state_graph/mod.rs` and `editor/src/plugins/absm/state_viewer/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 46 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (17 lines × 2) editor/src/world/mod.rs:523— editor/src/world/mod.rs:523-539 | editor/src/world/mod.rs:582-598 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (17 lines × 2) fyrox-core/src/pool/mod.rs:640— fyrox-core/src/pool/mod.rs:640-656 | fyrox-core/src/pool/mod.rs:695-711 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (17 lines × 2) fyrox-impl/src/scene/dim2/physics/mod.rs:422— fyrox-impl/src/scene/dim2/physics/mod.rs:422-438 | fyrox-impl/src/scene/graph/physics/mod.rs:781-797 — before extracting anything, compare `fyrox-impl/src/scene/dim2/physics/mod.rs` and `fyrox-impl/src/scene/graph/physics/mod.rs` as WHOLE FILES: this scan already matched 34 separate duplicated blocks between them, totalling at least 555 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 (17 lines × 2) fyrox-impl/src/scene/dim2/physics/mod.rs:1137— fyrox-impl/src/scene/dim2/physics/mod.rs:1137-1153 | fyrox-impl/src/scene/graph/physics/mod.rs:1635-1651 — before extracting anything, compare `fyrox-impl/src/scene/dim2/physics/mod.rs` and `fyrox-impl/src/scene/graph/physics/mod.rs` as WHOLE FILES: this scan already matched 34 separate duplicated blocks between them, totalling at least 555 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 (17 lines × 2) fyrox-impl/src/scene/tilemap/effect.rs:237— fyrox-impl/src/scene/tilemap/effect.rs:237-253 | fyrox-impl/src/scene/tilemap/effect.rs:270-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.
Duplicated block (17 lines × 2) fyrox-ui/src/color/mod.rs:270— fyrox-ui/src/color/mod.rs:270-286 | fyrox-ui/src/color/mod.rs:431-447 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (17 lines × 2) fyrox-ui/src/key.rs:265— fyrox-ui/src/key.rs:265-281 | fyrox-ui/src/key.rs:464-480 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) editor/src/export/mod.rs:272— editor/src/export/mod.rs:272-283 | editor/src/plugins/inspector/editors/spritesheet/window.rs:334-345 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (12 lines × 2) editor/src/plugins/animation/toolbar.rs:540— editor/src/plugins/animation/toolbar.rs:540-551 | editor/src/plugins/animation/toolbar.rs:660-671 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) editor/src/plugins/collider/cuboid.rs:156— editor/src/plugins/collider/cuboid.rs:156-167 | editor/src/plugins/collider/cuboid2d.rs:140-151 — 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 (12 lines × 2) editor/src/plugins/tilemap/commands.rs:1143— editor/src/plugins/tilemap/commands.rs:1143-1154 | editor/src/plugins/tilemap/commands.rs:1193-1204 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) fyrox-impl/src/resource/gltf/surface.rs:498— fyrox-impl/src/resource/gltf/surface.rs:498-509 | fyrox-impl/src/resource/gltf/surface.rs:550-561 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) fyrox-impl/src/scene/dim2/physics/mod.rs:281— fyrox-impl/src/scene/dim2/physics/mod.rs:281-292 | fyrox-impl/src/scene/graph/physics/mod.rs:404-415 — before extracting anything, compare `fyrox-impl/src/scene/dim2/physics/mod.rs` and `fyrox-impl/src/scene/graph/physics/mod.rs` as WHOLE FILES: this scan already matched 34 separate duplicated blocks between them, totalling at least 555 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 (12 lines × 2) fyrox-ui/src/file_browser/fs_tree.rs:85— fyrox-ui/src/file_browser/fs_tree.rs:85-96 | fyrox-ui/src/file_browser/fs_tree.rs:98-109 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) fyrox-ui/src/text_box.rs:1236— fyrox-ui/src/text_box.rs:1236-1247 | fyrox-ui/src/text_box.rs:1260-1271 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) editor/src/plugins/tilemap/tile_inspector.rs:445— editor/src/plugins/tilemap/tile_inspector.rs:445-456 | editor/src/plugins/tilemap/tileset.rs:153-164 — 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 (12 lines × 2) fyrox-impl/src/scene/dim2/rigidbody.rs:504— fyrox-impl/src/scene/dim2/rigidbody.rs:504-515 | fyrox-impl/src/scene/rigidbody.rs:645-656 — before extracting anything, compare `fyrox-impl/src/scene/dim2/rigidbody.rs` and `fyrox-impl/src/scene/rigidbody.rs` as WHOLE FILES: this scan already matched 9 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. 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 (12 lines × 2) fyrox-build-tools/src/lib.rs:183— fyrox-build-tools/src/lib.rs:183-194 | fyrox-build-tools/src/lib.rs:204-215 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
fyrox_impl::resource::fbx::create_materials (cyclomatic 32) fyrox-impl/src/resource/fbx/mod.rs:292— fyrox_impl::resource::fbx::create_materials has cyclomatic complexity 32 (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.
fyrox_impl::renderer::bundle::write_with_material (cyclomatic 27) fyrox-impl/src/renderer/bundle.rs:238— fyrox_impl::renderer::bundle::write_with_material 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.
fyrox_impl::resource::fbx::convert_model (cyclomatic 23) fyrox-impl/src/resource/fbx/mod.rs:669— fyrox_impl::resource::fbx::convert_model has cyclomatic complexity 23 (threshold 15). Of this number, 12 points are the body's own statements and 11 belong to one function item inside it that branches. 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.
fyrox_impl::resource::fbx::document::ascii::read_ascii (cyclomatic 22) fyrox-impl/src/resource/fbx/document/ascii.rs:31— fyrox_impl::resource::fbx::document::ascii::read_ascii 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.
fyrox_impl::resource::fbx::scene::link_child_with_parent_component (cyclomatic 22) fyrox-impl/src/resource/fbx/scene/mod.rs:185— fyrox_impl::resource::fbx::scene::link_child_with_parent_component 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.
fyrox_impl::resource::fbx::convert_mesh (cyclomatic 18) fyrox-impl/src/resource/fbx/mod.rs:486— fyrox_impl::resource::fbx::convert_mesh has cyclomatic complexity 18 (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.
fyrox_impl::engine::executor::run_normal (cyclomatic 18) fyrox-impl/src/engine/executor.rs:310— fyrox_impl::engine::executor::run_normal has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
fyrox_impl::resource::fbx::document::binary::read_binary_node (cyclomatic 17) fyrox-impl/src/resource/fbx/document/binary.rs:99— fyrox_impl::resource::fbx::document::binary::read_binary_node 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.
fyrox_impl::renderer::ui_renderer::write_uniform_blocks (cyclomatic 16) fyrox-impl/src/renderer/ui_renderer.rs:114— fyrox_impl::renderer::ui_renderer::write_uniform_blocks has cyclomatic complexity 16 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
fyrox_impl::resource::fbx::convert (cyclomatic 16) fyrox-impl/src/resource/fbx/mod.rs:809— fyrox_impl::resource::fbx::convert has cyclomatic complexity 16 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
UserInterface::process_os_event (cognitive 196) fyrox-ui/src/lib.rs:2776— UserInterface::process_os_event has cognitive complexity 196 (threshold 15). Drivers by points: if/else 46 (148 pts), loops 7 (26 pts), match/switch 7 (19 pts), boolean chains 3 (nesting depth added 133). 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.
UserInterface::poll_single_message (cognitive 83) fyrox-ui/src/lib.rs:2354— UserInterface::poll_single_message has cognitive complexity 83 (threshold 15). Drivers by points: if/else 25 (59 pts), match/switch 5 (12 pts), loops 3 (7 pts), boolean chains 5 (nesting depth added 45). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
UserInterface::update_tooltips (cognitive 34) fyrox-ui/src/lib.rs:2672— UserInterface::update_tooltips has cognitive complexity 34 (threshold 15). Drivers by points: if/else 12 (30 pts), loops 2 (4 pts) (nesting depth added 20). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
UserInterface::handle_layout_events (cognitive 23) fyrox-ui/src/lib.rs:1425— UserInterface::handle_layout_events has cognitive complexity 23 (threshold 15). Drivers by points: if/else 5 (14 pts), loops 3 (6 pts), match/switch 1 (2 pts), boolean chains 1 (nesting depth added 13). Of this number, 16 points are the body's own statements and 7 belong to one function item inside it that branches. 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.
UserInterface::measure_node (cognitive 21) fyrox-ui/src/lib.rs:1835— UserInterface::measure_node has cognitive complexity 21 (threshold 15). Drivers by points: if/else 13 (20 pts), boolean chains 1 (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.
UserInterface::update (cognitive 19) fyrox-ui/src/lib.rs:1549— UserInterface::update has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (13 pts), loops 4 (6 pts) (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.
UserInterface::is_node_clipped (cognitive 18) fyrox-ui/src/lib.rs:1911— UserInterface::is_node_clipped has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (14 pts), loops 1 (3 pts), boolean chains 1 (nesting depth added 11). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
UserInterface::draw (cognitive 16) fyrox-ui/src/lib.rs:1627— UserInterface::draw has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 2, loops 2 (nesting depth added 3). Of this number, 12 points are the body's own statements and 4 belong to one function item inside it that branches. 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.
UserInterface::arrange_node (cognitive 16) fyrox-ui/src/lib.rs:1750— UserInterface::arrange_node has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (11 pts), match/switch 2 (4 pts), boolean chains 1 (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.
PaletteWidget::draw (cognitive 72) editor/src/plugins/tilemap/palette.rs:1696— PaletteWidget::draw has cognitive complexity 72 (threshold 15). Drivers by points: if/else 29 (50 pts), loops 7 (17 pts), boolean chains 5 (nesting depth added 31). 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.
PaletteWidget::draw_tile_colliders (cognitive 39) editor/src/plugins/tilemap/palette.rs:1408— PaletteWidget::draw_tile_colliders has cognitive complexity 39 (threshold 15). Drivers by points: if/else 14 (30 pts), loops 5 (7 pts), boolean chains 2 (nesting depth added 18). 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.
PaletteWidget::handle_routed_message (cognitive 33) editor/src/plugins/tilemap/palette.rs:1889— PaletteWidget::handle_routed_message has cognitive complexity 33 (threshold 15). Drivers by points: if/else 17 (28 pts), match/switch 1 (3 pts), boolean chains 2 (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.
PaletteWidget::sync_to_state (cognitive 27) editor/src/plugins/tilemap/palette.rs:675— PaletteWidget::sync_to_state has cognitive complexity 27 (threshold 15). Drivers by points: if/else 12 (22 pts), match/switch 2 (3 pts), boolean chains 2 (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.
PaletteWidget::send_update_tiles (cognitive 20) editor/src/plugins/tilemap/palette.rs:832— PaletteWidget::send_update_tiles has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (16 pts), loops 1 (3 pts), match/switch 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.
PaletteWidget::draw (cognitive 19) editor/src/plugins/tilemap/palette.rs:1284— PaletteWidget::draw has cognitive complexity 19 (threshold 15). Drivers by points: if/else 11 (18 pts), match/switch 1 (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.
PaletteWidget::end_tile_drag (cognitive 17) editor/src/plugins/tilemap/palette.rs:1225— PaletteWidget::end_tile_drag has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (13 pts), loops 1 (3 pts), 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.
PaletteWidget::end_page_drag (cognitive 16) editor/src/plugins/tilemap/palette.rs:1182— PaletteWidget::end_page_drag has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (12 pts), loops 1 (3 pts), 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.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×8
Members sharing a duplicated core (4 members, 50+ identical tokens) editor/src/asset/creator.rs:65— editor/src/asset/creator.rs:65-163 | editor/src/light.rs:115-181 | editor/src/plugins/inspector/mod.rs:219-317 | editor/src/scene/dialog.rs:60-148 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) editor/src/plugins/collider/mod.rs:406— editor/src/plugins/collider/mod.rs:406-484 | editor/src/plugins/collider/mod.rs:541-634 | editor/src/plugins/probe.rs:179-203 | editor/src/plugins/probe.rs:240-274 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) editor/src/plugins/tilemap/autotile.rs:466— editor/src/plugins/tilemap/autotile.rs:466-536 | editor/src/plugins/tilemap/autotile.rs:615-638 | editor/src/plugins/tilemap/wfc.rs:501-623 | editor/src/plugins/tilemap/wfc.rs:633-678 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) editor/src/plugins/tilemap/properties_tab.rs:668— editor/src/plugins/tilemap/properties_tab.rs:668-684 | editor/src/plugins/tilemap/properties_tab.rs:691-717 | editor/src/plugins/tilemap/properties_tab.rs:724-750 | editor/src/plugins/tilemap/properties_tab.rs:757-783 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) fyrox-graphics-gl/src/texture.rs:346— fyrox-graphics-gl/src/texture.rs:346-394 | fyrox-graphics-gl/src/texture.rs:403-633 | fyrox-graphics-wgpu/src/texture.rs:297-416 | fyrox-graphics-wgpu/src/texture.rs:440-479 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) fyrox-impl/src/resource/gltf/animation.rs:484— fyrox-impl/src/resource/gltf/animation.rs:484-506 | fyrox-impl/src/resource/gltf/animation.rs:543-572 | fyrox-impl/src/resource/gltf/animation.rs:619-641 | fyrox-impl/src/resource/gltf/animation.rs:650-680 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) fyrox-impl/src/scene/debug.rs:123— fyrox-impl/src/scene/debug.rs:123-199 | fyrox-impl/src/scene/debug.rs:202-278 | fyrox-impl/src/scene/debug.rs:286-378 | fyrox-impl/src/scene/debug.rs:542-575 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) fyrox-impl/src/scene/debug.rs:700— fyrox-impl/src/scene/debug.rs:700-746 | fyrox-impl/src/scene/debug.rs:757-830 | fyrox-impl/src/scene/mesh/surface.rs:616-689 | fyrox-impl/src/scene/mesh/surface.rs:757-860 — 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.
Editor::handle_hotkeys (cognitive 106) editor/src/lib.rs:1211— Editor::handle_hotkeys has cognitive complexity 106 (threshold 15). Drivers by points: if/else 44 (105 pts), boolean chains 1 (nesting depth added 61). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
Editor::handle_modes (cognitive 70) editor/src/lib.rs:2399— Editor::handle_modes has cognitive complexity 70 (threshold 15). Drivers by points: if/else 17 (59 pts), match/switch 4 (10 pts), boolean chains 1 (nesting depth added 48). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
Editor::update (cognitive 47) editor/src/lib.rs:2508— Editor::update has cognitive complexity 47 (threshold 15). Drivers by points: if/else 19 (32 pts), loops 3 (7 pts), match/switch 2 (7 pts), boolean chains 1 (nesting depth added 22). 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.
Editor::handle_ui_message (cognitive 31) editor/src/lib.rs:1391— Editor::handle_ui_message has cognitive complexity 31 (threshold 15). Drivers by points: if/else 15 (29 pts), match/switch 1 (2 pts) (nesting depth added 15). 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.
Editor::run (cognitive 27) editor/src/lib.rs:3029— Editor::run has cognitive complexity 27 (threshold 15). Drivers by points: if/else 9 (22 pts), match/switch 2 (3 pts), boolean chains 2 (nesting depth added 14). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
Editor::set_play_mode (cognitive 16) editor/src/lib.rs:1645— Editor::set_play_mode has cognitive complexity 16 (threshold 15). Drivers by points: loops 4 (10 pts), if/else 5, match/switch 1 (nesting depth added 6). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
Editor::load_scene (cognitive 16) editor/src/lib.rs:2084— Editor::load_scene has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (8 pts), match/switch 3 (7 pts), loops 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.
fyroxed_base::update (cognitive 57) editor/src/lib.rs:3183— fyroxed_base::update has cognitive complexity 57 (threshold 15). Drivers by points: if/else 12 (35 pts), loops 6 (20 pts), match/switch 1 (2 pts) (nesting depth added 38). 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.
fyroxed_base::plugins::animation::track::type_id_to_supported_type (cognitive 47) editor/src/plugins/animation/track.rs:195— fyroxed_base::plugins::animation::track::type_id_to_supported_type has cognitive complexity 47 (threshold 15). Drivers by points: if/else 47. 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.
fyroxed_base::scene::property::object_to_property_tree (cognitive 32) editor/src/scene/property.rs:163— fyroxed_base::scene::property::object_to_property_tree has cognitive complexity 32 (threshold 15). Drivers by points: if/else 7 (18 pts), loops 3 (8 pts), match/switch 2 (5 pts), boolean chains 1 (nesting depth added 19). 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.
fyroxed_base::camera::precise_ray_test (cognitive 24) editor/src/camera/mod.rs:944— fyroxed_base::camera::precise_ray_test has cognitive complexity 24 (threshold 15). Drivers by points: if/else 4 (18 pts), loops 3 (6 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.
fyroxed_base::plugins::tilemap::palette::send_copy_brush_pages (cognitive 17) editor/src/plugins/tilemap/palette.rs:471— fyroxed_base::plugins::tilemap::palette::send_copy_brush_pages has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (16 pts), loops 1 (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.
fyroxed_base::asset::is_path_in_registry (cognitive 16) editor/src/asset/mod.rs:145— fyroxed_base::asset::is_path_in_registry has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (16 pts) (nesting depth added 10). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
fyroxed_base::plugins::tilemap::interaction_mode::draw (cognitive 16) editor/src/plugins/tilemap/interaction_mode.rs:432— fyroxed_base::plugins::tilemap::interaction_mode::draw has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (15 pts), match/switch 1 (nesting depth added 5). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
FunctionTooLong: fyroxed_base::plugins::inspector::editors::make_property_editors_container editor/src/plugins/inspector/editors/mod.rs:317— FunctionTooLong — fyroxed_base::plugins::inspector::editors::make_property_editors_container runs 385 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 285 over it, 3.85× 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.
FunctionTooLong: fyrox_project_manager::main project-manager/src/main.rs:73— FunctionTooLong — fyrox_project_manager::main runs 139 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 39 over it, 1.39× 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.
FunctionTooLong: fyrox_ui::node::constructor::new_widget_constructor_container fyrox-ui/src/node/constructor.rs:81— FunctionTooLong — fyrox_ui::node::constructor::new_widget_constructor_container runs 127 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) 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.
FunctionTooLong: fyrox_impl::resource::fbx::convert_mesh fyrox-impl/src/resource/fbx/mod.rs:486— FunctionTooLong — fyrox_impl::resource::fbx::convert_mesh runs 112 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) 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.
FunctionTooLong: fyrox_core_derive::visit::impl_visit_enum fyrox-core-derive/src/visit.rs:90— FunctionTooLong — fyrox_core_derive::visit::impl_visit_enum runs 103 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 3 over it, 1.03× 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.
FunctionTooLong: fyrox_project_manager::manager::make_project_item project-manager/src/manager.rs:173— FunctionTooLong — fyrox_project_manager::manager::make_project_item runs 103 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 3 over it, 1.03× 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.
FunctionTooLong: fyrox_impl::resource::fbx::create_materials fyrox-impl/src/resource/fbx/mod.rs:292— FunctionTooLong — fyrox_impl::resource::fbx::create_materials runs 101 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) 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.
Change coupling: selection.rs ↔ selection.rs editor/src/ui_scene/selection.rs— `editor/src/ui_scene/selection.rs` and `editor/src/world/selection.rs` change together 69% of the time (9 of the 13 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 9 shared commits counted here, the most recent 3 are `7eaf5def` fixed doc provider; `62501164` use inner value of node/widget wrapper in the inspector; `bee807ea` fixed downcasting for widgets and scene nodes — run `git show` on any of them.
Change coupling: enumeration.rs ↔ inspectable.rs fyrox-ui/src/inspector/editors/enumeration.rs— `fyrox-ui/src/inspector/editors/enumeration.rs` and `fyrox-ui/src/inspector/editors/inspectable.rs` change together 61% of the time (14 of the 23 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 between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 14 shared commits counted here, the most recent 3 are `135dc00c` include type name of fields in inspector tooltips; `b88e4a09` fixed layout of inheritable property editor + styling; `be14535d` typed handles for `Inspector` widget — run `git show` on any of them.
Change coupling: mod.rs ↔ mod.rs editor/src/plugins/absm/state_graph/mod.rs— `editor/src/plugins/absm/state_graph/mod.rs` and `editor/src/plugins/absm/state_viewer/mod.rs` change together 58% of the time (19 of the 33 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 19 shared commits counted here, the most recent 3 are `8d815db3` keep previous absm selected in the editor; `da549573` more typed handles for widgets; `13818290` allow comparison of base and derived handles — run `git show` on any of them.
Change coupling: selection.rs ↔ selection.rs editor/src/interaction/navmesh/selection.rs— `editor/src/interaction/navmesh/selection.rs` and `editor/src/world/selection.rs` change together 54% of the time (7 of the 13 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 7 shared commits counted here, the most recent 3 are `7eaf5def` fixed doc provider; `bee807ea` fixed downcasting for widgets and scene nodes; `0ba40900` show the content of built-in assets in inspector when selected — run `git show` on any of them.
Change coupling: camera.rs ↔ decal.rs fyrox-impl/src/scene/camera.rs— `fyrox-impl/src/scene/camera.rs` and `fyrox-impl/src/scene/decal.rs` change together 53% of the time (8 of the 15 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 between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `11522405` simplified usage of `ResourceManager::request` + fixed tests (at that commit the files were still `src/scene/camera.rs` and `src/scene/decal.rs`); `ddae1609` tests fix (at that commit the files were still `src/scene/camera.rs` and `src/scene/decal.rs`); `605e10c7` drop backward compatibility code (at that commit the files were still `src/scene/camera.rs` and `src/scene/decal.rs`) — run `git show` on any of them.
Change coupling: collection.rs ↔ inspectable.rs fyrox-ui/src/inspector/editors/collection.rs— `fyrox-ui/src/inspector/editors/collection.rs` and `fyrox-ui/src/inspector/editors/inspectable.rs` change together 52% of the time (12 of the 23 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 between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 12 shared commits counted here, the most recent 3 are `135dc00c` include type name of fields in inspector tooltips; `b88e4a09` fixed layout of inheritable property editor + styling; `092d30b4` removed redundant trait bounds — run `git show` on any of them.
Change coupling: gradient.rs ↔ mod.rs fyrox-ui/src/color/gradient.rs— `fyrox-ui/src/color/gradient.rs` and `fyrox-ui/src/curve/mod.rs` change together 50% of the time (5 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 5 shared commits counted here, the most recent 3 are `113945a0` finished transition to typed handles for ui; `78c43162` add layout invalidation for all widgets with custom draw methods; `8d88f8b0` disable picking restriction for menus and context menus — run `git show` on any of them.
Duplicated block (16 lines × 2) editor/src/interaction/rotate_mode.rs:151— editor/src/interaction/rotate_mode.rs:151-166 | editor/src/interaction/scale_mode.rs:143-158 — before extracting anything, compare `editor/src/interaction/rotate_mode.rs` and `editor/src/interaction/scale_mode.rs` as WHOLE FILES: this scan already matched 7 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 (16 lines × 2) editor/src/interaction/select_mode.rs:159— editor/src/interaction/select_mode.rs:159-174 | editor/src/ui_scene/interaction/mod.rs:174-189 — 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 (16 lines × 2) editor/src/plugins/inspector/editors/dyntype.rs:160— editor/src/plugins/inspector/editors/dyntype.rs:160-175 | editor/src/plugins/inspector/editors/script.rs:232-247 — before extracting anything, compare `editor/src/plugins/inspector/editors/dyntype.rs` and `editor/src/plugins/inspector/editors/script.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 110 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (16 lines × 2) editor/src/plugins/tilemap/palette.rs:2123— editor/src/plugins/tilemap/palette.rs:2123-2138 | fyrox-ui/src/color/mod.rs:235-250 — 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 (16 lines × 2) fyrox-impl/src/scene/dim2/physics/mod.rs:727— fyrox-impl/src/scene/dim2/physics/mod.rs:727-742 | fyrox-impl/src/scene/graph/physics/mod.rs:1169-1184 — before extracting anything, compare `fyrox-impl/src/scene/dim2/physics/mod.rs` and `fyrox-impl/src/scene/graph/physics/mod.rs` as WHOLE FILES: this scan already matched 34 separate duplicated blocks between them, totalling at least 555 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 (16 lines × 2) fyrox-ui/src/inspector/editors/collection.rs:527— fyrox-ui/src/inspector/editors/collection.rs:527-542 | fyrox-ui/src/inspector/editors/enumeration.rs:407-422 — 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 (16 lines × 2) fyrox-ui/src/inspector/editors/hashmap/mod.rs:482— fyrox-ui/src/inspector/editors/hashmap/mod.rs:482-497 | fyrox-ui/src/inspector/editors/hashmap/mod.rs:505-520 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
PhysicsWorld::sync_to_rigid_body_node (cognitive 38) fyrox-impl/src/scene/graph/physics/mod.rs:1489— PhysicsWorld::sync_to_rigid_body_node has cognitive complexity 38 (threshold 15). Drivers by points: if/else 9 (19 pts), match/switch 4 (14 pts), loops 1 (4 pts), boolean chains 1 (nesting depth added 23). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
PhysicsWorld::sync_to_rigid_body_node (cognitive 29) fyrox-impl/src/scene/dim2/physics/mod.rs:1049— PhysicsWorld::sync_to_rigid_body_node has cognitive complexity 29 (threshold 15). Drivers by points: if/else 9 (19 pts), match/switch 1 (5 pts), loops 1 (4 pts), boolean chains 1 (nesting depth added 17). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
PhysicsWorld::sync_to_collider_node (cognitive 26) fyrox-impl/src/scene/dim2/physics/mod.rs:1192— PhysicsWorld::sync_to_collider_node has cognitive complexity 26 (threshold 15). Drivers by points: if/else 11 (26 pts) (nesting depth added 15). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
PhysicsWorld::sync_to_collider_node (cognitive 26) fyrox-impl/src/scene/graph/physics/mod.rs:1703— PhysicsWorld::sync_to_collider_node has cognitive complexity 26 (threshold 15). Drivers by points: if/else 11 (26 pts) (nesting depth added 15). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
PhysicsWorld::sync_to_joint_node (cognitive 26) fyrox-impl/src/scene/graph/physics/mod.rs:1838— PhysicsWorld::sync_to_joint_node has cognitive complexity 26 (threshold 15). Drivers by points: if/else 11 (21 pts), loops 1 (2 pts), match/switch 1 (2 pts), boolean chains 1 (nesting depth added 12). 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.
PhysicsWorld::sync_to_joint_node (cognitive 24) fyrox-impl/src/scene/dim2/physics/mod.rs:1325— PhysicsWorld::sync_to_joint_node has cognitive complexity 24 (threshold 15). Drivers by points: if/else 11 (21 pts), match/switch 1 (2 pts), boolean chains 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.
Duplicated block (12–13 lines × 2) editor/src/mesh.rs:187— editor/src/mesh.rs:187-198 | editor/src/mesh.rs:231-243 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12–13 lines × 2) editor/src/plugins/inspector/editors/dyntype.rs:256— editor/src/plugins/inspector/editors/dyntype.rs:256-267 | editor/src/plugins/inspector/editors/script.rs:352-364 — before extracting anything, compare `editor/src/plugins/inspector/editors/dyntype.rs` and `editor/src/plugins/inspector/editors/script.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 110 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (12–13 lines × 2) fyrox-impl/src/scene/dim2/physics/mod.rs:1252— fyrox-impl/src/scene/dim2/physics/mod.rs:1252-1263 | fyrox-impl/src/scene/graph/physics/mod.rs:1765-1777 — before extracting anything, compare `fyrox-impl/src/scene/dim2/physics/mod.rs` and `fyrox-impl/src/scene/graph/physics/mod.rs` as WHOLE FILES: this scan already matched 34 separate duplicated blocks between them, totalling at least 555 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 (12–13 lines × 2) fyrox-impl/src/scene/dim2/physics/mod.rs:1331— fyrox-impl/src/scene/dim2/physics/mod.rs:1331-1343 | fyrox-impl/src/scene/graph/physics/mod.rs:1844-1855 — before extracting anything, compare `fyrox-impl/src/scene/dim2/physics/mod.rs` and `fyrox-impl/src/scene/graph/physics/mod.rs` as WHOLE FILES: this scan already matched 34 separate duplicated blocks between them, totalling at least 555 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 (12–13 lines × 2) fyrox-impl/src/scene/terrain/mod.rs:1562— fyrox-impl/src/scene/terrain/mod.rs:1562-1573 | fyrox-impl/src/scene/terrain/mod.rs:2736-2748 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12–13 lines × 2) fyrox-ui/src/inspector/editors/inspectable.rs:164— fyrox-ui/src/inspector/editors/inspectable.rs:164-176 | fyrox-ui/src/inspector/editors/refcell.rs:158-169 — before extracting anything, compare `fyrox-ui/src/inspector/editors/inspectable.rs` and `fyrox-ui/src/inspector/editors/refcell.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 52 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.
Editor::update (cyclomatic 60) editor/src/lib.rs:2508— Editor::update has cyclomatic complexity 60 (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.
Editor::handle_hotkeys (cyclomatic 44) editor/src/lib.rs:1211— Editor::handle_hotkeys has cyclomatic complexity 44 (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.
Editor::run (cyclomatic 23) editor/src/lib.rs:3029— Editor::run 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.
Editor::handle_modes (cyclomatic 20) editor/src/lib.rs:2399— Editor::handle_modes 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.
Editor::handle_ui_message (cyclomatic 17) editor/src/lib.rs:1391— Editor::handle_ui_message 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.
Hotspot: editor/src/scene_viewer/mod.rs editor/src/scene_viewer/mod.rs:692— editor/src/scene_viewer/mod.rs changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 55 in SceneViewer::handle_ui_message at line 692. 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-06-29..2026-09-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-29 10:33:17 +03:00' --until='2026-09-27 10:33:17 +03:00' --full-history --no-merges -- editor/src/scene_viewer/mod.rs`: 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: editor/src/plugins/absm/canvas.rs editor/src/plugins/absm/canvas.rs:416— editor/src/plugins/absm/canvas.rs changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 45 in AbsmCanvas::handle_routed_message at line 416. 4 of those changes were fix/bug commits, so the churn is repair rather than feature work. 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-06-29..2026-09-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-29 10:33:17 +03:00' --until='2026-09-27 10:33:17 +03:00' --full-history --no-merges -- editor/src/plugins/absm/canvas.rs`: 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: fyrox-ui/src/formatted_text.rs fyrox-ui/src/formatted_text.rs:1059— fyrox-ui/src/formatted_text.rs changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 26 in FormattedText::arrange at line 1059. 3 of those changes were fix/bug commits, so the churn is repair rather than feature work. 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-06-29..2026-09-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-29 10:33:17 +03:00' --until='2026-09-27 10:33:17 +03:00' --full-history --no-merges -- fyrox-ui/src/formatted_text.rs`: 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: editor/src/plugins/inspector/mod.rs editor/src/plugins/inspector/mod.rs:456— editor/src/plugins/inspector/mod.rs changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in InspectorPlugin::on_ui_message at line 456. 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-06-29..2026-09-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-29 10:33:17 +03:00' --until='2026-09-27 10:33:17 +03:00' --full-history --no-merges -- editor/src/plugins/inspector/mod.rs`: 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: editor/src/plugins/settings.rs editor/src/plugins/settings.rs:241— editor/src/plugins/settings.rs changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in SettingsWindow::handle_ui_message at line 241. 2 of those changes were fix/bug commits, so the churn is repair rather than feature work. 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-06-29..2026-09-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-29 10:33:17 +03:00' --until='2026-09-27 10:33:17 +03:00' --full-history --no-merges -- editor/src/plugins/settings.rs`: 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.
Engine::handle_async_tasks (cognitive 47) fyrox-impl/src/engine/mod.rs:1805— Engine::handle_async_tasks has cognitive complexity 47 (threshold 15). Drivers by points: if/else 10 (46 pts), loops 1 (nesting depth added 36). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
Engine::reload_plugin (cognitive 46) fyrox-impl/src/engine/mod.rs:2555— Engine::reload_plugin has cognitive complexity 46 (threshold 15). Drivers by points: if/else 14 (30 pts), loops 15 (16 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.
Engine::handle_os_events (cognitive 30) fyrox-impl/src/engine/mod.rs:2076— Engine::handle_os_events has cognitive complexity 30 (threshold 15). Drivers by points: if/else 5 (17 pts), match/switch 5 (11 pts), loops 1 (2 pts) (nesting depth added 19). 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.
Engine::update_plugins (cognitive 16) fyrox-impl/src/engine/mod.rs:1908— Engine::update_plugins has cognitive complexity 16 (threshold 15). Drivers by points: loops 4 (11 pts), if/else 2 (5 pts) (nesting depth added 10). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
Engine::post_update_plugins (cognitive 16) fyrox-impl/src/engine/mod.rs:2000— Engine::post_update_plugins has cognitive complexity 16 (threshold 15). Drivers by points: loops 3 (7 pts), if/else 2 (5 pts), match/switch 1 (4 pts) (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.
EditNavmeshMode::on_left_mouse_button_down (cognitive 44) editor/src/interaction/navmesh/mod.rs:245— EditNavmeshMode::on_left_mouse_button_down has cognitive complexity 44 (threshold 15). Drivers by points: if/else 11 (28 pts), loops 4 (16 pts) (nesting depth added 29). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
EditNavmeshMode::on_mouse_move (cognitive 36) editor/src/interaction/navmesh/mod.rs:411— EditNavmeshMode::on_mouse_move has cognitive complexity 36 (threshold 15). Drivers by points: if/else 9 (21 pts), loops 2 (10 pts), match/switch 1 (4 pts), boolean chains 1 (nesting depth added 23). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
EditNavmeshMode::update (cognitive 22) editor/src/interaction/navmesh/mod.rs:512— EditNavmeshMode::update has cognitive complexity 22 (threshold 15). Drivers by points: if/else 5 (10 pts), loops 2 (8 pts), match/switch 1 (4 pts) (nesting depth added 14). 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.
EditNavmeshMode::on_left_mouse_button_up (cognitive 16) editor/src/interaction/navmesh/mod.rs:353— EditNavmeshMode::on_left_mouse_button_up has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (7 pts), loops 1 (5 pts), match/switch 1 (4 pts) (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.
EditNavmeshMode::on_key_down (cognitive 16) editor/src/interaction/navmesh/mod.rs:609— EditNavmeshMode::on_key_down has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (9 pts), loops 1 (4 pts), match/switch 1 (2 pts), boolean chains 1 (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.
Terrain::raycast (cognitive 41) fyrox-impl/src/scene/terrain/mod.rs:1957— Terrain::raycast has cognitive complexity 41 (threshold 15). Drivers by points: if/else 8 (26 pts), loops 4 (15 pts) (nesting depth added 29). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
Terrain::collect_render_data (cognitive 29) fyrox-impl/src/scene/terrain/mod.rs:2432— Terrain::collect_render_data has cognitive complexity 29 (threshold 15). Drivers by points: if/else 6 (14 pts), loops 5 (12 pts), boolean chains 3 (nesting depth added 15). 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.
Terrain::resize (cognitive 19) fyrox-impl/src/scene/terrain/mod.rs:1514— Terrain::resize has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (14 pts), loops 4 (5 pts) (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.
Terrain::align_chunk_margins (cognitive 17) fyrox-impl/src/scene/terrain/mod.rs:1271— Terrain::align_chunk_margins has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9, loops 4 (8 pts) (nesting depth added 4). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This shape REPEATS in the file: one other method here (Terrain::align_chunk_edges) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
Terrain::align_chunk_edges (cognitive 17) fyrox-impl/src/scene/terrain/mod.rs:1326— Terrain::align_chunk_edges has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9, loops 4 (8 pts) (nesting depth added 4). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This shape REPEATS in the file: one other method here (Terrain::align_chunk_margins) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
Graph::set_lightmap (cognitive 34) fyrox-impl/src/scene/graph/mod.rs:1014— Graph::set_lightmap has cognitive complexity 34 (threshold 15). Drivers by points: if/else 7 (22 pts), loops 4 (12 pts) (nesting depth added 23). 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.
Graph::apply_lightmap (cognitive 29) fyrox-impl/src/scene/graph/mod.rs:1071— Graph::apply_lightmap has cognitive complexity 29 (threshold 15). Drivers by points: if/else 5 (15 pts), loops 5 (14 pts) (nesting depth added 19). 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.
Graph::process_node_messages (cognitive 29) fyrox-impl/src/scene/graph/mod.rs:1303— Graph::process_node_messages has cognitive complexity 29 (threshold 15). Drivers by points: if/else 10 (22 pts), loops 3 (5 pts), match/switch 1 (2 pts) (nesting depth added 15). Of this number, 24 points are the body's own statements and 5 belong to one function item inside it that branches. 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.
Graph::build_indexed_path (cognitive 22) fyrox-impl/src/utils/astar.rs:434— Graph::build_indexed_path has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (18 pts), loops 2 (3 pts), boolean chains 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.
Graph::update_node (cognitive 18) fyrox-impl/src/scene/graph/mod.rs:1415— Graph::update_node has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (17 pts), boolean chains 1 (nesting depth added 11). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
Change coupling clique: directional.rs, point.rs, spot.rs fyrox-impl/src/scene/light/directional.rs— 3 files — `fyrox-impl/src/scene/light/directional.rs`, `fyrox-impl/src/scene/light/point.rs`, `fyrox-impl/src/scene/light/spot.rs` — all change together with no explicit dependency: a fully-connected co-change clique, not 3 separate couplings. They share one concern (thin parallel siblings over a common abstraction), so extract the shared part into ONE unit and the whole clique's coupling clears at once — you do not need to break each pair individually.
Change coupling clique: gbuffer.rs, csm.rs, point.rs, spot.rs fyrox-impl/src/renderer/gbuffer.rs— 4 files — `fyrox-impl/src/renderer/gbuffer.rs`, `fyrox-impl/src/renderer/shadow/csm.rs`, `fyrox-impl/src/renderer/shadow/point.rs`, `fyrox-impl/src/renderer/shadow/spot.rs` — all change together with no explicit dependency: a fully-connected co-change clique, not 6 separate couplings. They share one concern (thin parallel siblings over a common abstraction), so extract the shared part into ONE unit and the whole clique's coupling clears at once — you do not need to break each pair individually.
Change coupling clique: move_mode.rs, rotate_mode.rs, scale_mode.rs editor/src/interaction/move_mode.rs— 3 files — `editor/src/interaction/move_mode.rs`, `editor/src/interaction/rotate_mode.rs`, `editor/src/interaction/scale_mode.rs` — all change together with no explicit dependency: a fully-connected co-change clique, not 3 separate couplings. They share one concern (thin parallel siblings over a common abstraction), so extract the shared part into ONE unit and the whole clique's coupling clears at once — you do not need to break each pair individually.
Change coupling clique: move_gizmo.rs, rotate_gizmo.rs, scale_gizmo.rs editor/src/interaction/gizmo/move_gizmo.rs— 3 files — `editor/src/interaction/gizmo/move_gizmo.rs`, `editor/src/interaction/gizmo/rotate_gizmo.rs`, `editor/src/interaction/gizmo/scale_gizmo.rs` — all change together with no explicit dependency: a fully-connected co-change clique, not 3 separate couplings. They share one concern (thin parallel siblings over a common abstraction), so extract the shared part into ONE unit and the whole clique's coupling clears at once — you do not need to break each pair individually.
Change coupling clique: preview.rs, panel.rs, particle.rs editor/src/audio/preview.rs— 3 files — `editor/src/audio/preview.rs`, `editor/src/camera/panel.rs`, `editor/src/particle.rs` — all change together with no explicit dependency: a fully-connected co-change clique, not 3 separate couplings. They share one concern (thin parallel siblings over a common abstraction), so extract the shared part into ONE unit and the whole clique's coupling clears at once — you do not need to break each pair individually.
PaletteWidget::draw (cyclomatic 40) editor/src/plugins/tilemap/palette.rs:1696— PaletteWidget::draw has cyclomatic complexity 40 (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.
PaletteWidget::handle_routed_message (cyclomatic 27) editor/src/plugins/tilemap/palette.rs:1889— PaletteWidget::handle_routed_message 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.
PaletteWidget::sync_to_state (cyclomatic 22) editor/src/plugins/tilemap/palette.rs:675— PaletteWidget::sync_to_state 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.
PaletteWidget::draw_tile_colliders (cyclomatic 21) editor/src/plugins/tilemap/palette.rs:1408— PaletteWidget::draw_tile_colliders 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.
FixmeComment editor/src/audio/mod.rs:123— // FIXME: HACK! — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment editor/src/audio/mod.rs:151— // FIXME: HACK! — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment fyrox-core/src/visitor/impls.rs:416— // FIXME: Visiting an Rc/Arc is undefined behavior because it mutates the shared data. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment fyrox-core/src/visitor/impls.rs:422— // FIXME: Visiting an Rc/Arc is undefined behavior because it mutates the shared data. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
HackComment editor/src/plugins/animation/mod.rs:490— // HACK. This is unreliable to just use `bool` here. It should be wrapped into — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment editor/src/world/mod.rs:151— /// Hack. Due to delayed execution of UI code we can't sync immediately after we — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment editor/src/world/mod.rs:823— // Hack. See `self.sync_selection` for details. — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment fyrox-impl/src/scene/graph/physics/mod.rs:690— // HACK: Temporary solution for https://github.com/FyroxEngine/Fyrox/issues/365 — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
CurveEditor::handle_routed_message (cognitive 289) fyrox-ui/src/curve/mod.rs:574— CurveEditor::handle_routed_message has cognitive complexity 289 (threshold 15). Drivers by points: if/else 46 (188 pts), loops 10 (55 pts), match/switch 9 (45 pts), boolean chains 1 (nesting depth added 223). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
CurveEditor::draw_keys (cognitive 45) fyrox-ui/src/curve/mod.rs:1608— CurveEditor::draw_keys has cognitive complexity 45 (threshold 15). Drivers by points: if/else 7 (24 pts), match/switch 4 (18 pts), loops 2 (3 pts) (nesting depth added 32). 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.
CurveEditor::preview_message (cognitive 18) fyrox-ui/src/curve/mod.rs:1033— CurveEditor::preview_message has cognitive complexity 18 (threshold 15). Drivers by points: if/else 13 (17 pts), boolean chains 1 (nesting depth added 4). 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.
CurveEditor::pick (cognitive 17) fyrox-ui/src/curve/mod.rs:1345— CurveEditor::pick has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (14 pts), loops 2 (3 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.
TextBox::handle_routed_message (cognitive 266) fyrox-ui/src/text_box.rs:1128— TextBox::handle_routed_message has cognitive complexity 266 (threshold 15). Drivers by points: if/else 56 (232 pts), match/switch 5 (19 pts), loops 2 (10 pts), boolean chains 5 (nesting depth added 198). Of this number, 247 points are the body's own statements and 19 belong to one function item inside it that branches. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
TextBox::move_caret (cognitive 23) fyrox-ui/src/text_box.rs:544— TextBox::move_caret has cognitive complexity 23 (threshold 15). Drivers by points: if/else 11 (22 pts), boolean chains 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.
TextBox::draw (cognitive 23) fyrox-ui/src/text_box.rs:989— TextBox::draw has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (19 pts), loops 1 (3 pts), boolean chains 1 (nesting depth added 12). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
TextBox::select_word (cognitive 19) fyrox-ui/src/text_box.rs:905— TextBox::select_word has cognitive complexity 19 (threshold 15). Drivers by points: if/else 4 (9 pts), boolean chains 6, loops 2 (4 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.
Tile::handle_routed_message (cognitive 216) fyrox-ui/src/dock/tile.rs:461— Tile::handle_routed_message has cognitive complexity 216 (threshold 15). Drivers by points: if/else 30 (114 pts), loops 11 (64 pts), match/switch 10 (35 pts), boolean chains 3 (nesting depth added 162). Of this number, 205 points are the body's own statements and 11 belong to one function item inside it that branches. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
Tile::preview_message (cognitive 66) fyrox-ui/src/dock/tile.rs:818— Tile::preview_message has cognitive complexity 66 (threshold 15). Drivers by points: if/else 16 (38 pts), loops 3 (17 pts), match/switch 2 (10 pts), boolean chains 1 (nesting depth added 44). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
Tile::measure_override (cognitive 24) fyrox-ui/src/dock/tile.rs:294— Tile::measure_override has cognitive complexity 24 (threshold 15). Drivers by points: if/else 10 (16 pts), loops 3 (5 pts), match/switch 2 (3 pts) (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.
Tile::arrange_override (cognitive 18) fyrox-ui/src/dock/tile.rs:379— Tile::arrange_override has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (15 pts), match/switch 1 (2 pts), loops 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.
GameScene::draw_auxiliary_geometry::draw_recursively (cognitive 41) editor/src/scene/mod.rs:340— GameScene::draw_auxiliary_geometry::draw_recursively has cognitive complexity 41 (threshold 15). Drivers by points: if/else 17 (29 pts), loops 4 (11 pts), boolean chains 1 (nesting depth added 19). 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.
GameScene::update (cognitive 28) editor/src/scene/mod.rs:889— GameScene::update has cognitive complexity 28 (threshold 15). Drivers by points: if/else 10 (18 pts), loops 3 (5 pts), match/switch 3 (4 pts), boolean chains 1 (nesting depth added 11). Of this number, 25 points are the body's own statements and 3 belong to one function item inside it that branches. 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.
GameScene::on_drop (cognitive 23) editor/src/scene/mod.rs:683— GameScene::on_drop has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (23 pts) (nesting depth added 15). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
GameScene::on_drag_over (cognitive 18) editor/src/scene/mod.rs:589— GameScene::on_drag_over has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (14 pts), match/switch 2 (4 pts) (nesting depth added 10). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
fyrox_ui::transform_size (cognitive 41) fyrox-ui/src/lib.rs:3871— fyrox_ui::transform_size has cognitive complexity 41 (threshold 15). Drivers by points: if/else 22 (33 pts), boolean chains 8 (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.
fyrox_ui::menu::keyboard_navigation (cognitive 26) fyrox-ui/src/menu.rs:1241— fyrox_ui::menu::keyboard_navigation has cognitive complexity 26 (threshold 15). Drivers by points: if/else 13 (24 pts), boolean chains 1, match/switch 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.
fyrox_ui::markdown::markdown_to_visual_tree::traverse_ast_recursively (cognitive 25) fyrox-ui/src/markdown.rs:70— fyrox_ui::markdown::markdown_to_visual_tree::traverse_ast_recursively has cognitive complexity 25 (threshold 15). Drivers by points: if/else 5 (13 pts), loops 3 (9 pts), match/switch 2 (3 pts) (nesting depth added 15). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
fyrox_ui::file_browser::fs_tree::find_tree_item (cognitive 23) fyrox-ui/src/file_browser/fs_tree.rs:75— fyrox_ui::file_browser::fs_tree::find_tree_item has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (17 pts), loops 2 (6 pts) (nesting depth added 12). 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.
fyrox_build_tools::export::export (cognitive 19) fyrox-build-tools/src/export/mod.rs:148— fyrox_build_tools::export::export has cognitive complexity 19 (threshold 15). Drivers by points: match/switch 5 (10 pts), if/else 4 (6 pts), loops 2 (3 pts) (nesting depth added 8). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
fyrox_build_tools::export::build_package (cognitive 17) fyrox-build-tools/src/export/mod.rs:86— fyrox_build_tools::export::build_package has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (10 pts), match/switch 3 (4 pts), loops 2 (3 pts) (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.
fyrox_build_tools::export::pc::copy_binaries (cognitive 17) fyrox-build-tools/src/export/pc.rs:40— fyrox_build_tools::export::pc::copy_binaries has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (12 pts), match/switch 1 (3 pts), loops 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.
fyrox_build_tools::export::android::copy_binaries (cognitive 17) fyrox-build-tools/src/export/android.rs:52— fyrox_build_tools::export::android::copy_binaries has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (12 pts), match/switch 1 (3 pts), loops 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.
TooManyFields: Widget fyrox-ui/src/widget.rs:572— TooManyFields — 60 stored fields beside 110 methods. The bar is 30 stored fields; this is 30 over it, 2.00× the bar. This is width in DATA, not behaviour: every reader that takes the whole type couples to all of its fields, so a change to any one of them is a change every reader has to be checked against. To reduce it, group the fields that are read together by the same callers into a smaller type of their own, and have this one hold that type as a single member — each reader then names only the group it uses.
TooManyFields: WidgetBuilder fyrox-ui/src/widget.rs:1688— TooManyFields — 39 stored fields beside 46 methods. The bar is 30 stored fields; this is 9 over it, 1.30× the bar. This is width in DATA, not behaviour: every reader that takes the whole type couples to all of its fields, so a change to any one of them is a change every reader has to be checked against. To reduce it, group the fields that are read together by the same callers into a smaller type of their own, and have this one hold that type as a single member — each reader then names only the group it uses.
TooManyFields: ProjectManager project-manager/src/manager.rs:132— TooManyFields — 38 stored fields beside 26 methods. The bar is 30 stored fields; this is 8 over it, 1.27× the bar. This is width in DATA, not behaviour: every reader that takes the whole type couples to all of its fields, so a change to any one of them is a change every reader has to be checked against. To reduce it, group the fields that are read together by the same callers into a smaller type of their own, and have this one hold that type as a single member — each reader then names only the group it uses.
TooManyFields: UserInterface fyrox-ui/src/lib.rs:736— TooManyFields — 34 stored fields beside 95 methods. The bar is 30 stored fields; this is 4 over it, 1.13× the bar. This is width in DATA, not behaviour: every reader that takes the whole type couples to all of its fields, so a change to any one of them is a change every reader has to be checked against. To reduce it, group the fields that are read together by the same callers into a smaller type of their own, and have this one hold that type as a single member — each reader then names only the group it uses.
Duplicated block (26 lines × 2) editor/src/plugins/tilemap/interaction_mode.rs:318— editor/src/plugins/tilemap/interaction_mode.rs:318-343 | editor/src/plugins/tilemap/interaction_mode.rs:358-383 — both copies are in the same file, so extract the 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 (26 lines × 2) fyrox-impl/src/renderer/settings.rs:180— fyrox-impl/src/renderer/settings.rs:180-205 | fyrox-impl/src/renderer/settings.rs:216-241 — both copies are in the same file, so extract the 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 (26 lines × 2) fyrox-ui/src/inspector/editors/inspectable.rs:136— fyrox-ui/src/inspector/editors/inspectable.rs:136-161 | fyrox-ui/src/inspector/editors/refcell.rs:130-155 — before extracting anything, compare `fyrox-ui/src/inspector/editors/inspectable.rs` and `fyrox-ui/src/inspector/editors/refcell.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 52 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 (26 lines × 2) fyrox-ui/src/lib.rs:3926— fyrox-ui/src/lib.rs:3926-3951 | fyrox-ui/src/lib.rs:3958-3983 — both copies are in the same file, so extract the 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 (18 lines × 2) editor/src/plugins/inspector/editors/dyntype.rs:359— editor/src/plugins/inspector/editors/dyntype.rs:359-376 | editor/src/plugins/inspector/editors/script.rs:458-475 — before extracting anything, compare `editor/src/plugins/inspector/editors/dyntype.rs` and `editor/src/plugins/inspector/editors/script.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 110 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 (18 lines × 2) fyrox-scripts/src/camera.rs:152— fyrox-scripts/src/camera.rs:152-169 | fyrox-scripts/src/camera.rs: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.
Duplicated block (18 lines × 2) fyrox-ui/src/inspector/editors/array.rs:134— fyrox-ui/src/inspector/editors/array.rs:134-151 | fyrox-ui/src/inspector/editors/array.rs:408-425 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (18 lines × 2) fyrox-ui/src/matrix.rs:161— fyrox-ui/src/matrix.rs:161-178 | fyrox-ui/src/vec.rs:198-215 — before extracting anything, compare `fyrox-ui/src/matrix.rs` and `fyrox-ui/src/vec.rs` 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 (10 lines × 3) editor/src/plugins/tilemap/interaction_mode.rs:329— editor/src/plugins/tilemap/interaction_mode.rs:329-338 | editor/src/plugins/tilemap/interaction_mode.rs:369-378 | editor/src/plugins/tilemap/interaction_mode.rs:408-417 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (10 lines × 3) fyrox-impl/src/scene/dim2/rectangle.rs:386— fyrox-impl/src/scene/dim2/rectangle.rs:386-395 | fyrox-impl/src/scene/particle_system/mod.rs:607-616 | fyrox-impl/src/scene/sprite.rs:381-390 — before extracting anything, compare `fyrox-impl/src/scene/dim2/rectangle.rs` and `fyrox-impl/src/scene/sprite.rs` as WHOLE FILES: this scan already matched 3 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. 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 (10 lines × 3) fyrox-ui/src/inspector/editors/array.rs:138— fyrox-ui/src/inspector/editors/array.rs:138-147 | fyrox-ui/src/inspector/editors/array.rs:412-421 | fyrox-ui/src/inspector/editors/collection.rs:609-618 — before extracting anything, compare `fyrox-ui/src/inspector/editors/array.rs` and `fyrox-ui/src/inspector/editors/collection.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 76 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 × 3) fyrox-ui/src/inspector/editors/mod.rs:748— fyrox-ui/src/inspector/editors/mod.rs:748-757 | fyrox-ui/src/inspector/editors/mod.rs:758-767 | fyrox-ui/src/inspector/editors/mod.rs:768-777 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (8–10 lines × 2) editor/src/plugins/absm/state_graph/mod.rs:307— editor/src/plugins/absm/state_graph/mod.rs:307-316 | editor/src/plugins/absm/state_viewer/mod.rs:422-429 — `editor/src/plugins/absm/state_graph/mod.rs` and `editor/src/plugins/absm/state_viewer/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 46 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (8–10 lines × 2) editor/src/scene/mod.rs:299— editor/src/scene/mod.rs:299-306 | editor/src/ui_scene/mod.rs:271-280 — 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 (8–10 lines × 2) fyrox-math/src/lib.rs:135— fyrox-math/src/lib.rs:135-144 | fyrox-math/src/lib.rs:297-304 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8–10 lines × 2) fyrox-ui/src/nine_patch.rs:260— fyrox-ui/src/nine_patch.rs:260-269 | fyrox-ui/src/nine_patch.rs:282-289 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 3) fyrox-core/src/visitor/impls.rs:55— fyrox-core/src/visitor/impls.rs:55-62 | fyrox-core/src/visitor/mod.rs:152-159 | fyrox-core/src/visitor/pod.rs:161-168 — 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 (8 lines × 3) fyrox-impl/src/scene/terrain/brushstroke/mod.rs:987— fyrox-impl/src/scene/terrain/brushstroke/mod.rs:987-994 | fyrox-impl/src/scene/terrain/brushstroke/mod.rs:1000-1007 | fyrox-impl/src/scene/terrain/brushstroke/mod.rs:1011-1018 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (8 lines × 3) fyrox-ui/src/inspector/editors/char.rs:52— fyrox-ui/src/inspector/editors/char.rs:52-59 | fyrox-ui/src/inspector/editors/immutable_string.rs:56-63 | fyrox-ui/src/inspector/editors/string.rs:52-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 all 3 call sites, so a change lands once.
Duplicated block (8 lines × 3) editor/src/interaction/move_mode.rs:497— editor/src/interaction/move_mode.rs:497-504 | editor/src/interaction/rotate_mode.rs:279-286 | editor/src/interaction/scale_mode.rs:254-261 — before extracting anything, compare `editor/src/interaction/rotate_mode.rs` and `editor/src/interaction/scale_mode.rs` as WHOLE FILES: this scan already matched 7 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 × 3) editor/src/plugins/tilemap/colliders_tab.rs:154— editor/src/plugins/tilemap/colliders_tab.rs:154-160 | editor/src/plugins/tilemap/macro_tab.rs:209-215 | editor/src/plugins/tilemap/properties_tab.rs:258-264 — before extracting anything, compare `editor/src/plugins/tilemap/colliders_tab.rs` and `editor/src/plugins/tilemap/macro_tab.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 113 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 3) editor/src/plugins/tilemap/commands.rs:156— editor/src/plugins/tilemap/commands.rs:156-162 | editor/src/plugins/tilemap/commands.rs:192-198 | editor/src/plugins/tilemap/commands.rs:228-234 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (7 lines × 3) editor/src/plugins/inspector/editors/font.rs:225— editor/src/plugins/inspector/editors/font.rs:225-232 | editor/src/plugins/inspector/editors/surface.rs:343-350 | editor/src/plugins/material/editor.rs:406-412 — 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 (7 lines × 3) fyrox-ui/src/inspector/editors/bit.rs:78— fyrox-ui/src/inspector/editors/bit.rs:78-84 | fyrox-ui/src/inspector/editors/numeric.rs:98-104 | fyrox-ui/src/inspector/editors/uuid.rs:64-70 — 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.
Tile::handle_routed_message (cyclomatic 69) fyrox-ui/src/dock/tile.rs:461— Tile::handle_routed_message has cyclomatic complexity 69 (threshold 15). Of this number, 67 points are the body's own statements and 2 belong to one function item inside it that branches. 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.
Tile::preview_message (cyclomatic 24) fyrox-ui/src/dock/tile.rs:818— Tile::preview_message 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.
Tile::measure_override (cyclomatic 17) fyrox-ui/src/dock/tile.rs:294— Tile::measure_override 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.
TrackList::handle_ui_message (cyclomatic 60) editor/src/plugins/animation/track.rs:926— TrackList::handle_ui_message has cyclomatic complexity 60 (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.
TrackList::sync_to_model (cyclomatic 31) editor/src/plugins/animation/track.rs:1435— TrackList::sync_to_model 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.
TrackList::on_add_key_pressed (cyclomatic 26) editor/src/plugins/animation/track.rs:764— TrackList::on_add_key_pressed 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.
Toolbar::handle_ui_message (cyclomatic 25) editor/src/plugins/animation/toolbar.rs:727— Toolbar::handle_ui_message has cyclomatic complexity 25 (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.
Toolbar::handle_ui_message (cyclomatic 24) editor/src/plugins/absm/toolbar.rs:160— Toolbar::handle_ui_message 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.
Toolbar::post_handle_ui_message (cyclomatic 16) editor/src/plugins/animation/toolbar.rs:906— Toolbar::post_handle_ui_message 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.
PhysicsWorld::sync_to_rigid_body_node (cyclomatic 22) fyrox-impl/src/scene/graph/physics/mod.rs:1489— PhysicsWorld::sync_to_rigid_body_node 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.
PhysicsWorld::sync_to_rigid_body_node (cyclomatic 19) fyrox-impl/src/scene/dim2/physics/mod.rs:1049— PhysicsWorld::sync_to_rigid_body_node 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.
PhysicsWorld::sync_to_joint_node (cyclomatic 16) fyrox-impl/src/scene/graph/physics/mod.rs:1838— PhysicsWorld::sync_to_joint_node 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.
Repeated repair: fyrox-ui/src/inspector/editors/inspectable.rs fyrox-ui/src/inspector/editors/inspectable.rs:130— fyrox-ui/src/inspector/editors/inspectable.rs 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 3 (its worst body is InspectablePropertyEditorDefinition::create_message at line 130), 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: “do not compact fields in the inspector + always show `revert` button”; “fixed style for hash map property editor”; “fixed layout of inheritable property editor + styling”. 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-06-29..2026-09-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-29 10:33:17 +03:00' --until='2026-09-27 10:33:17 +03:00' --full-history --no-merges -- fyrox-ui/src/inspector/editors/inspectable.rs`: 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: fyrox-core-derive/src/reflect.rs fyrox-core-derive/src/reflect.rs:116— fyrox-core-derive/src/reflect.rs changed 4 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 8 (its worst body is fyrox_core_derive::reflect::quote_field_prop at line 116), 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: “fixed `field_direct_ref/mut` for structs with hidden fields”; “fixed incorrect impl of derived `fields_count`”; “fixed tuple elements naming”. 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-06-29..2026-09-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-29 10:33:17 +03:00' --until='2026-09-27 10:33:17 +03:00' --full-history --no-merges -- fyrox-core-derive/src/reflect.rs`: 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: editor/src/plugins/inspector/editors/dyntype.rs editor/src/plugins/inspector/editors/dyntype.rs:296— editor/src/plugins/inspector/editors/dyntype.rs changed 4 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 6 (its worst body is DynTypePropertyEditorDefinition::create_message at line 296), 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: “fixed tests”; “fixed dyn type editor + tests”; “fixed layout of inheritable property editor + styling”. 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-06-29..2026-09-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-29 10:33:17 +03:00' --until='2026-09-27 10:33:17 +03:00' --full-history --no-merges -- editor/src/plugins/inspector/editors/dyntype.rs`: 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.
TrackList::handle_ui_message (cognitive 137) editor/src/plugins/animation/track.rs:926— TrackList::handle_ui_message has cognitive complexity 137 (threshold 15). Drivers by points: if/else 49 (106 pts), match/switch 4 (17 pts), loops 3 (12 pts), boolean chains 2 (nesting depth added 79). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
TrackList::on_add_key_pressed (cognitive 86) editor/src/plugins/animation/track.rs:764— TrackList::on_add_key_pressed has cognitive complexity 86 (threshold 15). Drivers by points: if/else 25 (72 pts), loops 4 (10 pts), match/switch 1 (4 pts) (nesting depth added 56). 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.
TrackList::sync_to_model (cognitive 82) editor/src/plugins/animation/track.rs:1435— TrackList::sync_to_model has cognitive complexity 82 (threshold 15). Drivers by points: if/else 17 (53 pts), match/switch 6 (20 pts), loops 4 (9 pts) (nesting depth added 55). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
AssetBrowser::handle_ui_message (cognitive 122) editor/src/asset/mod.rs:631— AssetBrowser::handle_ui_message has cognitive complexity 122 (threshold 15). Drivers by points: if/else 41 (107 pts), loops 3 (9 pts), match/switch 2 (4 pts), boolean chains 2 (nesting depth added 74). Of this number, 115 points are the body's own statements and 7 belong to one function item inside it that branches. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
AssetBrowser::on_message (cognitive 46) editor/src/asset/mod.rs:930— AssetBrowser::on_message has cognitive complexity 46 (threshold 15). Drivers by points: if/else 10 (36 pts), loops 3 (10 pts) (nesting depth added 33). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
AssetBrowser::refresh (cognitive 27) editor/src/asset/mod.rs:503— AssetBrowser::refresh has cognitive complexity 27 (threshold 15). Drivers by points: if/else 12 (24 pts), 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.
MenuItem::handle_routed_message (cognitive 101) fyrox-ui/src/menu.rs:546— MenuItem::handle_routed_message has cognitive complexity 101 (threshold 15). Drivers by points: if/else 27 (78 pts), loops 3 (11 pts), match/switch 3 (8 pts), boolean chains 4 (nesting depth added 64). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
MenuItem::preview_message (cognitive 29) fyrox-ui/src/menu.rs:719— MenuItem::preview_message has cognitive complexity 29 (threshold 15). Drivers by points: if/else 9 (26 pts), loops 1 (3 pts) (nesting depth added 19). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
MenuItem::handle_os_event (cognitive 16) fyrox-ui/src/menu.rs:756— MenuItem::handle_os_event has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (15 pts), boolean chains 1 (nesting depth added 10). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
Toolbar::handle_ui_message (cognitive 62) editor/src/plugins/absm/toolbar.rs:160— Toolbar::handle_ui_message has cognitive complexity 62 (threshold 15). Drivers by points: if/else 22 (47 pts), loops 3 (15 pts) (nesting depth added 37). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
Toolbar::post_handle_ui_message (cognitive 48) editor/src/plugins/animation/toolbar.rs:906— Toolbar::post_handle_ui_message has cognitive complexity 48 (threshold 15). Drivers by points: if/else 13 (36 pts), match/switch 2 (7 pts), loops 1 (4 pts), boolean chains 1 (nesting depth added 31). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
Toolbar::handle_ui_message (cognitive 34) editor/src/plugins/animation/toolbar.rs:727— Toolbar::handle_ui_message has cognitive complexity 34 (threshold 15). Drivers by points: if/else 25 (34 pts) (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.
CameraController::pick_recursive (cognitive 53) editor/src/camera/mod.rs:677— CameraController::pick_recursive has cognitive complexity 53 (threshold 15). Drivers by points: if/else 16 (47 pts), boolean chains 5, loops 1 (nesting depth added 31). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
CameraController::update (cognitive 26) editor/src/camera/mod.rs:555— CameraController::update has cognitive complexity 26 (threshold 15). Drivers by points: if/else 16 (24 pts), boolean chains 1, match/switch 1 (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.
CameraController::pick (cognitive 18) editor/src/camera/mod.rs:788— CameraController::pick has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11 (15 pts), loops 1 (2 pts), boolean chains 1 (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.
SceneGraph::restore_integrity (cognitive 52) fyrox-graph/src/lib.rs:1197— SceneGraph::restore_integrity has cognitive complexity 52 (threshold 15). Drivers by points: if/else 15 (43 pts), loops 4 (8 pts), boolean chains 1 (nesting depth added 32). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
SceneGraph::restore_original_handles_and_inherit_properties (cognitive 26) fyrox-graph/src/lib.rs:1354— SceneGraph::restore_original_handles_and_inherit_properties has cognitive complexity 26 (threshold 15). Drivers by points: if/else 7 (21 pts), match/switch 1 (4 pts), loops 1 (nesting depth added 17). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
SceneGraph::remap_handles (cognitive 20) fyrox-graph/src/lib.rs:1455— SceneGraph::remap_handles has cognitive complexity 20 (threshold 15). Drivers by points: if/else 4 (15 pts), loops 3 (5 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.
Inspector::handle_context_menu_message_ex (cognitive 45) fyrox-ui/src/inspector/mod.rs:795— Inspector::handle_context_menu_message_ex has cognitive complexity 45 (threshold 15). Drivers by points: if/else 17 (39 pts), loops 1 (5 pts), match/switch 1 (nesting depth added 26). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
Inspector::handle_routed_message (cognitive 43) fyrox-ui/src/inspector/mod.rs:1665— Inspector::handle_routed_message has cognitive complexity 43 (threshold 15). Drivers by points: if/else 13 (36 pts), loops 2 (5 pts), match/switch 1 (2 pts) (nesting depth added 27). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
Inspector::preview_message (cognitive 16) fyrox-ui/src/inspector/mod.rs:1760— Inspector::preview_message has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (15 pts), boolean chains 1 (nesting depth added 10). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
TerrainInteractionMode::on_left_mouse_button_down (cognitive 30) editor/src/interaction/terrain.rs:281— TerrainInteractionMode::on_left_mouse_button_down has cognitive complexity 30 (threshold 15). Drivers by points: if/else 11 (29 pts), boolean chains 1 (nesting depth added 18). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
TerrainInteractionMode::on_mouse_move (cognitive 22) editor/src/interaction/terrain.rs:356— TerrainInteractionMode::on_mouse_move has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (17 pts), match/switch 1 (5 pts) (nesting depth added 14). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
TerrainInteractionMode::on_hot_key_pressed (cognitive 17) editor/src/interaction/terrain.rs:481— TerrainInteractionMode::on_hot_key_pressed has cognitive complexity 17 (threshold 15). Drivers by points: if/else 12 (14 pts), match/switch 2 (3 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.
TileMapInteractionMode::on_left_mouse_button_down (cognitive 29) editor/src/plugins/tilemap/interaction_mode.rs:487— TileMapInteractionMode::on_left_mouse_button_down has cognitive complexity 29 (threshold 15). Drivers by points: if/else 12 (23 pts), loops 1 (4 pts), match/switch 1 (2 pts) (nesting depth added 15). 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.
TileMapInteractionMode::on_left_mouse_button_up (cognitive 19) editor/src/plugins/tilemap/interaction_mode.rs:585— TileMapInteractionMode::on_left_mouse_button_up has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (18 pts), match/switch 1 (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.
TileMapInteractionMode::on_mouse_move (cognitive 17) editor/src/plugins/tilemap/interaction_mode.rs:680— TileMapInteractionMode::on_mouse_move has cognitive complexity 17 (threshold 15). Drivers by points: if/else 13 (16 pts), match/switch 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.
Duplicated block (27 lines × 2) editor/src/plugins/tilemap/colliders_tab.rs:193— editor/src/plugins/tilemap/colliders_tab.rs:193-219 | editor/src/plugins/tilemap/macro_tab.rs:259-285 — before extracting anything, compare `editor/src/plugins/tilemap/colliders_tab.rs` and `editor/src/plugins/tilemap/macro_tab.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 113 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (27 lines × 2) fyrox-impl/src/scene/dim2/physics/mod.rs:1297— fyrox-impl/src/scene/dim2/physics/mod.rs:1297-1323 | fyrox-impl/src/scene/graph/physics/mod.rs:1810-1836 — before extracting anything, compare `fyrox-impl/src/scene/dim2/physics/mod.rs` and `fyrox-impl/src/scene/graph/physics/mod.rs` as WHOLE FILES: this scan already matched 34 separate duplicated blocks between them, totalling at least 555 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 (27 lines × 2) fyrox-impl/src/scene/tilemap/autotile.rs:152— fyrox-impl/src/scene/tilemap/autotile.rs:152-178 | fyrox-impl/src/scene/tilemap/autotile.rs:262-288 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (25 lines × 2) fyrox-impl/src/engine/mod.rs:509— fyrox-impl/src/engine/mod.rs:509-533 | fyrox-impl/src/engine/mod.rs:540-564 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (25 lines × 2) fyrox-resource/src/manager.rs:498— fyrox-resource/src/manager.rs:498-522 | fyrox-resource/src/manager.rs:604-628 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (25 lines × 2) fyrox-ui/src/lib.rs:2871— fyrox-ui/src/lib.rs:2871-2895 | fyrox-ui/src/lib.rs:3153-3177 — both copies are in the same file, so extract the 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 (23 lines × 2) fyrox-impl/src/renderer/light.rs:914— fyrox-impl/src/renderer/light.rs:914-936 | fyrox-impl/src/renderer/light.rs:992-1014 — both copies are in the same file, so extract the 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 (23 lines × 2) fyrox-impl/src/scene/dim2/physics/mod.rs:1054— fyrox-impl/src/scene/dim2/physics/mod.rs:1054-1076 | fyrox-impl/src/scene/graph/physics/mod.rs:1494-1516 — before extracting anything, compare `fyrox-impl/src/scene/dim2/physics/mod.rs` and `fyrox-impl/src/scene/graph/physics/mod.rs` as WHOLE FILES: this scan already matched 34 separate duplicated blocks between them, totalling at least 555 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 (23 lines × 2) fyrox-ui/src/inspector/editors/hashmap/mod.rs:130— fyrox-ui/src/inspector/editors/hashmap/mod.rs:130-152 | fyrox-ui/src/inspector/editors/hashmap/mod.rs:182-204 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (21 lines × 2) editor/src/plugins/animation/toolbar.rs:276— editor/src/plugins/animation/toolbar.rs:276-296 | editor/src/plugins/animation/toolbar.rs:929-949 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (21 lines × 2) editor/src/plugins/tilemap/panel.rs:287— editor/src/plugins/tilemap/panel.rs:287-307 | editor/src/plugins/tilemap/tile_bounds_editor.rs:201-221 — 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 (21 lines × 2) fyrox-core/src/visitor/reader/ascii.rs:379— fyrox-core/src/visitor/reader/ascii.rs:379-399 | fyrox-core/src/visitor/reader/binary.rs:250-270 — 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 (20 lines × 2) editor/src/plugins/absm/mod.rs:851— editor/src/plugins/absm/mod.rs:851-870 | editor/src/plugins/animation/mod.rs:1003-1022 — `editor/src/plugins/absm/mod.rs` and `editor/src/plugins/animation/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 6 separate duplicated blocks between them, totalling at least 68 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (20 lines × 2) fyrox-impl/src/scene/dim2/physics/mod.rs:677— fyrox-impl/src/scene/dim2/physics/mod.rs:677-696 | fyrox-impl/src/scene/graph/physics/mod.rs:1119-1138 — before extracting anything, compare `fyrox-impl/src/scene/dim2/physics/mod.rs` and `fyrox-impl/src/scene/graph/physics/mod.rs` as WHOLE FILES: this scan already matched 34 separate duplicated blocks between them, totalling at least 555 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 (20 lines × 2) fyrox-impl/src/scene/dim2/physics/mod.rs:1080— fyrox-impl/src/scene/dim2/physics/mod.rs:1080-1099 | fyrox-impl/src/scene/graph/physics/mod.rs:1557-1576 — before extracting anything, compare `fyrox-impl/src/scene/dim2/physics/mod.rs` and `fyrox-impl/src/scene/graph/physics/mod.rs` as WHOLE FILES: this scan already matched 34 separate duplicated blocks between them, totalling at least 555 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 (18–19 lines × 2) editor/src/plugins/inspector/editors/dyntype.rs:378— editor/src/plugins/inspector/editors/dyntype.rs:378-396 | editor/src/plugins/inspector/editors/script.rs:477-494 — before extracting anything, compare `editor/src/plugins/inspector/editors/dyntype.rs` and `editor/src/plugins/inspector/editors/script.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 110 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 (18–19 lines × 2) fyrox-impl/src/scene/dim2/physics/mod.rs:1425— fyrox-impl/src/scene/dim2/physics/mod.rs:1425-1442 | fyrox-impl/src/scene/graph/physics/mod.rs:1946-1964 — before extracting anything, compare `fyrox-impl/src/scene/dim2/physics/mod.rs` and `fyrox-impl/src/scene/graph/physics/mod.rs` as WHOLE FILES: this scan already matched 34 separate duplicated blocks between them, totalling at least 555 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 (18–19 lines × 2) fyrox-ui/src/inspector/editors/collection.rs:611— fyrox-ui/src/inspector/editors/collection.rs:611-629 | fyrox-ui/src/inspector/editors/hashmap/mod.rs:396-413 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (12 lines × 3) editor/src/plugins/tilemap/colliders_tab.rs:242— editor/src/plugins/tilemap/colliders_tab.rs:242-253 | editor/src/plugins/tilemap/macro_tab.rs:311-322 | editor/src/plugins/tilemap/properties_tab.rs:466-477 — before extracting anything, compare `editor/src/plugins/tilemap/colliders_tab.rs` and `editor/src/plugins/tilemap/macro_tab.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 113 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 3) editor/src/plugins/tilemap/colliders_tab.rs:87— editor/src/plugins/tilemap/colliders_tab.rs:87-98 | editor/src/plugins/tilemap/macro_tab.rs:89-100 | editor/src/plugins/tilemap/properties_tab.rs:107-118 — before extracting anything, compare `editor/src/plugins/tilemap/colliders_tab.rs` and `editor/src/plugins/tilemap/macro_tab.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 113 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 3) editor/src/asset/mod.rs:972— editor/src/asset/mod.rs:972-983 | editor/src/export/mod.rs:272-283 | editor/src/plugins/inspector/editors/spritesheet/window.rs:334-345 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
Duplicated block (10–11 lines × 2) editor/src/plugins/tilemap/autotile.rs:514— editor/src/plugins/tilemap/autotile.rs:514-523 | editor/src/plugins/tilemap/wfc.rs:530-540 — before extracting anything, compare `editor/src/plugins/tilemap/autotile.rs` and `editor/src/plugins/tilemap/wfc.rs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 142 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (10–11 lines × 2) fyrox-graphics-gl/src/texture.rs:376— fyrox-graphics-gl/src/texture.rs:376-385 | fyrox-graphics-wgpu/src/texture.rs:464-474 — 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 (10–11 lines × 2) fyrox-impl/src/scene/mesh/surface.rs:636— fyrox-impl/src/scene/mesh/surface.rs:636-645 | fyrox-impl/src/scene/mesh/surface.rs:775-785 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 4) fyrox-graphics-gl/src/texture.rs:375— fyrox-graphics-gl/src/texture.rs:375-384 | fyrox-graphics-gl/src/texture.rs:580-589 | fyrox-graphics-wgpu/src/texture.rs:382-391 | fyrox-graphics-wgpu/src/texture.rs:463-472 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (10 lines × 4) editor/src/plugins/absm/mod.rs:530— editor/src/plugins/absm/mod.rs:530-539 | editor/src/plugins/animation/mod.rs:355-364 | editor/src/plugins/ragdoll.rs:1136-1145 | fyrox-ui/src/log.rs:250-259 — `editor/src/plugins/absm/mod.rs` and `editor/src/plugins/animation/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 6 separate duplicated blocks between them, totalling at least 68 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (10 lines × 4) fyrox-impl/src/scene/dim2/rectangle.rs:116— fyrox-impl/src/scene/dim2/rectangle.rs:116-125 | fyrox-impl/src/scene/mesh/vertex.rs:125-134 | fyrox-impl/src/scene/mesh/vertex.rs:227-236 | fyrox-impl/src/scene/mesh/vertex.rs:279-288 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (8–9 lines × 2) editor/src/plugins/tilemap/autotile.rs:523— editor/src/plugins/tilemap/autotile.rs:523-530 | editor/src/plugins/tilemap/wfc.rs:607-615 — before extracting anything, compare `editor/src/plugins/tilemap/autotile.rs` and `editor/src/plugins/tilemap/wfc.rs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 142 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (8–9 lines × 2) fyrox-core/src/visitor/impls.rs:58— fyrox-core/src/visitor/impls.rs:58-65 | fyrox-core/src/visitor/pod.rs:164-172 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (8–9 lines × 2) fyrox-impl/src/scene/mesh/surface.rs:355— fyrox-impl/src/scene/mesh/surface.rs:355-363 | fyrox-impl/src/scene/mesh/surface.rs:365-372 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
UserInterface::process_os_event (cyclomatic 70) fyrox-ui/src/lib.rs:2776— UserInterface::process_os_event has cyclomatic complexity 70 (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.
UserInterface::poll_single_message (cyclomatic 53) fyrox-ui/src/lib.rs:2354— UserInterface::poll_single_message has cyclomatic complexity 53 (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.
fyroxed_base::plugins::animation::track::type_id_to_supported_type (cyclomatic 47) editor/src/plugins/animation/track.rs:195— fyroxed_base::plugins::animation::track::type_id_to_supported_type has cyclomatic complexity 47 (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.
fyroxed_base::update (cyclomatic 21) editor/src/lib.rs:3183— fyroxed_base::update 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.
WgpuFrameBuffer::do_draw (cyclomatic 33) fyrox-graphics-wgpu/src/framebuffer.rs:489— WgpuFrameBuffer::do_draw has cyclomatic complexity 33 (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.
WgpuFrameBuffer::get_or_create_pipeline (cyclomatic 23) fyrox-graphics-wgpu/src/framebuffer.rs:253— WgpuFrameBuffer::get_or_create_pipeline has cyclomatic complexity 23 (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.
AnimationEditor::handle_ui_message (cyclomatic 30) editor/src/plugins/animation/mod.rs:366— AnimationEditor::handle_ui_message 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.
AnimationEditor::sync_to_model (cyclomatic 23) editor/src/plugins/animation/mod.rs:739— AnimationEditor::sync_to_model 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.
FormattedText::arrange (cyclomatic 26) fyrox-ui/src/formatted_text.rs:1059— FormattedText::arrange 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.
FormattedText::measure (cyclomatic 20) fyrox-ui/src/formatted_text.rs:924— FormattedText::measure 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.
TreeRoot::handle_routed_message (cyclomatic 26) fyrox-ui/src/tree.rs:844— TreeRoot::handle_routed_message 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.
TreeRoot::move_selection (cyclomatic 20) fyrox-ui/src/tree.rs:973— TreeRoot::move_selection 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.
WorldViewer::sync_graph (cyclomatic 24) editor/src/world/mod.rs:474— WorldViewer::sync_graph 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.
WorldViewer::handle_ui_message (cyclomatic 20) editor/src/world/mod.rs:683— WorldViewer::handle_ui_message 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.
ProjectManager::handle_ui_message (cyclomatic 23) project-manager/src/manager.rs:1248— ProjectManager::handle_ui_message 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.
ProjectManager::on_button_click (cyclomatic 16) project-manager/src/manager.rs:1094— ProjectManager::on_button_click 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.
AudioPanel::handle_ui_message (cyclomatic 22) editor/src/audio/mod.rs:370— AudioPanel::handle_ui_message 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.
AudioPanel::sync_to_model (cyclomatic 16) editor/src/audio/mod.rs:458— AudioPanel::sync_to_model 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.
NodeHandleMap::remap_inheritable_handles_internal (cyclomatic 22) fyrox-graph/src/lib.rs:310— NodeHandleMap::remap_inheritable_handles_internal 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.
NodeHandleMap::remap_handles_any (cyclomatic 21) fyrox-graph/src/lib.rs:208— NodeHandleMap::remap_handles_any 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.
CameraController::pick_recursive (cyclomatic 20) editor/src/camera/mod.rs:677— CameraController::pick_recursive 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.
CameraController::update (cyclomatic 18) editor/src/camera/mod.rs:555— CameraController::update has cyclomatic complexity 18 (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.
BitField::handle_routed_message (cyclomatic 18) fyrox-ui/src/bit.rs:322— BitField::handle_routed_message has cyclomatic complexity 18 (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.
BitField::draw (cyclomatic 17) fyrox-ui/src/bit.rs:232— BitField::draw 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.
Inspector::handle_routed_message (cyclomatic 18) fyrox-ui/src/inspector/mod.rs:1665— Inspector::handle_routed_message has cyclomatic complexity 18 (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.
Inspector::handle_context_menu_message_ex (cyclomatic 16) fyrox-ui/src/inspector/mod.rs:795— Inspector::handle_context_menu_message_ex 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.
SceneViewer::handle_ui_message (cognitive 113) editor/src/scene_viewer/mod.rs:692— SceneViewer::handle_ui_message has cognitive complexity 113 (threshold 15). Drivers by points: if/else 31 (79 pts), match/switch 7 (31 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 73). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
SceneViewer::sync_to_model (cognitive 20) editor/src/scene_viewer/mod.rs:923— SceneViewer::sync_to_model has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (17 pts), loops 3 (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.
StateViewer::sync_to_model (cognitive 98) editor/src/plugins/absm/state_viewer/mod.rs:410— StateViewer::sync_to_model has cognitive complexity 98 (threshold 15). Drivers by points: if/else 27 (71 pts), loops 7 (17 pts), match/switch 3 (9 pts), boolean chains 1 (nesting depth added 60). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
StateViewer::handle_ui_message (cognitive 21) editor/src/plugins/absm/state_viewer/mod.rs:271— StateViewer::handle_ui_message has cognitive complexity 21 (threshold 15). Drivers by points: if/else 4 (11 pts), match/switch 2 (9 pts), boolean chains 1 (nesting depth added 14). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
AbsmCanvas::handle_routed_message (cognitive 90) editor/src/plugins/absm/canvas.rs:416— AbsmCanvas::handle_routed_message has cognitive complexity 90 (threshold 15). Drivers by points: if/else 28 (63 pts), match/switch 5 (16 pts), loops 2 (7 pts), boolean chains 4 (nesting depth added 51). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
AbsmCanvas::sync_transitions_ends (cognitive 24) editor/src/plugins/absm/canvas.rs:246— AbsmCanvas::sync_transitions_ends has cognitive complexity 24 (threshold 15). Drivers by points: if/else 5 (16 pts), boolean chains 4, loops 2 (4 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.
AnimationEditor::sync_to_model (cognitive 70) editor/src/plugins/animation/mod.rs:739— AnimationEditor::sync_to_model has cognitive complexity 70 (threshold 15). Drivers by points: if/else 16 (48 pts), loops 4 (16 pts), match/switch 1 (4 pts), boolean chains 2 (nesting depth added 47). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
AnimationEditor::handle_ui_message (cognitive 53) editor/src/plugins/animation/mod.rs:366— AnimationEditor::handle_ui_message has cognitive complexity 53 (threshold 15). Drivers by points: if/else 14 (41 pts), match/switch 3 (9 pts), loops 1 (3 pts) (nesting depth added 35). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
WorldViewer::sync_graph (cognitive 69) editor/src/world/mod.rs:474— WorldViewer::sync_graph has cognitive complexity 69 (threshold 15). Drivers by points: if/else 16 (49 pts), loops 7 (18 pts), boolean chains 2 (nesting depth added 44). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
WorldViewer::handle_ui_message (cognitive 30) editor/src/world/mod.rs:683— WorldViewer::handle_ui_message has cognitive complexity 30 (threshold 15). Drivers by points: if/else 17 (28 pts), boolean chains 2 (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.
MachineLayer::evaluate_pose (cognitive 69) fyrox-animation/src/machine/layer.rs:590— MachineLayer::evaluate_pose has cognitive complexity 69 (threshold 15). Drivers by points: if/else 15 (50 pts), loops 4 (17 pts), boolean chains 2 (nesting depth added 48). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
MachineLayer::collect_active_animations_events (cognitive 34) fyrox-animation/src/machine/layer.rs:308— MachineLayer::collect_active_animations_events has cognitive complexity 34 (threshold 15). Drivers by points: if/else 10 (27 pts), loops 1 (4 pts), match/switch 1 (3 pts) (nesting depth added 22). 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.
WgpuFrameBuffer::do_draw (cognitive 68) fyrox-graphics-wgpu/src/framebuffer.rs:489— WgpuFrameBuffer::do_draw has cognitive complexity 68 (threshold 15). Drivers by points: if/else 29 (49 pts), boolean chains 8, match/switch 3 (8 pts), loops 2 (3 pts) (nesting depth added 26). 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.
WgpuFrameBuffer::get_or_create_pipeline (cognitive 25) fyrox-graphics-wgpu/src/framebuffer.rs:253— WgpuFrameBuffer::get_or_create_pipeline has cognitive complexity 25 (threshold 15). Drivers by points: if/else 17, match/switch 5, boolean chains 3. 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.
FormattedText::arrange (cognitive 65) fyrox-ui/src/formatted_text.rs:1059— FormattedText::arrange has cognitive complexity 65 (threshold 15). Drivers by points: if/else 17 (41 pts), loops 6 (16 pts), match/switch 3 (7 pts), boolean chains 1 (nesting depth added 38). 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.
FormattedText::measure (cognitive 31) fyrox-ui/src/formatted_text.rs:924— FormattedText::measure has cognitive complexity 31 (threshold 15). Drivers by points: if/else 14 (18 pts), loops 4 (8 pts), match/switch 2 (3 pts), boolean chains 2 (nesting depth added 9). 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.
BlendAnimationsByIndex::collect_animation_events (cognitive 64) fyrox-animation/src/machine/node/blend.rs:370— BlendAnimationsByIndex::collect_animation_events has cognitive complexity 64 (threshold 15). Drivers by points: if/else 14 (53 pts), loops 1 (6 pts), match/switch 1 (5 pts) (nesting depth added 48). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
BlendAnimationsByIndex::eval_pose (cognitive 21) fyrox-animation/src/machine/node/blend.rs:306— BlendAnimationsByIndex::eval_pose has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (21 pts) (nesting depth added 13). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
TreeRoot::move_selection (cognitive 61) fyrox-ui/src/tree.rs:973— TreeRoot::move_selection has cognitive complexity 61 (threshold 15). Drivers by points: if/else 16 (50 pts), loops 2 (8 pts), match/switch 1 (2 pts), boolean chains 1 (nesting depth added 41). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
TreeRoot::handle_routed_message (cognitive 59) fyrox-ui/src/tree.rs:844— TreeRoot::handle_routed_message has cognitive complexity 59 (threshold 15). Drivers by points: if/else 13 (44 pts), loops 3 (10 pts), match/switch 2 (5 pts) (nesting depth added 41). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
Popup::handle_routed_message (cognitive 58) fyrox-ui/src/popup.rs:386— Popup::handle_routed_message has cognitive complexity 58 (threshold 15). Drivers by points: if/else 17 (50 pts), match/switch 2 (6 pts), boolean chains 2 (nesting depth added 37). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
Popup::handle_os_event (cognitive 16) fyrox-ui/src/popup.rs:502— Popup::handle_os_event has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (14 pts), boolean chains 2 (nesting depth added 8). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
StateGraphViewer::sync_to_model (cognitive 53) editor/src/plugins/absm/state_graph/mod.rs:294— StateGraphViewer::sync_to_model has cognitive complexity 53 (threshold 15). Drivers by points: if/else 17 (40 pts), loops 5 (9 pts), match/switch 3, boolean chains 1 (nesting depth added 27). 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.
StateGraphViewer::handle_ui_message (cognitive 16) editor/src/plugins/absm/state_graph/mod.rs:164— StateGraphViewer::handle_ui_message has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (12 pts), match/switch 1 (3 pts), boolean chains 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.
UiSceneWorldViewerDataProvider::on_change_hierarchy_request (cognitive 40) editor/src/ui_scene/utils.rs:194— UiSceneWorldViewerDataProvider::on_change_hierarchy_request has cognitive complexity 40 (threshold 15). Drivers by points: if/else 7 (29 pts), loops 2 (7 pts), match/switch 1 (4 pts) (nesting depth added 30). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
UiSceneWorldViewerDataProvider::icon_of (cognitive 17) editor/src/ui_scene/utils.rs:124— UiSceneWorldViewerDataProvider::icon_of has cognitive complexity 17 (threshold 15). Drivers by points: if/else 17. 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.
Mesh::collect_render_data (cognitive 39) fyrox-impl/src/scene/mesh/mod.rs:691— Mesh::collect_render_data has cognitive complexity 39 (threshold 15). Drivers by points: if/else 12 (23 pts), loops 3 (8 pts), match/switch 2 (6 pts), boolean chains 2 (nesting depth added 20). 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.
Mesh::accurate_world_bounding_box (cognitive 30) fyrox-impl/src/scene/mesh/mod.rs:470— Mesh::accurate_world_bounding_box has cognitive complexity 30 (threshold 15). Drivers by points: if/else 6 (19 pts), loops 4 (11 pts) (nesting depth added 20). 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.
BitField::handle_routed_message (cognitive 38) fyrox-ui/src/bit.rs:322— BitField::handle_routed_message has cognitive complexity 38 (threshold 15). Drivers by points: if/else 13 (28 pts), match/switch 2 (8 pts), boolean chains 2 (nesting depth added 21). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
BitField::draw (cognitive 23) fyrox-ui/src/bit.rs:232— BitField::draw has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (14 pts), loops 5, boolean chains 4 (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.
ProjectManager::handle_ui_message (cognitive 38) project-manager/src/manager.rs:1248— ProjectManager::handle_ui_message has cognitive complexity 38 (threshold 15). Drivers by points: if/else 22 (38 pts) (nesting depth added 16). 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.
ProjectManager::handle_modes (cognitive 34) project-manager/src/manager.rs:836— ProjectManager::handle_modes has cognitive complexity 34 (threshold 15). Drivers by points: if/else 12 (29 pts), match/switch 2 (5 pts) (nesting depth added 20). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
AudioPanel::handle_ui_message (cognitive 36) editor/src/audio/mod.rs:370— AudioPanel::handle_ui_message has cognitive complexity 36 (threshold 15). Drivers by points: if/else 13 (22 pts), match/switch 2 (8 pts), loops 2 (6 pts) (nesting depth added 19). 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.
AudioPanel::sync_to_model (cognitive 28) editor/src/audio/mod.rs:458— AudioPanel::sync_to_model has cognitive complexity 28 (threshold 15). Drivers by points: if/else 8 (18 pts), loops 4 (7 pts), match/switch 2, boolean chains 1 (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.
Menu::handle_routed_message (cognitive 33) fyrox-ui/src/menu.rs:229— Menu::handle_routed_message has cognitive complexity 33 (threshold 15). Drivers by points: if/else 10 (27 pts), loops 1 (4 pts), 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.
Menu::handle_os_event (cognitive 27) fyrox-ui/src/menu.rs:281— Menu::handle_os_event has cognitive complexity 27 (threshold 15). Drivers by points: if/else 6 (21 pts), loops 1 (4 pts), boolean chains 2 (nesting depth added 18). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
WfcMacro::on_instance_ui_message (cognitive 32) editor/src/plugins/tilemap/wfc.rs:263— WfcMacro::on_instance_ui_message has cognitive complexity 32 (threshold 15). Drivers by points: if/else 17 (27 pts), loops 2 (5 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.
WfcMacro::create_command (cognitive 16) editor/src/plugins/tilemap/wfc.rs:698— WfcMacro::create_command has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 1, loops 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.
AudioPreviewPanel::handle_ui_message (cognitive 31) editor/src/audio/preview.rs:292— AudioPreviewPanel::handle_ui_message has cognitive complexity 31 (threshold 15). Drivers by points: if/else 12 (25 pts), loops 2 (6 pts) (nesting depth added 17). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
AudioPreviewPanel::enter_preview_mode (cognitive 21) editor/src/audio/preview.rs:210— AudioPreviewPanel::enter_preview_mode has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (19 pts), loops 1 (2 pts) (nesting depth added 15). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
InspectorContext::from_object (cognitive 31) fyrox-ui/src/inspector/mod.rs:1347— InspectorContext::from_object has cognitive complexity 31 (threshold 15). Drivers by points: if/else 11 (23 pts), match/switch 2 (7 pts), loops 1 (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.
InspectorContext::sync (cognitive 24) fyrox-ui/src/inspector/mod.rs:1567— InspectorContext::sync has cognitive complexity 24 (threshold 15). Drivers by points: if/else 10 (19 pts), match/switch 1 (4 pts), loops 1 (nesting depth added 12). 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.
NodeHandleMap::remap_inheritable_handles_internal (cognitive 30) fyrox-graph/src/lib.rs:310— NodeHandleMap::remap_inheritable_handles_internal has cognitive complexity 30 (threshold 15). Drivers by points: if/else 16 (23 pts), loops 3 (5 pts), boolean chains 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.
NodeHandleMap::remap_handles_any (cognitive 28) fyrox-graph/src/lib.rs:208— NodeHandleMap::remap_handles_any has cognitive complexity 28 (threshold 15). Drivers by points: if/else 15 (21 pts), loops 3 (5 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.
Ray::cylinder_intersection (cognitive 29) fyrox-math/src/ray.rs:331— Ray::cylinder_intersection has cognitive complexity 29 (threshold 15). Drivers by points: if/else 5 (15 pts), match/switch 2 (7 pts), loops 2 (6 pts), boolean chains 1 (nesting depth added 19). 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.
Ray::box_intersection (cognitive 17) fyrox-math/src/ray.rs:169— Ray::box_intersection has cognitive complexity 17 (threshold 15). Drivers by points: if/else 14, boolean chains 3. 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.
BlendSpace::collect_animation_events (cognitive 25) fyrox-animation/src/machine/node/blendspace.rs:157— BlendSpace::collect_animation_events has cognitive complexity 25 (threshold 15). Drivers by points: if/else 5 (16 pts), loops 1 (5 pts), match/switch 1 (4 pts) (nesting depth added 18). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
BlendSpace::fetch_weights (cognitive 18) fyrox-animation/src/machine/node/blendspace.rs:338— BlendSpace::fetch_weights has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (14 pts), loops 3 (4 pts) (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.
Navmesh::query_closest_internal (cognitive 22) fyrox-impl/src/utils/navmesh.rs:477— Navmesh::query_closest_internal has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (17 pts), loops 3 (5 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.
Navmesh::ray_cast (cognitive 16) fyrox-impl/src/utils/navmesh.rs:579— Navmesh::ray_cast has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (12 pts), loops 2 (4 pts) (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.
fyrox_graphics_wgpu::program::create_bind_group_layout_with_formats (cognitive 18) fyrox-graphics-wgpu/src/program.rs:142— fyrox_graphics_wgpu::program::create_bind_group_layout_with_formats has cognitive complexity 18 (threshold 15). Drivers by points: match/switch 3 (9 pts), if/else 4 (8 pts), loops 1 (nesting depth added 10). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
fyrox_graphics_wgpu::framebuffer::create_bind_group (cognitive 17) fyrox-graphics-wgpu/src/framebuffer.rs:1128— fyrox_graphics_wgpu::framebuffer::create_bind_group has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (7 pts), match/switch 2 (7 pts), loops 2 (3 pts) (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.
RotateInteractionMode::on_left_mouse_button_up (cognitive 17) editor/src/interaction/rotate_mode.rs:109— RotateInteractionMode::on_left_mouse_button_up has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (17 pts) (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.
RotateInteractionMode::on_mouse_move (cognitive 16) editor/src/interaction/rotate_mode.rs:191— RotateInteractionMode::on_mouse_move has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (13 pts), loops 1 (3 pts) (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.
SoundSource::set_buffer (cognitive 16) fyrox-sound/src/source.rs:209— SoundSource::set_buffer has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (14 pts), match/switch 1 (2 pts) (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.
SoundSource::render_until_block_end_resample (cognitive 16) fyrox-sound/src/source.rs:602— SoundSource::render_until_block_end_resample has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 3 (5 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.
Duplicated block (22–23 lines × 2) fyrox-impl/src/engine/mod.rs:478— fyrox-impl/src/engine/mod.rs:478-500 | fyrox-impl/src/engine/mod.rs:570-591 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (22–23 lines × 2) fyrox-impl/src/scene/dim2/physics/mod.rs:1102— fyrox-impl/src/scene/dim2/physics/mod.rs:1102-1123 | fyrox-impl/src/scene/graph/physics/mod.rs:1599-1621 — before extracting anything, compare `fyrox-impl/src/scene/dim2/physics/mod.rs` and `fyrox-impl/src/scene/graph/physics/mod.rs` as WHOLE FILES: this scan already matched 34 separate duplicated blocks between them, totalling at least 555 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 (22 lines × 2) editor/src/plugins/inspector/editors/dyntype.rs:273— editor/src/plugins/inspector/editors/dyntype.rs:273-294 | editor/src/plugins/inspector/editors/script.rs:371-392 — before extracting anything, compare `editor/src/plugins/inspector/editors/dyntype.rs` and `editor/src/plugins/inspector/editors/script.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 110 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 × 2) fyrox-impl/src/scene/dim2/physics/mod.rs:1452— fyrox-impl/src/scene/dim2/physics/mod.rs:1452-1473 | fyrox-impl/src/scene/graph/physics/mod.rs:1974-1995 — before extracting anything, compare `fyrox-impl/src/scene/dim2/physics/mod.rs` and `fyrox-impl/src/scene/graph/physics/mod.rs` as WHOLE FILES: this scan already matched 34 separate duplicated blocks between them, totalling at least 555 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 (19 lines × 2) fyrox-graph/src/lib.rs:237— fyrox-graph/src/lib.rs:237-255 | fyrox-graph/src/lib.rs:360-378 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (19 lines × 2) fyrox-ui/src/inspector/editors/array.rs:152— fyrox-ui/src/inspector/editors/array.rs:152-170 | fyrox-ui/src/inspector/editors/collection.rs:248-266 — before extracting anything, compare `fyrox-ui/src/inspector/editors/array.rs` and `fyrox-ui/src/inspector/editors/collection.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 76 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (17–18 lines × 2) editor/src/plugins/tilemap/autotile.rs:617— editor/src/plugins/tilemap/autotile.rs:617-634 | editor/src/plugins/tilemap/wfc.rs:635-651 — before extracting anything, compare `editor/src/plugins/tilemap/autotile.rs` and `editor/src/plugins/tilemap/wfc.rs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 142 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (17–18 lines × 2) editor/src/plugins/tilemap/palette.rs:1675— editor/src/plugins/tilemap/palette.rs:1675-1691 | editor/src/plugins/tilemap/palette.rs:1806-1823 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 4) editor/src/asset/creator.rs:144— editor/src/asset/creator.rs:144-157 | editor/src/light.rs:165-177 | editor/src/plugins/inspector/mod.rs:298-310 | editor/src/scene/dialog.rs:133-146 — before extracting anything, compare `editor/src/asset/creator.rs` and `editor/src/light.rs` 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. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 4) fyrox-impl/src/scene/dim2/joint.rs:349— fyrox-impl/src/scene/dim2/joint.rs:349-361 | fyrox-impl/src/scene/dim2/joint.rs:383-395 | fyrox-impl/src/scene/joint.rs:408-420 | fyrox-impl/src/scene/joint.rs:442-454 — before extracting anything, compare `fyrox-impl/src/scene/dim2/joint.rs` and `fyrox-impl/src/scene/joint.rs` 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. 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 (12 lines × 4) editor/src/plugins/collider/mod.rs:413— editor/src/plugins/collider/mod.rs:413-424 | editor/src/plugins/collider/mod.rs:551-562 | editor/src/plugins/probe.rs:184-195 | editor/src/plugins/probe.rs:245-256 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (12 lines × 4) editor/src/plugins/tilemap/autotile.rs:468— editor/src/plugins/tilemap/autotile.rs:468-479 | editor/src/plugins/tilemap/autotile.rs:619-630 | editor/src/plugins/tilemap/wfc.rs:503-514 | editor/src/plugins/tilemap/wfc.rs:637-648 — before extracting anything, compare `editor/src/plugins/tilemap/autotile.rs` and `editor/src/plugins/tilemap/wfc.rs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 142 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (11–12 lines × 2) fyrox-build-tools/src/lib.rs:149— fyrox-build-tools/src/lib.rs:149-159 | fyrox-build-tools/src/lib.rs:203-214 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11–12 lines × 2) fyrox-impl/src/scene/tilemap/autotile.rs:325— fyrox-impl/src/scene/tilemap/autotile.rs:325-336 | fyrox-impl/src/scene/tilemap/autotile.rs:489-499 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 5) editor/src/asset/creator.rs:165— editor/src/asset/creator.rs:165-174 | editor/src/export/mod.rs:336-345 | editor/src/light.rs:200-209 | editor/src/plugins/absm/blendspace.rs:809-818 | editor/src/plugins/curve_editor.rs:330-339 — before extracting anything, compare `editor/src/asset/creator.rs` and `editor/src/light.rs` 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. 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 (10 lines × 5) editor/src/plugins/ragdoll.rs:729— editor/src/plugins/ragdoll.rs:729-738 | editor/src/plugins/ragdoll.rs:742-753 | editor/src/plugins/ragdoll.rs:765-774 | editor/src/plugins/ragdoll.rs:831-840 | editor/src/plugins/ragdoll.rs:870-879 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (9 lines × 3) editor/src/plugins/absm/blendspace.rs:186— editor/src/plugins/absm/blendspace.rs:186-194 | editor/src/plugins/absm/canvas.rs:389-397 | fyrox-ui/src/canvas.rs:93-101 — 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 (9 lines × 3) editor/src/interaction/move_mode.rs:487— editor/src/interaction/move_mode.rs:487-495 | editor/src/interaction/rotate_mode.rs:269-277 | editor/src/interaction/scale_mode.rs:244-252 — before extracting anything, compare `editor/src/interaction/rotate_mode.rs` and `editor/src/interaction/scale_mode.rs` as WHOLE FILES: this scan already matched 7 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.
Off the main sequence: fyrox-math — fyrox-math: abstractness 0.26, instability 0.00, distance 0.74 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: fyrox-autotile — fyrox-autotile: abstractness 0.29, instability 0.00, distance 0.71 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
TextBox::handle_routed_message (cyclomatic 99) fyrox-ui/src/text_box.rs:1128— TextBox::handle_routed_message has cyclomatic complexity 99 (threshold 15). Of this number, 96 points are the body's own statements and 3 belong to one function item inside it that branches. 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.
Window::handle_routed_message (cyclomatic 90) fyrox-ui/src/window.rs:393— Window::handle_routed_message has cyclomatic complexity 90 (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.
CurveEditor::handle_routed_message (cyclomatic 80) fyrox-ui/src/curve/mod.rs:574— CurveEditor::handle_routed_message has cyclomatic complexity 80 (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.
AsciiReader::read_field (cyclomatic 59) fyrox-core/src/visitor/reader/ascii.rs:202— AsciiReader::read_field has cyclomatic complexity 59 (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.
SceneViewer::handle_ui_message (cyclomatic 55) editor/src/scene_viewer/mod.rs:692— SceneViewer::handle_ui_message has cyclomatic complexity 55 (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.
AsciiWriter::write_field (cyclomatic 55) fyrox-core/src/visitor/writer/ascii.rs:34— AsciiWriter::write_field has cyclomatic complexity 55 (threshold 15). Of this number, 53 points are the body's own statements and 2 belong to one function item inside it that branches. 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.
TrackValue::apply_to_any (cyclomatic 52) fyrox-animation/src/value.rs:234— TrackValue::apply_to_any has cyclomatic complexity 52 (threshold 15). Of this number, 51 points are the body's own statements and 1 belongs to one function item inside it that branches. 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.
AssetBrowser::handle_ui_message (cyclomatic 48) editor/src/asset/mod.rs:631— AssetBrowser::handle_ui_message has cyclomatic complexity 48 (threshold 15). Of this number, 46 points are the body's own statements and 2 belong to one function item inside it that branches. 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.
AbsmCanvas::handle_routed_message (cyclomatic 45) editor/src/plugins/absm/canvas.rs:416— AbsmCanvas::handle_routed_message has cyclomatic complexity 45 (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.
MenuItem::handle_routed_message (cyclomatic 43) fyrox-ui/src/menu.rs:546— MenuItem::handle_routed_message has cyclomatic complexity 43 (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.
DeferredLightRenderer::render (cyclomatic 40) fyrox-impl/src/renderer/light.rs:254— DeferredLightRenderer::render has cyclomatic complexity 40 (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.
Texture::load_from_memory (cyclomatic 39) fyrox-texture/src/lib.rs:1493— Texture::load_from_memory has cyclomatic complexity 39 (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.
Tree::handle_routed_message (cyclomatic 38) fyrox-ui/src/tree.rs:350— Tree::handle_routed_message has cyclomatic complexity 38 (threshold 15). Of this number, 33 points are the body's own statements and 5 belong to one function item inside it that branches. 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.
NumericUpDown::handle_routed_message (cyclomatic 37) fyrox-ui/src/numeric.rs:403— NumericUpDown::handle_routed_message has cyclomatic complexity 37 (threshold 15). Of this number, 31 points are the body's own statements and 6 belong to one function item inside it that branches. 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.
ScrollViewer::handle_routed_message (cyclomatic 37) fyrox-ui/src/scroll_viewer.rs:236— ScrollViewer::handle_routed_message has cyclomatic complexity 37 (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.
AssetItemContextMenu::handle_ui_message (cyclomatic 36) editor/src/asset/menu.rs:339— AssetItemContextMenu::handle_ui_message has cyclomatic complexity 36 (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.
StateViewer::sync_to_model (cyclomatic 33) editor/src/plugins/absm/state_viewer/mod.rs:410— StateViewer::sync_to_model has cyclomatic complexity 33 (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.
GlShader::new (cyclomatic 33) fyrox-graphics-gl/src/program.rs:153— GlShader::new has cyclomatic complexity 33 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
SceneNodeContextMenu::handle_ui_message (cyclomatic 31) editor/src/world/menu.rs:268— SceneNodeContextMenu::handle_ui_message 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.
Popup::handle_routed_message (cyclomatic 31) fyrox-ui/src/popup.rs:386— Popup::handle_routed_message 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.
Engine::reload_plugin (cyclomatic 30) fyrox-impl/src/engine/mod.rs:2555— Engine::reload_plugin 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.
ScriptProcessor::handle_scripts (cyclomatic 30) fyrox-impl/src/engine/mod.rs:642— ScriptProcessor::handle_scripts 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.
PropertiesTab::handle_ui_message (cyclomatic 28) editor/src/plugins/tilemap/properties_tab.rs:580— PropertiesTab::handle_ui_message has cyclomatic complexity 28 (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.
ColorPicker::handle_routed_message (cyclomatic 28) fyrox-ui/src/color/mod.rs:821— ColorPicker::handle_routed_message 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.
ScrollBar::handle_routed_message (cyclomatic 28) fyrox-ui/src/scroll_bar.rs:221— ScrollBar::handle_routed_message 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.
CurveEditorWindow::handle_ui_message (cyclomatic 27) editor/src/plugins/curve_editor.rs:416— CurveEditorWindow::handle_ui_message 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.
Animation::update_root_motion (cyclomatic 26) fyrox-animation/src/lib.rs:498— Animation::update_root_motion has cyclomatic complexity 26 (threshold 15). Of this number, 24 points are the body's own statements and 2 belong to 2 function items inside it that branch. 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.
FileMenu::handle_ui_message (cyclomatic 25) editor/src/menu/file.rs:363— FileMenu::handle_ui_message has cyclomatic complexity 25 (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.
AbsmEditor::handle_ui_message (cyclomatic 25) editor/src/plugins/absm/mod.rs:585— AbsmEditor::handle_ui_message has cyclomatic complexity 25 (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.
StateGraphViewer::sync_to_model (cyclomatic 25) editor/src/plugins/absm/state_graph/mod.rs:294— StateGraphViewer::sync_to_model has cyclomatic complexity 25 (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.
MaterialEditor::sync_to_model (cyclomatic 25) editor/src/plugins/material/mod.rs:570— MaterialEditor::sync_to_model has cyclomatic complexity 25 (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.
TileSetEditor::handle_ui_message (cyclomatic 25) editor/src/plugins/tilemap/tileset.rs:642— TileSetEditor::handle_ui_message has cyclomatic complexity 25 (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.
Decorator::handle_routed_message (cyclomatic 25) fyrox-ui/src/decorator.rs:157— Decorator::handle_routed_message has cyclomatic complexity 25 (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.
Text::handle_routed_message (cyclomatic 25) fyrox-ui/src/text.rs:420— Text::handle_routed_message has cyclomatic complexity 25 (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.
fyrox_project_manager::main (cyclomatic 25) project-manager/src/main.rs:73— fyrox_project_manager::main has cyclomatic complexity 25 (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.
PropertyAction::apply_on_result (cyclomatic 24) fyrox-ui/src/inspector/mod.rs:296— PropertyAction::apply_on_result 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.
TabControl::handle_routed_message (cyclomatic 24) fyrox-ui/src/tab_control.rs:375— TabControl::handle_routed_message 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.
fyrox_ui::transform_size (cyclomatic 24) fyrox-ui/src/lib.rs:3871— fyrox_ui::transform_size 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.
TileInspector::handle_ui_message (cyclomatic 23) editor/src/plugins/tilemap/tile_inspector.rs:1070— TileInspector::handle_ui_message 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.
GlGraphicsServer::new (cyclomatic 23) fyrox-graphics-gl/src/server.rs:591— GlGraphicsServer::new has cyclomatic complexity 23 (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.
FbxScene::new (cyclomatic 23) fyrox-impl/src/resource/fbx/scene/mod.rs:57— FbxScene::new 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.
Chunk::set_height_map (cyclomatic 23) fyrox-impl/src/scene/terrain/mod.rs:534— Chunk::set_height_map 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.
BlendSpaceField::handle_routed_message (cyclomatic 22) editor/src/plugins/absm/blendspace.rs:317— BlendSpaceField::handle_routed_message 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.
Ruler::handle_routed_message (cyclomatic 22) editor/src/plugins/animation/ruler.rs:290— Ruler::handle_routed_message 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.
RenderDataBundle::render_to_frame_buffer (cyclomatic 22) fyrox-impl/src/renderer/bundle.rs:509— RenderDataBundle::render_to_frame_buffer 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.
MachineLayer::evaluate_pose (cyclomatic 21) fyrox-animation/src/machine/layer.rs:590— MachineLayer::evaluate_pose 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.
Selector::handle_routed_message (cyclomatic 21) fyrox-ui/src/selector.rs:149— Selector::handle_routed_message 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.
RootMotionDropdownArea::handle_ui_message (cyclomatic 20) editor/src/plugins/animation/toolbar.rs:211— RootMotionDropdownArea::handle_ui_message 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.
GameScene::draw_auxiliary_geometry::draw_recursively (cyclomatic 20) editor/src/scene/mod.rs:340— GameScene::draw_auxiliary_geometry::draw_recursively 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.
WidgetContextMenu::handle_ui_message (cyclomatic 20) editor/src/ui_scene/menu.rs:182— WidgetContextMenu::handle_ui_message 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.
Ragdoll::update (cyclomatic 20) fyrox-impl/src/scene/ragdoll.rs:153— Ragdoll::update 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.
LightmapInputData::from_scene (cyclomatic 20) fyrox-impl/src/utils/lightmap.rs:403— LightmapInputData::from_scene 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.
CheckBox::handle_routed_message (cyclomatic 20) fyrox-ui/src/check_box.rs:200— CheckBox::handle_routed_message 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.
AbsmNode::handle_routed_message (cyclomatic 19) editor/src/plugins/absm/node.rs:163— AbsmNode::handle_routed_message 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.
MacroPropertyValueField::on_ui_message (cyclomatic 19) editor/src/plugins/tilemap/brush_macro.rs:811— MacroPropertyValueField::on_ui_message 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.
TileMapEditorPlugin::on_message (cyclomatic 19) editor/src/plugins/tilemap/mod.rs:816— TileMapEditorPlugin::on_message 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.
fyrox_core::variable::try_inherit_properties (cyclomatic 19) fyrox-core/src/variable.rs:613— fyrox_core::variable::try_inherit_properties 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.
GlTexture::set_data (cyclomatic 19) fyrox-graphics-gl/src/texture.rs:397— GlTexture::set_data 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. This is NOT this file's highest cyclomatic complexity: PixelDescriptor::from (cyclomatic 36) 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 function is counted neither in this dimension's figures nor in its score.
RenderDataBundleStorage::from_graph (cyclomatic 19) fyrox-impl/src/renderer/bundle.rs:873— RenderDataBundleStorage::from_graph has cyclomatic complexity 19 (threshold 15). Of this number, 16 points are the body's own statements and 3 belong to one function item inside it that branches. 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. This is NOT this file's highest cyclomatic complexity: fyrox_impl::renderer::bundle::write_shader_values (cyclomatic 21) 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 function is counted neither in this dimension's figures nor in its score.
ListView::handle_routed_message (cyclomatic 19) fyrox-ui/src/list_view.rs:405— ListView::handle_routed_message 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.
fyrox_template_core::upgrade_project (cyclomatic 19) template-core/src/lib.rs:806— fyrox_template_core::upgrade_project 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.
SurfaceDataPropertyEditor::handle_routed_message (cyclomatic 18) editor/src/plugins/inspector/editors/surface.rs:94— SurfaceDataPropertyEditor::handle_routed_message has cyclomatic complexity 18 (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.
InspectorPlugin::on_ui_message (cyclomatic 18) editor/src/plugins/inspector/mod.rs:456— InspectorPlugin::on_ui_message has cyclomatic complexity 18 (threshold 15). Of this number, 17 points are the body's own statements and 1 belongs to one function item inside it that branches. 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.
WfcMacro::on_instance_ui_message (cyclomatic 18) editor/src/plugins/tilemap/wfc.rs:263— WfcMacro::on_instance_ui_message has cyclomatic complexity 18 (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.
Mesh::collect_render_data (cyclomatic 18) fyrox-impl/src/scene/mesh/mod.rs:691— Mesh::collect_render_data has cyclomatic complexity 18 (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.
Button::handle_routed_message (cyclomatic 18) fyrox-ui/src/button.rs:189— Button::handle_routed_message has cyclomatic complexity 18 (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.
HandlePropertyEditor::handle_routed_message (cyclomatic 17) editor/src/plugins/inspector/editors/handle.rs:177— HandlePropertyEditor::handle_routed_message 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.
UiSceneWorldViewerDataProvider::icon_of (cyclomatic 17) editor/src/ui_scene/utils.rs:124— UiSceneWorldViewerDataProvider::icon_of 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.
SceneGraph::restore_integrity (cyclomatic 17) fyrox-graph/src/lib.rs:1197— SceneGraph::restore_integrity 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.
UiRenderer::render (cyclomatic 17) fyrox-impl/src/renderer/ui_renderer.rs:289— UiRenderer::render 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.
TileDataUpdate::swap_with_data (cyclomatic 17) fyrox-impl/src/scene/tilemap/update.rs:287— TileDataUpdate::swap_with_data has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
DockingManager::set_layout (cyclomatic 17) fyrox-ui/src/dock/mod.rs:244— DockingManager::set_layout 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.
MeshControlPanel::handle_ui_message (cyclomatic 16) editor/src/mesh.rs:156— MeshControlPanel::handle_ui_message 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.
SettingsWindow::handle_ui_message (cyclomatic 16) editor/src/plugins/settings.rs:241— SettingsWindow::handle_ui_message 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.
SceneItem::handle_routed_message (cyclomatic 16) editor/src/world/item.rs:170— SceneItem::handle_routed_message 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.
HashConstraintMap::fill_from (cyclomatic 16) fyrox-autotile/src/auto.rs:164— HashConstraintMap::fill_from 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.
GlFrameBuffer::clear (cyclomatic 16) fyrox-graphics-gl/src/framebuffer.rs:307— GlFrameBuffer::clear 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.
Graph::process_node_messages (cyclomatic 16) fyrox-impl/src/scene/graph/mod.rs:1303— Graph::process_node_messages has cyclomatic complexity 16 (threshold 15). Of this number, 14 points are the body's own statements and 2 belong to one function item inside it that branches. 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.
BehaviorTree::tick_recursive (cyclomatic 16) fyrox-impl/src/utils/behavior/mod.rs:175— BehaviorTree::tick_recursive has cyclomatic complexity 16 (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.
fyrox_resource::collect_used_resources (cyclomatic 16) fyrox-resource/src/lib.rs:655— fyrox_resource::collect_used_resources 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.
TodoComment repeated across 16 files editor/src/lib.rs:21— The identical TodoComment appears in 16 files (22 occurrences) — almost certainly one boilerplate line from a single migration or decision, not 22 independent debts. Fix the systemic cause once rather than file-by-file. Text: "// TODO". Source code is not a task system: track the cleanup where tasks live. (Every occurrence still counts toward the score and metrics.)
XxxComment fyrox-material/src/shader/mod.rs:410— //! - **Possible values:** `None`, [Some(CullFace::XXX)](fyrox_graphics::CullFace) — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
Window::handle_routed_message (cognitive 237) fyrox-ui/src/window.rs:393— Window::handle_routed_message has cognitive complexity 237 (threshold 15). Drivers by points: if/else 53 (192 pts), match/switch 7 (23 pts), loops 3 (14 pts), boolean chains 8 (nesting depth added 166). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
Tree::handle_routed_message (cognitive 140) fyrox-ui/src/tree.rs:350— Tree::handle_routed_message has cognitive complexity 140 (threshold 15). Drivers by points: if/else 28 (108 pts), loops 4 (21 pts), match/switch 3 (10 pts), boolean chains 1 (nesting depth added 104). Of this number, 100 points are the body's own statements and 40 belong to one function item inside it that branches. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
AssetItemContextMenu::handle_ui_message (cognitive 137) editor/src/asset/menu.rs:339— AssetItemContextMenu::handle_ui_message has cognitive complexity 137 (threshold 15). Drivers by points: if/else 34 (129 pts), match/switch 1 (8 pts) (nesting depth added 102). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
ScriptProcessor::handle_scripts (cognitive 103) fyrox-impl/src/engine/mod.rs:642— ScriptProcessor::handle_scripts has cognitive complexity 103 (threshold 15). Drivers by points: if/else 21 (65 pts), loops 11 (31 pts), match/switch 1 (5 pts), boolean chains 2 (nesting depth added 68). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
Animation::update_root_motion (cognitive 98) fyrox-animation/src/lib.rs:498— Animation::update_root_motion has cognitive complexity 98 (threshold 15). Drivers by points: if/else 30 (87 pts), boolean chains 4, match/switch 1 (4 pts), loops 1 (3 pts) (nesting depth added 62). Of this number, 94 points are the body's own statements and 4 belong to 2 function items inside it that branch. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
fyrox_template_core::upgrade_project (cognitive 98) template-core/src/lib.rs:806— fyrox_template_core::upgrade_project has cognitive complexity 98 (threshold 15). Drivers by points: if/else 19 (96 pts), boolean chains 1, match/switch 1 (nesting depth added 77). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
SceneNodeContextMenu::handle_ui_message (cognitive 88) editor/src/world/menu.rs:268— SceneNodeContextMenu::handle_ui_message has cognitive complexity 88 (threshold 15). Drivers by points: if/else 29 (82 pts), loops 1 (5 pts), boolean chains 1 (nesting depth added 57). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
UiRenderer::render (cognitive 80) fyrox-impl/src/renderer/ui_renderer.rs:289— UiRenderer::render has cognitive complexity 80 (threshold 15). Drivers by points: if/else 11 (65 pts), match/switch 2 (10 pts), loops 2 (4 pts), boolean chains 1 (nesting depth added 64). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
ScrollBar::handle_routed_message (cognitive 76) fyrox-ui/src/scroll_bar.rs:221— ScrollBar::handle_routed_message has cognitive complexity 76 (threshold 15). Drivers by points: if/else 21 (63 pts), match/switch 4 (13 pts) (nesting depth added 51). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
AbsmEditor::handle_ui_message (cognitive 71) editor/src/plugins/absm/mod.rs:585— AbsmEditor::handle_ui_message has cognitive complexity 71 (threshold 15). Drivers by points: if/else 16 (51 pts), match/switch 3 (11 pts), loops 2 (9 pts) (nesting depth added 50). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
ScrollViewer::handle_routed_message (cognitive 70) fyrox-ui/src/scroll_viewer.rs:236— ScrollViewer::handle_routed_message has cognitive complexity 70 (threshold 15). Drivers by points: if/else 20 (51 pts), match/switch 3 (9 pts), boolean chains 6, loops 1 (4 pts) (nesting depth added 40). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
PropertyAction::apply_on_result (cognitive 67) fyrox-ui/src/inspector/mod.rs:296— PropertyAction::apply_on_result has cognitive complexity 67 (threshold 15). Drivers by points: if/else 32 (62 pts), match/switch 2 (5 pts) (nesting depth added 33). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
DeferredLightRenderer::render (cognitive 66) fyrox-impl/src/renderer/light.rs:254— DeferredLightRenderer::render has cognitive complexity 66 (threshold 15). Drivers by points: if/else 25 (46 pts), boolean chains 9, match/switch 3 (8 pts), loops 2 (3 pts) (nesting depth added 27). 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.
NumericUpDown::handle_routed_message (cognitive 60) fyrox-ui/src/numeric.rs:403— NumericUpDown::handle_routed_message has cognitive complexity 60 (threshold 15). Drivers by points: if/else 19 (41 pts), match/switch 4 (11 pts), boolean chains 8 (nesting depth added 29). Of this number, 51 points are the body's own statements and 9 belong to one function item inside it that branches. 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.
Ruler::handle_routed_message (cognitive 56) editor/src/plugins/animation/ruler.rs:290— Ruler::handle_routed_message has cognitive complexity 56 (threshold 15). Drivers by points: if/else 11 (41 pts), match/switch 3 (10 pts), loops 1 (4 pts), boolean chains 1 (nesting depth added 40). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
WidgetContextMenu::handle_ui_message (cognitive 56) editor/src/ui_scene/menu.rs:182— WidgetContextMenu::handle_ui_message has cognitive complexity 56 (threshold 15). Drivers by points: if/else 19 (56 pts) (nesting depth added 37). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
GlTexture::set_data (cognitive 51) fyrox-graphics-gl/src/texture.rs:397— GlTexture::set_data has cognitive complexity 51 (threshold 15). Drivers by points: if/else 21 (44 pts), loops 2 (5 pts), match/switch 1 (2 pts) (nesting depth added 27). 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.
Selector::handle_routed_message (cognitive 51) fyrox-ui/src/selector.rs:149— Selector::handle_routed_message has cognitive complexity 51 (threshold 15). Drivers by points: if/else 13 (38 pts), loops 3 (10 pts), match/switch 1 (2 pts), boolean chains 1 (nesting depth added 33). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
fyrox_core::variable::try_inherit_properties (cognitive 49) fyrox-core/src/variable.rs:613— fyrox_core::variable::try_inherit_properties has cognitive complexity 49 (threshold 15). Drivers by points: if/else 15 (41 pts), loops 2 (7 pts), boolean chains 1 (nesting depth added 31). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
CurveEditorWindow::handle_ui_message (cognitive 48) editor/src/plugins/curve_editor.rs:416— CurveEditorWindow::handle_ui_message has cognitive complexity 48 (threshold 15). Drivers by points: if/else 27 (44 pts), boolean chains 2, match/switch 1 (2 pts) (nesting depth added 18). 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.
Decorator::handle_routed_message (cognitive 48) fyrox-ui/src/decorator.rs:157— Decorator::handle_routed_message has cognitive complexity 48 (threshold 15). Drivers by points: if/else 17 (41 pts), match/switch 2 (5 pts), boolean chains 2 (nesting depth added 27). 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.
ListView::handle_routed_message (cognitive 48) fyrox-ui/src/list_view.rs:405— ListView::handle_routed_message has cognitive complexity 48 (threshold 15). Drivers by points: if/else 15 (38 pts), match/switch 3 (10 pts) (nesting depth added 30). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
FileMenu::handle_ui_message (cognitive 47) editor/src/menu/file.rs:363— FileMenu::handle_ui_message has cognitive complexity 47 (threshold 15). Drivers by points: if/else 27 (47 pts) (nesting depth added 20). 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.
TabControl::handle_routed_message (cognitive 47) fyrox-ui/src/tab_control.rs:375— TabControl::handle_routed_message has cognitive complexity 47 (threshold 15). Drivers by points: if/else 14 (35 pts), loops 2 (5 pts), match/switch 2 (5 pts), boolean chains 2 (nesting depth added 27). 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.
fyrox_project_manager::main (cognitive 47) project-manager/src/main.rs:73— fyrox_project_manager::main has cognitive complexity 47 (threshold 15). Drivers by points: if/else 14 (37 pts), loops 2 (7 pts), match/switch 2 (3 pts) (nesting depth added 29). 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.
SurfaceDataPropertyEditor::handle_routed_message (cognitive 46) editor/src/plugins/inspector/editors/surface.rs:94— SurfaceDataPropertyEditor::handle_routed_message has cognitive complexity 46 (threshold 15). Drivers by points: if/else 17 (44 pts), loops 1 (2 pts) (nesting depth added 28). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
Text::handle_routed_message (cognitive 46) fyrox-ui/src/text.rs:420— Text::handle_routed_message has cognitive complexity 46 (threshold 15). Drivers by points: if/else 13 (43 pts), match/switch 1 (3 pts) (nesting depth added 32). 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.
RenderDataBundleStorage::from_graph (cognitive 45) fyrox-impl/src/renderer/bundle.rs:873— RenderDataBundleStorage::from_graph has cognitive complexity 45 (threshold 15). Drivers by points: if/else 13 (32 pts), loops 4 (11 pts), boolean chains 2 (nesting depth added 26). Of this number, 39 points are the body's own statements and 6 belong to one function item inside it that branches. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
BlendSpaceField::handle_routed_message (cognitive 44) editor/src/plugins/absm/blendspace.rs:317— BlendSpaceField::handle_routed_message has cognitive complexity 44 (threshold 15). Drivers by points: if/else 10 (27 pts), match/switch 3 (9 pts), loops 2 (8 pts) (nesting depth added 29). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
ScriptMessageDispatcher::dispatch_messages (cognitive 44) fyrox-impl/src/engine/mod.rs:443— ScriptMessageDispatcher::dispatch_messages has cognitive complexity 44 (threshold 15). Drivers by points: if/else 5 (20 pts), loops 4 (15 pts), match/switch 3 (9 pts) (nesting depth added 32). 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.
fyrox_math::triangulator::triangulate (cognitive 44) fyrox-math/src/triangulator.rs:117— fyrox_math::triangulator::triangulate has cognitive complexity 44 (threshold 15). Drivers by points: if/else 15 (39 pts), loops 2 (5 pts) (nesting depth added 27). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
DockingManager::set_layout (cognitive 44) fyrox-ui/src/dock/mod.rs:244— DockingManager::set_layout has cognitive complexity 44 (threshold 15). Drivers by points: if/else 10 (30 pts), loops 3 (9 pts), match/switch 1 (4 pts), boolean chains 1 (nesting depth added 29). 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.
RootMotionDropdownArea::handle_ui_message (cognitive 43) editor/src/plugins/animation/toolbar.rs:211— RootMotionDropdownArea::handle_ui_message has cognitive complexity 43 (threshold 15). Drivers by points: if/else 20 (43 pts) (nesting depth added 23). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
ColorPicker::handle_routed_message (cognitive 43) fyrox-ui/src/color/mod.rs:821— ColorPicker::handle_routed_message has cognitive complexity 43 (threshold 15). Drivers by points: if/else 19 (32 pts), match/switch 2 (6 pts), boolean chains 5 (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.
EditorSceneWrapper::on_change_hierarchy_request (cognitive 40) editor/src/world/graph.rs:166— EditorSceneWrapper::on_change_hierarchy_request has cognitive complexity 40 (threshold 15). Drivers by points: if/else 7 (29 pts), loops 2 (7 pts), match/switch 1 (4 pts) (nesting depth added 30). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
Ragdoll::update (cognitive 40) fyrox-impl/src/scene/ragdoll.rs:153— Ragdoll::update has cognitive complexity 40 (threshold 15). Drivers by points: if/else 17 (33 pts), loops 2 (6 pts), boolean chains 1 (nesting depth added 20). 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.
Texture::load_from_memory (cognitive 40) fyrox-texture/src/lib.rs:1493— Texture::load_from_memory has cognitive complexity 40 (threshold 15). Drivers by points: if/else 15 (26 pts), match/switch 3 (7 pts), loops 2 (6 pts), boolean chains 1 (nesting depth added 19). 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.
TileInspector::handle_ui_message (cognitive 38) editor/src/plugins/tilemap/tile_inspector.rs:1070— TileInspector::handle_ui_message has cognitive complexity 38 (threshold 15). Drivers by points: if/else 22 (34 pts), loops 2 (4 pts) (nesting depth added 14). 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.
HashConstraintMap::fill_from (cognitive 38) fyrox-autotile/src/auto.rs:164— HashConstraintMap::fill_from has cognitive complexity 38 (threshold 15). Drivers by points: if/else 7 (25 pts), loops 6 (11 pts), boolean chains 2 (nesting depth added 23). 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.
NavigationLayer::handle_routed_message (cognitive 38) fyrox-ui/src/navigation.rs:98— NavigationLayer::handle_routed_message has cognitive complexity 38 (threshold 15). Drivers by points: if/else 10 (32 pts), loops 2 (5 pts), boolean chains 1 (nesting depth added 25). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
GlShader::new (cognitive 36) fyrox-graphics-gl/src/program.rs:153— GlShader::new has cognitive complexity 36 (threshold 15). Drivers by points: if/else 9 (22 pts), loops 4 (7 pts), match/switch 2 (6 pts), boolean chains 1 (nesting depth added 20). 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.
WgpuTexture::upload (cognitive 36) fyrox-graphics-wgpu/src/texture.rs:290— WgpuTexture::upload has cognitive complexity 36 (threshold 15). Drivers by points: if/else 8 (29 pts), loops 2 (5 pts), match/switch 1 (2 pts) (nesting depth added 25). 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.
TileSetPropertyOptionValue::intersect (cognitive 36) fyrox-impl/src/scene/tilemap/property.rs:696— TileSetPropertyOptionValue::intersect has cognitive complexity 36 (threshold 15). Drivers by points: if/else 12 (32 pts), loops 1 (3 pts), match/switch 1 (nesting depth added 22). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
ScriptPropertyEditor::preview_message (cognitive 35) editor/src/plugins/inspector/editors/script.rs:120— ScriptPropertyEditor::preview_message has cognitive complexity 35 (threshold 15). Drivers by points: if/else 9 (29 pts), match/switch 1 (6 pts) (nesting depth added 25). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
RenderDataBundle::render_to_frame_buffer (cognitive 35) fyrox-impl/src/renderer/bundle.rs:509— RenderDataBundle::render_to_frame_buffer has cognitive complexity 35 (threshold 15). Drivers by points: if/else 9 (18 pts), match/switch 5 (13 pts), loops 3 (4 pts) (nesting depth added 18). 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.
LightmapInputData::from_scene (cognitive 35) fyrox-impl/src/utils/lightmap.rs:403— LightmapInputData::from_scene has cognitive complexity 35 (threshold 15). Drivers by points: if/else 13 (26 pts), loops 4 (6 pts), boolean chains 3 (nesting depth added 15). 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.
InspectorPlugin::on_ui_message (cognitive 34) editor/src/plugins/inspector/mod.rs:456— InspectorPlugin::on_ui_message has cognitive complexity 34 (threshold 15). Drivers by points: if/else 10 (21 pts), match/switch 3 (11 pts), boolean chains 2 (nesting depth added 19). Of this number, 33 points are the body's own statements and 1 belongs to one function item inside it that branches. 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.
TileMapEditorPlugin::on_message (cognitive 34) editor/src/plugins/tilemap/mod.rs:816— TileMapEditorPlugin::on_message has cognitive complexity 34 (threshold 15). Drivers by points: if/else 20 (33 pts), boolean chains 1 (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.
PropertiesTab::handle_ui_message (cognitive 34) editor/src/plugins/tilemap/properties_tab.rs:580— PropertiesTab::handle_ui_message has cognitive complexity 34 (threshold 15). Drivers by points: if/else 27 (34 pts) (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.
TileSetEditor::handle_ui_message (cognitive 33) editor/src/plugins/tilemap/tileset.rs:642— TileSetEditor::handle_ui_message has cognitive complexity 33 (threshold 15). Drivers by points: if/else 21 (30 pts), boolean chains 3 (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.
TileSet::rebuild_animations (cognitive 33) fyrox-impl/src/scene/tilemap/tileset.rs:1548— TileSet::rebuild_animations has cognitive complexity 33 (threshold 15). Drivers by points: if/else 7 (20 pts), loops 5 (9 pts), match/switch 1 (3 pts), boolean chains 1 (nesting depth added 19). 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.
SaturationBrightnessField::handle_routed_message (cognitive 33) fyrox-ui/src/color/mod.rs:641— SaturationBrightnessField::handle_routed_message has cognitive complexity 33 (threshold 15). Drivers by points: if/else 8 (25 pts), match/switch 2 (8 pts) (nesting depth added 23). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
MeshControlPanel::handle_ui_message (cognitive 32) editor/src/mesh.rs:156— MeshControlPanel::handle_ui_message has cognitive complexity 32 (threshold 15). Drivers by points: if/else 10 (17 pts), loops 5 (15 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.
HandlePropertyEditor::handle_routed_message (cognitive 31) editor/src/plugins/inspector/editors/handle.rs:177— HandlePropertyEditor::handle_routed_message has cognitive complexity 31 (threshold 15). Drivers by points: if/else 19 (29 pts), match/switch 1 (2 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.
Chunk::set_height_map (cognitive 31) fyrox-impl/src/scene/terrain/mod.rs:534— Chunk::set_height_map has cognitive complexity 31 (threshold 15). Drivers by points: if/else 10 (25 pts), match/switch 1 (5 pts), boolean chains 1 (nesting depth added 19). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
MaterialEditor::handle_ui_message (cognitive 30) editor/src/plugins/material/mod.rs:625— MaterialEditor::handle_ui_message has cognitive complexity 30 (threshold 15). Drivers by points: if/else 7 (22 pts), loops 2 (4 pts), boolean chains 2, match/switch 1 (2 pts) (nesting depth added 18). 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.
SceneItem::handle_routed_message (cognitive 30) editor/src/world/item.rs:170— SceneItem::handle_routed_message has cognitive complexity 30 (threshold 15). Drivers by points: if/else 13 (25 pts), match/switch 2 (5 pts) (nesting depth added 15). 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.
CheckBox::handle_routed_message (cognitive 30) fyrox-ui/src/check_box.rs:200— CheckBox::handle_routed_message has cognitive complexity 30 (threshold 15). Drivers by points: if/else 11 (20 pts), boolean chains 5, match/switch 2 (5 pts) (nesting depth added 12). 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.
BlendSpaceEditor::handle_ui_message (cognitive 29) editor/src/plugins/absm/blendspace.rs:876— BlendSpaceEditor::handle_ui_message has cognitive complexity 29 (threshold 15). Drivers by points: if/else 6 (22 pts), match/switch 1 (6 pts), boolean chains 1 (nesting depth added 21). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
GlGraphicsServer::new (cognitive 29) fyrox-graphics-gl/src/server.rs:591— GlGraphicsServer::new has cognitive complexity 29 (threshold 15). Drivers by points: if/else 24 (27 pts), boolean chains 2 (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.
SkyBox::validate (cognitive 29) fyrox-impl/src/scene/skybox.rs:108— SkyBox::validate has cognitive complexity 29 (threshold 15). Drivers by points: if/else 8 (27 pts), boolean chains 1, loops 1 (nesting depth added 19). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
AlphaBar::handle_routed_message (cognitive 29) fyrox-ui/src/color/mod.rs:304— AlphaBar::handle_routed_message has cognitive complexity 29 (threshold 15). Drivers by points: if/else 7 (20 pts), match/switch 2 (8 pts), boolean chains 1 (nesting depth added 19). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
SettingsWindow::handle_ui_message (cognitive 28) editor/src/plugins/settings.rs:241— SettingsWindow::handle_ui_message has cognitive complexity 28 (threshold 15). Drivers by points: if/else 16 (28 pts) (nesting depth added 12). 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.
MacroInspector::handle_ui_message (cognitive 28) editor/src/plugins/tilemap/macro_inspector.rs:375— MacroInspector::handle_ui_message has cognitive complexity 28 (threshold 15). Drivers by points: if/else 9 (25 pts), loops 2 (3 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.
ColorGradientEditor::preview_message (cognitive 28) fyrox-ui/src/color/gradient.rs:243— ColorGradientEditor::preview_message has cognitive complexity 28 (threshold 15). Drivers by points: if/else 11 (22 pts), boolean chains 3, loops 1 (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.
HueBar::handle_routed_message (cognitive 28) fyrox-ui/src/color/mod.rs:465— HueBar::handle_routed_message has cognitive complexity 28 (threshold 15). Drivers by points: if/else 7 (20 pts), match/switch 2 (8 pts) (nesting depth added 19). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
LightPanel::handle_ui_message (cognitive 27) editor/src/light.rs:330— LightPanel::handle_ui_message has cognitive complexity 27 (threshold 15). Drivers by points: if/else 10 (23 pts), match/switch 1 (4 pts) (nesting depth added 16). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
ResourceField::handle_routed_message (cognitive 27) editor/src/plugins/inspector/editors/resource.rs:205— ResourceField::handle_routed_message has cognitive complexity 27 (threshold 15). Drivers by points: if/else 11 (24 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 14). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
MacroPropertyValueField::on_ui_message (cognitive 27) editor/src/plugins/tilemap/brush_macro.rs:811— MacroPropertyValueField::on_ui_message has cognitive complexity 27 (threshold 15). Drivers by points: if/else 11 (18 pts), boolean chains 5, match/switch 1 (4 pts) (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.
FsTree::new (cognitive 27) fyrox-ui/src/file_browser/fs_tree.rs:431— FsTree::new has cognitive complexity 27 (threshold 15). Drivers by points: if/else 8 (22 pts), loops 2 (4 pts), boolean chains 1 (nesting depth added 16). 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.
ParticleSystem::tick (cognitive 26) fyrox-impl/src/scene/particle_system/mod.rs:406— ParticleSystem::tick has cognitive complexity 26 (threshold 15). Drivers by points: if/else 8 (21 pts), loops 4 (5 pts) (nesting depth added 14). 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.
BehaviorTree::tick_recursive (cognitive 26) fyrox-impl/src/utils/behavior/mod.rs:175— BehaviorTree::tick_recursive has cognitive complexity 26 (threshold 15). Drivers by points: match/switch 5 (13 pts), if/else 4 (7 pts), loops 2 (6 pts) (nesting depth added 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. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
ParticleSystemPreviewControlPanel::handle_ui_message (cognitive 25) editor/src/particle.rs:300— ParticleSystemPreviewControlPanel::handle_ui_message has cognitive complexity 25 (threshold 15). Drivers by points: if/else 12 (22 pts), loops 1 (3 pts) (nesting depth added 12). 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.
AbsmNode::handle_routed_message (cognitive 25) editor/src/plugins/absm/node.rs:163— AbsmNode::handle_routed_message has cognitive complexity 25 (threshold 15). Drivers by points: if/else 11 (16 pts), loops 2 (6 pts), match/switch 1 (2 pts), boolean chains 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.
NodeWrapper::revert_inheritable_property (cognitive 25) fyrox-graph/src/lib.rs:538— NodeWrapper::revert_inheritable_property has cognitive complexity 25 (threshold 15). Drivers by points: if/else 7 (17 pts), match/switch 3 (8 pts) (nesting depth added 15). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
TileDataUpdate::swap_with_data (cognitive 25) fyrox-impl/src/scene/tilemap/update.rs:287— TileDataUpdate::swap_with_data has cognitive complexity 25 (threshold 15). Drivers by points: if/else 4 (13 pts), loops 2 (6 pts), match/switch 3 (6 pts) (nesting depth added 16). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
NavmeshAgent::straighten_path (cognitive 25) fyrox-impl/src/utils/navmesh.rs:774— NavmeshAgent::straighten_path has cognitive complexity 25 (threshold 15). Drivers by points: if/else 7 (19 pts), loops 2 (5 pts), boolean chains 1 (nesting depth added 15). 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.
ResourceCreator::handle_ui_message (cognitive 24) editor/src/asset/creator.rs:177— ResourceCreator::handle_ui_message has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (19 pts), match/switch 1 (4 pts), boolean chains 1 (nesting depth added 13). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
AssetItem::open (cognitive 24) editor/src/asset/item.rs:143— AssetItem::open has cognitive complexity 24 (threshold 15). Drivers by points: if/else 12 (17 pts), match/switch 2 (6 pts), boolean chains 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.
SoundPreview::generate_preview (cognitive 24) editor/src/asset/preview/mod.rs:249— SoundPreview::generate_preview has cognitive complexity 24 (threshold 15). Drivers by points: loops 4 (13 pts), if/else 4 (11 pts) (nesting depth added 16). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
NodeContextMenu::handle_ui_message (cognitive 24) editor/src/plugins/absm/state_graph/context.rs:256— NodeContextMenu::handle_ui_message has cognitive complexity 24 (threshold 15). Drivers by points: if/else 13 (23 pts), boolean chains 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.
RenderPassContainer::run_pass (cognitive 24) fyrox-impl/src/renderer/cache/shader.rs:258— RenderPassContainer::run_pass has cognitive complexity 24 (threshold 15). Drivers by points: if/else 12 (21 pts), match/switch 1 (2 pts), loops 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.
AnimationSource::retarget_animations_directly (cognitive 24) fyrox-impl/src/resource/model/mod.rs:229— AnimationSource::retarget_animations_directly has cognitive complexity 24 (threshold 15). Drivers by points: if/else 3 (11 pts), loops 3 (8 pts), match/switch 1 (5 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.
ColorPoint::handle_routed_message (cognitive 24) fyrox-ui/src/color/gradient.rs:515— ColorPoint::handle_routed_message has cognitive complexity 24 (threshold 15). Drivers by points: if/else 6 (16 pts), match/switch 2 (8 pts) (nesting depth added 16). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
SpriteSheetFramesEditorWindow::handle_routed_message (cognitive 23) editor/src/plugins/inspector/editors/spritesheet/window.rs:121— SpriteSheetFramesEditorWindow::handle_routed_message has cognitive complexity 23 (threshold 15). Drivers by points: if/else 13 (22 pts), boolean chains 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.
TileMapPanel::handle_ui_message (cognitive 23) editor/src/plugins/tilemap/panel.rs:618— TileMapPanel::handle_ui_message has cognitive complexity 23 (threshold 15). Drivers by points: if/else 12 (22 pts), boolean chains 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.
SceneState::try_create_from_plugin (cognitive 23) fyrox-impl/src/engine/hotreload.rs:99— SceneState::try_create_from_plugin has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (18 pts), loops 2 (4 pts), boolean chains 1 (nesting depth added 12). 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.
RangeEditor::handle_routed_message (cognitive 23) fyrox-ui/src/range.rs:170— RangeEditor::handle_routed_message has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (21 pts), boolean chains 2 (nesting depth added 11). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
VecEditor::handle_routed_message (cognitive 23) fyrox-ui/src/vec.rs:177— VecEditor::handle_routed_message has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (17 pts), loops 2 (6 pts) (nesting depth added 14). 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.
AutoTiler::is_pattern_legal (cognitive 22) fyrox-autotile/src/auto.rs:382— AutoTiler::is_pattern_legal has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (18 pts), boolean chains 2, loops 2 (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.
GraphTraverseIteratorRef::next (cognitive 22) fyrox-graph/src/lib.rs:1514— GraphTraverseIteratorRef::next has cognitive complexity 22 (threshold 15). Drivers by points: if/else 4 (15 pts), loops 1 (4 pts), match/switch 2 (3 pts) (nesting depth added 15). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident. This shape REPEATS in the file: one other method here (GraphTraverseIteratorMut::next) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
GraphTraverseIteratorMut::next (cognitive 22) fyrox-graph/src/lib.rs:1576— GraphTraverseIteratorMut::next has cognitive complexity 22 (threshold 15). Drivers by points: if/else 4 (15 pts), loops 1 (4 pts), match/switch 2 (3 pts) (nesting depth added 15). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident. This shape REPEATS in the file: one other method here (GraphTraverseIteratorRef::next) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
GlFrameBuffer::clear (cognitive 22) fyrox-graphics-gl/src/framebuffer.rs:307— GlFrameBuffer::clear has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (12 pts), match/switch 3 (8 pts), loops 1 (2 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.
ColorGradingLut::new (cognitive 22) fyrox-impl/src/scene/camera.rs:928— ColorGradingLut::new has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 3 (9 pts), boolean chains 1, match/switch 1 (nesting depth added 11). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
UpgradeTool::handle_ui_message (cognitive 22) project-manager/src/upgrade.rs:200— UpgradeTool::handle_ui_message has cognitive complexity 22 (threshold 15). Drivers by points: if/else 11 (19 pts), match/switch 1 (3 pts) (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.
CommandStack::do_command (cognitive 21) editor/src/command/mod.rs:232— CommandStack::do_command has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (17 pts), loops 1 (2 pts), match/switch 1 (2 pts) (nesting depth added 11). Of this number, 16 points are the body's own statements and 5 belong to one function item inside it that branches. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
FbxScene::new (cognitive 21) fyrox-impl/src/resource/fbx/scene/mod.rs:57— FbxScene::new has cognitive complexity 21 (threshold 15). Drivers by points: match/switch 4 (10 pts), if/else 4 (8 pts), loops 2, boolean chains 1 (nesting depth added 10). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
fyrox_resource::collect_used_resources (cognitive 21) fyrox-resource/src/lib.rs:655— fyrox_resource::collect_used_resources has cognitive complexity 21 (threshold 15). Drivers by points: if/else 11 (15 pts), loops 3 (5 pts), boolean chains 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.
Button::handle_routed_message (cognitive 21) fyrox-ui/src/button.rs:189— Button::handle_routed_message has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (13 pts), match/switch 2 (5 pts), boolean chains 3 (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.
EditMenu::handle_ui_message (cognitive 20) editor/src/menu/edit.rs:116— EditMenu::handle_ui_message has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (20 pts) (nesting depth added 11). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
MaterialFieldEditor::handle_routed_message (cognitive 20) editor/src/plugins/material/editor.rs:129— MaterialFieldEditor::handle_routed_message has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11 (18 pts), loops 1 (2 pts) (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.
TileHandleField::handle_routed_message (cognitive 20) editor/src/plugins/tilemap/handle_field.rs:84— TileHandleField::handle_routed_message has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (20 pts) (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.
UiSelectInteractionMode::on_left_mouse_button_up (cognitive 20) editor/src/ui_scene/interaction/mod.rs:93— UiSelectInteractionMode::on_left_mouse_button_up has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (17 pts), loops 1 (2 pts), boolean chains 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.
Sprite::collect_render_data (cognitive 20) fyrox-impl/src/scene/sprite.rs:322— Sprite::collect_render_data has cognitive complexity 20 (threshold 15). Drivers by points: if/else 18, boolean chains 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.
TileMap::collect_render_data (cognitive 20) fyrox-impl/src/scene/tilemap/mod.rs:1417— TileMap::collect_render_data has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (13 pts), loops 4 (6 pts), boolean chains 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.
HashMapPropertyEditorDefinition::create_message (cognitive 20) fyrox-ui/src/inspector/editors/hashmap/mod.rs:336— HashMapPropertyEditorDefinition::create_message has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (18 pts), loops 1 (2 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.
TextureSliceEditorWindow::handle_routed_message (cognitive 20) fyrox-ui/src/inspector/editors/texture_slice.rs:529— TextureSliceEditorWindow::handle_routed_message has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (16 pts), loops 1 (3 pts), boolean chains 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.
Configurator::handle_ui_message (cognitive 19) editor/src/configurator.rs:277— Configurator::handle_ui_message has cognitive complexity 19 (threshold 15). Drivers by points: if/else 11 (19 pts) (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.
ColliderControlPanel::handle_ui_message (cognitive 19) editor/src/plugins/collider/panel.rs:124— ColliderControlPanel::handle_ui_message has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (14 pts), match/switch 1 (3 pts), loops 1 (2 pts) (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.
MacroTab::handle_ui_message (cognitive 19) editor/src/plugins/tilemap/macro_tab.rs:386— MacroTab::handle_ui_message has cognitive complexity 19 (threshold 15). Drivers by points: if/else 13 (19 pts) (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.
TileBoundsEditor::handle_routed_message (cognitive 19) editor/src/plugins/tilemap/tile_bounds_editor.rs:138— TileBoundsEditor::handle_routed_message has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (16 pts), loops 1 (3 pts) (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.
fyrox_graphics_gl::texture::desired_byte_count (cognitive 19) fyrox-graphics-gl/src/texture.rs:346— fyrox_graphics_gl::texture::desired_byte_count has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (16 pts), match/switch 1 (2 pts), loops 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.
ObserversCollection::from_scene (cognitive 19) fyrox-impl/src/renderer/observer.rs:88— ObserversCollection::from_scene has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (14 pts), loops 2 (5 pts) (nesting depth added 12). 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.
Rectangle::collect_render_data (cognitive 19) fyrox-impl/src/scene/dim2/rectangle.rs:323— Rectangle::collect_render_data has cognitive complexity 19 (threshold 15). Drivers by points: if/else 18, 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.
ResourceRegistry::scan (cognitive 19) fyrox-resource/src/registry.rs:419— ResourceRegistry::scan has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (14 pts), match/switch 2 (4 pts), loops 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.
DropdownList::handle_routed_message (cognitive 19) fyrox-ui/src/dropdown_list.rs:218— DropdownList::handle_routed_message has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (13 pts), match/switch 2 (4 pts), boolean chains 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.
ListViewBuilder::build (cognitive 19) fyrox-ui/src/list_view.rs:558— ListViewBuilder::build has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (14 pts), loops 3 (5 pts) (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.
ExportWindow::handle_ui_message (cognitive 18) editor/src/export/mod.rs:367— ExportWindow::handle_ui_message has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (12 pts), match/switch 2 (6 pts) (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.
NodeSelectorWindow::handle_routed_message (cognitive 18) editor/src/scene/selector.rs:465— NodeSelectorWindow::handle_routed_message has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 3 (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.
WgpuGeometryBuffer::new (cognitive 18) fyrox-graphics-wgpu/src/geometry_buffer.rs:77— WgpuGeometryBuffer::new has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (14 pts), loops 2 (3 pts), 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.
PluginContext::load_scene (cognitive 18) fyrox-impl/src/plugin/mod.rs:341— PluginContext::load_scene has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (13 pts), loops 1 (3 pts), match/switch 2 (nesting depth added 10). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
CollectionEditor::handle_routed_message (cognitive 18) fyrox-ui/src/inspector/editors/collection.rs:119— CollectionEditor::handle_routed_message has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (10 pts), loops 2 (8 pts) (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.
MatrixEditor::handle_routed_message (cognitive 18) fyrox-ui/src/matrix.rs:141— MatrixEditor::handle_routed_message has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (13 pts), loops 2 (5 pts) (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.
WrapPanel::arrange_override (cognitive 18) fyrox-ui/src/wrap_panel.rs:175— WrapPanel::arrange_override has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (8 pts), match/switch 3 (6 pts), loops 3 (4 pts) (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.
ScaleInteractionMode::on_left_mouse_button_up (cognitive 17) editor/src/interaction/scale_mode.rs:105— ScaleInteractionMode::on_left_mouse_button_up has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (17 pts) (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.
TextureEditor::handle_routed_message (cognitive 17) editor/src/plugins/inspector/editors/texture.rs:114— TextureEditor::handle_routed_message has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (17 pts) (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.
TilePropertyEditor::handle_ui_message (cognitive 17) editor/src/plugins/tilemap/tile_prop_editor.rs:575— TilePropertyEditor::handle_ui_message has cognitive complexity 17 (threshold 15). Drivers by points: if/else 12 (17 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.
SpriteSheetAnimation::update (cognitive 17) fyrox-animation/src/spritesheet/mod.rs:415— SpriteSheetAnimation::update has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 4, loops 1 (nesting depth added 3). 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.
AsciiReader::read_field (cognitive 17) fyrox-core/src/visitor/reader/ascii.rs:202— AsciiReader::read_field has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 2, loops 1 (2 pts), match/switch 1 (nesting depth added 6). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
WgpuShader::new (cognitive 17) fyrox-graphics-wgpu/src/program.rs:249— WgpuShader::new has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (14 pts), loops 2 (3 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.
OcclusionTester::try_query_visibility_results (cognitive 17) fyrox-impl/src/renderer/occlusion/mod.rs:173— OcclusionTester::try_query_visibility_results has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (9 pts), loops 5 (8 pts) (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.
TileMapBrush::palette_render_loop (cognitive 17) fyrox-impl/src/scene/tilemap/brush.rs:418— TileMapBrush::palette_render_loop has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (12 pts), loops 2 (4 pts), match/switch 1 (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.
ItemContextMenu::preview_message (cognitive 17) fyrox-ui/src/file_browser/menu.rs:141— ItemContextMenu::preview_message has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (17 pts) (nesting depth added 9). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
FileBrowser::handle_routed_message (cognitive 17) fyrox-ui/src/file_browser/mod.rs:549— FileBrowser::handle_routed_message has cognitive complexity 17 (threshold 15). Drivers by points: if/else 13 (16 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, 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.
TextureSliceEditor::on_thumb_dragged (cognitive 17) fyrox-ui/src/inspector/editors/texture_slice.rs:124— TextureSliceEditor::on_thumb_dragged has cognitive complexity 17 (threshold 15). Drivers by points: if/else 13 (17 pts) (nesting depth added 4). 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.
MessageBox::handle_routed_message (cognitive 17) fyrox-ui/src/messagebox.rs:220— MessageBox::handle_routed_message has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (12 pts), match/switch 2 (5 pts) (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.
SetPropertyCommand::swap (cognitive 16) editor/src/command/mod.rs:608— SetPropertyCommand::swap has cognitive complexity 16 (threshold 15). Drivers by points: match/switch 5 (14 pts), if/else 2 (nesting depth added 9). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
CanvasContextMenu::handle_ui_message (cognitive 16) editor/src/plugins/absm/state_graph/context.rs:116— CanvasContextMenu::handle_ui_message has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (9 pts), loops 2 (7 pts) (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.
TrackView::handle_routed_message (cognitive 16) editor/src/plugins/animation/track.rs:398— TrackView::handle_routed_message has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (11 pts), match/switch 2 (5 pts) (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.
ReflectionProbePreviewControlPanel::handle_ui_message (cognitive 16) editor/src/plugins/probe.rs:107— ReflectionProbePreviewControlPanel::handle_ui_message has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 1 (4 pts) (nesting depth added 10). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
TileColliderEditor::handle_ui_message (cognitive 16) editor/src/plugins/tilemap/collider_editor.rs:327— TileColliderEditor::handle_ui_message has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (13 pts), match/switch 1 (3 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.
CollidersTab::handle_ui_message (cognitive 16) editor/src/plugins/tilemap/colliders_tab.rs:293— CollidersTab::handle_ui_message has cognitive complexity 16 (threshold 15). Drivers by points: if/else 12 (16 pts) (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.
NodeSelector::handle_routed_message (cognitive 16) editor/src/scene/selector.rs:239— NodeSelector::handle_routed_message has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (14 pts), match/switch 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.
BlendAnimations::collect_animation_events (cognitive 16) fyrox-animation/src/machine/node/blend.rs:172— BlendAnimations::collect_animation_events has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (13 pts), loops 1 (2 pts), match/switch 1 (nesting depth added 9). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
PoseNode::collect_animations (cognitive 16) fyrox-animation/src/machine/node/mod.rs:116— PoseNode::collect_animations has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (9 pts), loops 3 (6 pts), match/switch 1 (nesting depth added 9). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
ColorGradient::get_color (cognitive 16) fyrox-core/src/color_gradient.rs:102— ColorGradient::get_color has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (13 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 4). 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.
InheritableVariable::visit (cognitive 16) fyrox-core/src/variable.rs:354— InheritableVariable::visit has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 1 (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.
VertexBuffer::new_with_layout (cognitive 16) fyrox-impl/src/scene/mesh/buffer.rs:815— VertexBuffer::new_with_layout has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 3 (4 pts), boolean chains 1 (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.
BlendShapesContainer::from_lists (cognitive 16) fyrox-impl/src/scene/mesh/surface.rs:116— BlendShapesContainer::from_lists has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (9 pts), loops 4 (7 pts) (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.
TileSetWfcConstraint::fill_pattern_map (cognitive 16) fyrox-impl/src/scene/tilemap/autotile.rs:137— TileSetWfcConstraint::fill_pattern_map has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (15 pts), loops 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.
CustomTileCollider::from_str (cognitive 16) fyrox-impl/src/scene/tilemap/tile_collider.rs:328— CustomTileCollider::from_str has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (12 pts), loops 3 (4 pts) (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.
TokenIter::next (cognitive 16) fyrox-impl/src/scene/tilemap/tile_collider.rs:422— TokenIter::next has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (15 pts), loops 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.
ResourceManagerState::try_move_folder (cognitive 16) fyrox-resource/src/manager.rs:2037— ResourceManagerState::try_move_folder has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (12 pts), loops 2 (3 pts), boolean chains 1 (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.
Image::measure_override (cognitive 16) fyrox-ui/src/image.rs:202— Image::measure_override has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (16 pts) (nesting depth added 10). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D22 · Internal API Consistency· Inconsistent naming for setting a path. AssetItemBuilder uses 'with_path', while the AssetSelector builders use 'with_selected_asset_path'. Given that AssetItem represents a file/resource and the selector selects one, 'with_path' is the more generic and consistent term for setting a location. · ×1
Inconsistent naming for setting a path. AssetItemBuilder uses 'with_path', while the AssetSelector builders use 'with_selected_asset_path'. Given that AssetItem represents a file/resource and the selector selects one, 'with_path' is the more generic and consistent term for setting a location. — Rename 'with_selected_asset_path' to 'with_path' in both AssetSelectorBuilder and AssetSelectorWindowBuilder to align with AssetItemBuilder. (signatures: AssetItemBuilder.with_path(path: P): Self | AssetSelectorBuilder.with_selected_asset_path(selected_asset_path: Cow): Self | AssetSelectorWindowBuilder.with_selected_asset_path(selected_asset_path: Cow): Self)
D22 · Internal API Consistency· Redundant methods with overlapping intent. 'push' and 'push_command' both add a command to the group. One likely accepts a generic type C and the other a concrete Command, but this creates confusion for users on which to use. · ×1
Redundant methods with overlapping intent. 'push' and 'push_command' both add a command to the group. One likely accepts a generic type C and the other a concrete Command, but this creates confusion for users on which to use. — Remove 'push_command' and rely on 'push' with appropriate type inference or overloading, or rename 'push' to 'push_generic' if 'push_command' is the primary intended API for the concrete type. (signatures: CommandGroup.push(command: C) | CommandGroup.push_command(command: Command))
D22 · Internal API Consistency· Inconsistent removal API. 'remove' takes an ID and returns a boxed trait object, while 'remove_typed' takes no arguments (implying it removes the specific type T) and returns the concrete type. This splits the removal logic between ID-based and Type-based removal without a clear pattern (e.g., 'remove_by_id' vs 'remove_by_type'). · ×1
Inconsistent removal API. 'remove' takes an ID and returns a boxed trait object, while 'remove_typed' takes no arguments (implying it removes the specific type T) and returns the concrete type. This splits the removal logic between ID-based and Type-based removal without a clear pattern (e.g., 'remove_by_id' vs 'remove_by_type'). — Standardize on ID-based removal for all types (e.g., 'remove<T>(id: Uuid)') or provide 'remove_by_id' and 'remove_by_type' explicitly. Currently, 'remove_typed' is ambiguous about which instance it removes if multiple of type T exist. (signatures: InteractionModeContainer.remove(id: Uuid): Box<dyn InteractionMode> | InteractionModeContainer.remove_typed(): T)
D22 · Internal API Consistency· Inconsistent method signatures for UI message handling. The parameters vary significantly · ×1
Inconsistent method signatures for UI message handling. The parameters vary significantly: some include 'engine', some 'sender', some 'editor_selection', some 'entry', and some none. This makes it difficult to implement a unified message dispatch system or understand the required context for each component. — Define a standard 'HandleUiMessage' trait or signature that accepts a consistent set of context objects (e.g., Engine, Sender, Selection) and have all components implement it, allowing optional context to be ignored if not needed. (signatures: AssetItemContextMenu.handle_ui_message(message: UiMessage, sender: MessageSender, engine: Engine): bool | AssetBrowser.handle_ui_message(message: UiMessage, engine: Engine, entry: EditorSceneEntry, sender: MessageSender) | AudioPanel.handle_ui_message(message: UiMessage, editor_selection: Selection, sender: MessageSender, engine: Engine) | CommandStackViewer.handle_ui_message(message: UiMessage))
Change-coupling hub: mod.rs → selection.rs, selection.rs, selection.rs editor/src/audio/mod.rs— `editor/src/audio/mod.rs` changes together with 3 other files — `editor/src/plugins/animation/selection.rs`, `editor/src/ui_scene/selection.rs`, `editor/src/world/selection.rs` — none of which declares a dependency on it: one file is the hub of 3 separate couplings, not 3 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 3.
D4 · Code Duplication· Near-duplicate member family (3 members, 45 shared lines) · ×1
Near-duplicate member family (3 members, 45 shared lines) editor/src/plugins/tilemap/colliders_tab.rs:148— editor/src/plugins/tilemap/colliders_tab.rs:148-262 | editor/src/plugins/tilemap/macro_tab.rs:200-333 | editor/src/plugins/tilemap/properties_tab.rs:252-499 — These 3 members are variants of one another: a block of 45 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 3 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 3 times.
Near-duplicate member pair (101 shared lines) fyrox-impl/src/scene/dim2/physics/mod.rs:1330— fyrox-impl/src/scene/dim2/physics/mod.rs:1330-1473 | fyrox-impl/src/scene/graph/physics/mod.rs:1843-1995 — These two members are variants of one another: 101 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
Near-duplicate member pair (97 shared lines) fyrox-impl/src/scene/dim2/physics/mod.rs:1053— fyrox-impl/src/scene/dim2/physics/mod.rs:1053-1190 | fyrox-impl/src/scene/graph/physics/mod.rs:1493-1701 — These two members are variants of one another: 97 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
Near-duplicate member pair (91 shared lines) fyrox-impl/src/scene/dim2/physics/mod.rs:1197— fyrox-impl/src/scene/dim2/physics/mod.rs:1197-1323 | fyrox-impl/src/scene/graph/physics/mod.rs:1708-1836 — These two members are variants of one another: 91 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
Near-duplicate member pair (55 shared lines) fyrox-impl/src/scene/dim2/physics/mod.rs:708— fyrox-impl/src/scene/dim2/physics/mod.rs:708-770 | fyrox-impl/src/scene/graph/physics/mod.rs:1150-1213 — These two members are variants of one another: 55 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
Near-duplicate member pair (47 shared lines) editor/src/plugins/inspector/editors/dyntype.rs:299— editor/src/plugins/inspector/editors/dyntype.rs:299-396 | editor/src/plugins/inspector/editors/script.rs:397-494 — These two members are variants of one another: 47 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· Edited copy of a member (33 corresponding lines) · ×1
Edited copy of a member (33 corresponding lines) fyrox-graphics/src/gpu_texture.rs:284— fyrox-graphics/src/gpu_texture.rs:284-320 | fyrox-graphics/src/gpu_texture.rs:324-360 — These two members are one piece of code written twice and then edited apart: 33 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 (12 corresponding lines) · ×1
Edited copy of a member (12 corresponding lines) fyrox-animation/src/machine/node/blendspace.rs:124— fyrox-animation/src/machine/node/blendspace.rs:124-151 | fyrox-animation/src/machine/node/blendspace.rs:163-218 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (11 corresponding lines) · ×1
Edited copy of a member (11 corresponding lines) editor/src/plugins/tilemap/autotile.rs:875— editor/src/plugins/tilemap/autotile.rs:875-885 | editor/src/plugins/tilemap/wfc.rs:888-898 — 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 (14 corresponding lines) · ×1
Edited copy of a member (14 corresponding lines) fyrox-math/src/lib.rs:134— fyrox-math/src/lib.rs:134-154 | fyrox-math/src/lib.rs:296-313 — 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· Members sharing a duplicated core (8 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (8 members, 50+ identical tokens) fyrox-impl/src/engine/mod.rs:1810— fyrox-impl/src/engine/mod.rs:1810-1906 | fyrox-impl/src/engine/mod.rs:1908-1998 | fyrox-impl/src/engine/mod.rs:2005-2073 | fyrox-impl/src/engine/mod.rs:2082-2179 | fyrox-impl/src/engine/mod.rs:2186-2214 | fyrox-impl/src/engine/mod.rs:2221-2249 | fyrox-impl/src/engine/mod.rs:2256-2284 | fyrox-impl/src/engine/mod.rs:2404-2466 — 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· Members sharing a duplicated core (6 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (6 members, 50+ identical tokens) fyrox-ui/src/inspector/editors/cell.rs:78— fyrox-ui/src/inspector/editors/cell.rs:78-118 | fyrox-ui/src/inspector/editors/cell.rs:123-164 | fyrox-ui/src/inspector/editors/hashmap/mod.rs:121-158 | fyrox-ui/src/inspector/editors/hashmap/mod.rs:175-210 | fyrox-ui/src/inspector/editors/style.rs:514-584 | fyrox-ui/src/inspector/editors/style.rs:589-636 — 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.
Duplicated block (52–54 lines × 2) fyrox-impl/src/scene/dim2/physics/mod.rs:1198— fyrox-impl/src/scene/dim2/physics/mod.rs:1198-1249 | fyrox-impl/src/scene/graph/physics/mod.rs:1709-1762 — before extracting anything, compare `fyrox-impl/src/scene/dim2/physics/mod.rs` and `fyrox-impl/src/scene/graph/physics/mod.rs` as WHOLE FILES: this scan already matched 34 separate duplicated blocks between them, totalling at least 555 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 (50 lines × 2) editor/src/plugins/tilemap/palette.rs:2181— editor/src/plugins/tilemap/palette.rs:2181-2230 | editor/src/plugins/tilemap/panel_preview.rs:91-140 — 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 (48–49 lines × 2) fyrox-impl/src/scene/dim2/physics/mod.rs:1369— fyrox-impl/src/scene/dim2/physics/mod.rs:1369-1417 | fyrox-impl/src/scene/graph/physics/mod.rs:1884-1931 — before extracting anything, compare `fyrox-impl/src/scene/dim2/physics/mod.rs` and `fyrox-impl/src/scene/graph/physics/mod.rs` as WHOLE FILES: this scan already matched 34 separate duplicated blocks between them, totalling at least 555 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 (43 lines × 2) fyrox-impl/src/scene/graph/physics/mod.rs:534— fyrox-impl/src/scene/graph/physics/mod.rs:534-576 | fyrox-impl/src/scene/graph/physics/mod.rs:625-667 — both copies are in the same file, so extract the 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 (39 lines × 2) fyrox-build-tools/src/export/android.rs:61— fyrox-build-tools/src/export/android.rs:61-99 | fyrox-build-tools/src/export/pc.rs:49-87 — 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 (34–36 lines × 2) fyrox-impl/src/scene/dim2/physics/mod.rs:861— fyrox-impl/src/scene/dim2/physics/mod.rs:861-896 | fyrox-impl/src/scene/graph/physics/mod.rs:1303-1336 — before extracting anything, compare `fyrox-impl/src/scene/dim2/physics/mod.rs` and `fyrox-impl/src/scene/graph/physics/mod.rs` as WHOLE FILES: this scan already matched 34 separate duplicated blocks between them, totalling at least 555 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 (31 lines × 2) fyrox-ui/src/lib.rs:2796— fyrox-ui/src/lib.rs:2796-2826 | fyrox-ui/src/lib.rs:3036-3066 — both copies are in the same file, so extract the 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 (28–29 lines × 2) editor/src/plugins/tilemap/autotile.rs:468— editor/src/plugins/tilemap/autotile.rs:468-495 | editor/src/plugins/tilemap/wfc.rs:503-531 — before extracting anything, compare `editor/src/plugins/tilemap/autotile.rs` and `editor/src/plugins/tilemap/wfc.rs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 142 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (29 lines × 2) fyrox-impl/src/scene/dim2/rectangle.rs:382— fyrox-impl/src/scene/dim2/rectangle.rs:382-410 | fyrox-impl/src/scene/sprite.rs:377-405 — before extracting anything, compare `fyrox-impl/src/scene/dim2/rectangle.rs` and `fyrox-impl/src/scene/sprite.rs` as WHOLE FILES: this scan already matched 3 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. 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 (28 lines × 2) fyrox-impl/src/scene/tilemap/update.rs:919— fyrox-impl/src/scene/tilemap/update.rs:919-946 | fyrox-impl/src/scene/tilemap/update.rs:947-974 — both copies are in the same file, so extract the 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 (24–27 lines × 2) fyrox-ui/src/inspector/editors/array.rs:460— fyrox-ui/src/inspector/editors/array.rs:460-483 | fyrox-ui/src/inspector/editors/collection.rs:660-686 — before extracting anything, compare `fyrox-ui/src/inspector/editors/array.rs` and `fyrox-ui/src/inspector/editors/collection.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 76 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 (24–25 lines × 2) fyrox-resource/src/manager.rs:1125— fyrox-resource/src/manager.rs:1125-1148 | fyrox-resource/src/manager.rs:1273-1297 — both copies are in the same file, so extract the 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 (23–24 lines × 2) editor/src/plugins/tilemap/colliders_tab.rs:237— editor/src/plugins/tilemap/colliders_tab.rs:237-260 | editor/src/plugins/tilemap/properties_tab.rs:462-484 — before extracting anything, compare `editor/src/plugins/tilemap/colliders_tab.rs` and `editor/src/plugins/tilemap/properties_tab.rs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 157 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 (24 lines × 2) fyrox-graphics-gl/src/framebuffer.rs:431— fyrox-graphics-gl/src/framebuffer.rs:431-454 | fyrox-graphics-gl/src/framebuffer.rs:487-510 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (21–22 lines × 2) fyrox-core/src/pool/multiborrow.rs:235— fyrox-core/src/pool/multiborrow.rs:235-255 | fyrox-core/src/pool/multiborrow.rs:296-317 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (21 lines × 3) fyrox-ui/src/lib.rs:2822— fyrox-ui/src/lib.rs:2822-2842 | fyrox-ui/src/lib.rs:3062-3082 | fyrox-ui/src/lib.rs:3109-3129 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (20 lines × 4) fyrox-impl/src/scene/debug.rs:135— fyrox-impl/src/scene/debug.rs:135-154 | fyrox-impl/src/scene/debug.rs:214-233 | fyrox-impl/src/scene/debug.rs:314-333 | fyrox-impl/src/scene/debug.rs:555-574 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (20 lines × 3) fyrox-graphics/src/gpu_texture.rs:286— fyrox-graphics/src/gpu_texture.rs:286-305 | fyrox-graphics/src/gpu_texture.rs:326-345 | fyrox-graphics/src/gpu_texture.rs:365-384 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (18 lines × 3) editor/src/plugins/tilemap/properties_tab.rs:693— editor/src/plugins/tilemap/properties_tab.rs:693-710 | editor/src/plugins/tilemap/properties_tab.rs:726-743 | editor/src/plugins/tilemap/properties_tab.rs:759-776 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (15–18 lines × 2) fyrox-impl/src/resource/fbx/mod.rs:331— fyrox-impl/src/resource/fbx/mod.rs:331-348 | fyrox-impl/src/resource/gltf/material.rs:430-444 — 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 (13–18 lines × 2) fyrox-ui/src/border.rs:165— fyrox-ui/src/border.rs:165-177 | fyrox-ui/src/scroll_panel.rs:242-259 — 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–17 lines × 3) editor/src/plugins/tilemap/colliders_tab.rs:192— editor/src/plugins/tilemap/colliders_tab.rs:192-201 | editor/src/plugins/tilemap/macro_tab.rs:258-267 | editor/src/plugins/tilemap/properties_tab.rs:314-330 — before extracting anything, compare `editor/src/plugins/tilemap/colliders_tab.rs` and `editor/src/plugins/tilemap/macro_tab.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 113 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (16–17 lines × 3) editor/src/plugins/tilemap/colliders_tab.rs:208— editor/src/plugins/tilemap/colliders_tab.rs:208-223 | editor/src/plugins/tilemap/macro_tab.rs:274-290 | editor/src/plugins/tilemap/properties_tab.rs:337-352 — before extracting anything, compare `editor/src/plugins/tilemap/colliders_tab.rs` and `editor/src/plugins/tilemap/macro_tab.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 113 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (13–17 lines × 2) editor/src/command/panel.rs:98— editor/src/command/panel.rs:98-110 | fyrox-ui/src/log.rs:178-194 — 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 (16–17 lines × 2) editor/src/light.rs:163— editor/src/light.rs:163-179 | editor/src/plugins/inspector/mod.rs:297-312 — before extracting anything, compare `editor/src/light.rs` and `editor/src/plugins/inspector/mod.rs` as WHOLE FILES: this scan already matched 3 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. 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 (16 lines × 4) fyrox-impl/src/scene/debug.rs:184— fyrox-impl/src/scene/debug.rs:184-199 | fyrox-impl/src/scene/debug.rs:263-278 | fyrox-impl/src/scene/debug.rs:363-378 | fyrox-impl/src/scene/debug.rs:560-575 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (16 lines × 3) editor/src/plugins/ragdoll.rs:346— editor/src/plugins/ragdoll.rs:346-361 | editor/src/plugins/ragdoll.rs:401-416 | editor/src/plugins/ragdoll.rs:446-461 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (14–16 lines × 2) fyrox-ui/src/color/mod.rs:466— fyrox-ui/src/color/mod.rs:466-479 | fyrox-ui/src/color/mod.rs:642-657 — both copies are in the same file, so extract the 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 × 3) editor/src/plugins/inspector/editors/resource.rs:242— editor/src/plugins/inspector/editors/resource.rs:242-256 | editor/src/plugins/inspector/editors/surface.rs:162-176 | editor/src/plugins/material/editor.rs:174-188 — 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 (13–15 lines × 2) editor/src/lib.rs:455— editor/src/lib.rs:455-467 | editor/src/lib.rs:476-490 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 3) editor/src/asset/creator.rs:145— editor/src/asset/creator.rs:145-158 | editor/src/light.rs:165-178 | editor/src/plugins/inspector/mod.rs:298-311 — before extracting anything, compare `editor/src/asset/creator.rs` and `editor/src/light.rs` 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. 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 (12–14 lines × 3) fyrox-graphics-wgpu/src/buffer.rs:167— fyrox-graphics-wgpu/src/buffer.rs:167-180 | fyrox-graphics-wgpu/src/framebuffer.rs:963-974 | fyrox-graphics-wgpu/src/read_buffer.rs:148-159 — 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–14 lines × 2) editor/src/scene/clipboard.rs:71— editor/src/scene/clipboard.rs:71-84 | editor/src/ui_scene/clipboard.rs:67-78 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (11–14 lines × 2) fyrox-impl/src/scene/mesh/surface.rs:648— fyrox-impl/src/scene/mesh/surface.rs:648-658 | fyrox-impl/src/scene/mesh/surface.rs:799-812 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 8) fyrox-impl/src/engine/mod.rs:1815— fyrox-impl/src/engine/mod.rs:1815-1827 | fyrox-impl/src/engine/mod.rs:1917-1929 | fyrox-impl/src/engine/mod.rs:1958-1970 | fyrox-impl/src/engine/mod.rs:2010-2022 | fyrox-impl/src/engine/mod.rs:2155-2167 | fyrox-impl/src/engine/mod.rs:2190-2202 | fyrox-impl/src/engine/mod.rs:2225-2237 | fyrox-impl/src/engine/mod.rs:2260-2272 — all 8 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (13 lines × 5) fyrox-ui/src/inspector/editors/cell.rs:84— fyrox-ui/src/inspector/editors/cell.rs:84-96 | fyrox-ui/src/inspector/editors/cell.rs:129-141 | fyrox-ui/src/inspector/editors/hashmap/mod.rs:178-190 | fyrox-ui/src/inspector/editors/style.rs:519-531 | fyrox-ui/src/inspector/editors/style.rs:601-613 — there are 5 copies across 3 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 5 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (13 lines × 3) fyrox-ui/src/inspector/editors/inherit.rs:215— fyrox-ui/src/inspector/editors/inherit.rs:215-227 | fyrox-ui/src/inspector/editors/inspectable.rs:93-105 | fyrox-ui/src/inspector/editors/refcell.rs:84-96 — before extracting anything, compare `fyrox-ui/src/inspector/editors/inspectable.rs` and `fyrox-ui/src/inspector/editors/refcell.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 52 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–13 lines × 2) fyrox-graph/src/lib.rs:1527— fyrox-graph/src/lib.rs:1527-1536 | fyrox-graph/src/lib.rs:1595-1607 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11–12 lines × 3) fyrox-impl/src/scene/transform.rs:501— fyrox-impl/src/scene/transform.rs:501-512 | fyrox-impl/src/scene/transform.rs:514-525 | fyrox-impl/src/scene/transform.rs:526-536 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (11 lines × 10) fyrox-impl/src/engine/mod.rs:1820— fyrox-impl/src/engine/mod.rs:1820-1830 | fyrox-impl/src/engine/mod.rs:1922-1932 | fyrox-impl/src/engine/mod.rs:1963-1973 | fyrox-impl/src/engine/mod.rs:2015-2025 | fyrox-impl/src/engine/mod.rs:2160-2170 | fyrox-impl/src/engine/mod.rs:2195-2205 | fyrox-impl/src/engine/mod.rs:2230-2240 | fyrox-impl/src/engine/mod.rs:2265-2275 | fyrox-impl/src/engine/mod.rs:2417-2427 | fyrox-impl/src/engine/mod.rs:2445-2455 — all 10 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (11 lines × 3) editor/src/plugins/tilemap/colliders_tab.rs:69— editor/src/plugins/tilemap/colliders_tab.rs:69-79 | editor/src/plugins/tilemap/macro_tab.rs:71-81 | editor/src/plugins/tilemap/properties_tab.rs:89-99 — before extracting anything, compare `editor/src/plugins/tilemap/colliders_tab.rs` and `editor/src/plugins/tilemap/macro_tab.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 113 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–11 lines × 2) fyrox-graphics-gl/src/program.rs:162— fyrox-graphics-gl/src/program.rs:162-172 | fyrox-graphics-wgpu/src/program.rs:257-264 — 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 (9–10 lines × 2) editor/src/plugins/tilemap/colliders_tab.rs:166— editor/src/plugins/tilemap/colliders_tab.rs:166-174 | editor/src/plugins/tilemap/properties_tab.rs:375-384 — before extracting anything, compare `editor/src/plugins/tilemap/colliders_tab.rs` and `editor/src/plugins/tilemap/properties_tab.rs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 157 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 × 4) fyrox-impl/src/scene/debug.rs:707— fyrox-impl/src/scene/debug.rs:707-714 | fyrox-impl/src/scene/debug.rs:764-771 | fyrox-impl/src/scene/mesh/surface.rs:624-631 | fyrox-impl/src/scene/mesh/surface.rs:765-772 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (6–8 lines × 3) fyrox-math/src/lib.rs:144— fyrox-math/src/lib.rs:144-151 | fyrox-math/src/lib.rs:304-309 | fyrox-math/src/lib.rs:340-347 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (7 lines × 4) editor/src/plugins/tilemap/properties_tab.rs:669— editor/src/plugins/tilemap/properties_tab.rs:669-675 | editor/src/plugins/tilemap/properties_tab.rs:692-698 | editor/src/plugins/tilemap/properties_tab.rs:725-731 | editor/src/plugins/tilemap/properties_tab.rs:758-764 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (6–7 lines × 2) editor/src/plugins/tilemap/colliders_tab.rs:300— editor/src/plugins/tilemap/colliders_tab.rs:300-306 | editor/src/plugins/tilemap/properties_tab.rs:587-592 — before extracting anything, compare `editor/src/plugins/tilemap/colliders_tab.rs` and `editor/src/plugins/tilemap/properties_tab.rs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 157 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 (4–7 lines × 4) fyrox-ui/src/node/constructor.rs:183— fyrox-ui/src/node/constructor.rs:183-186 | fyrox-ui/src/node/constructor.rs:190-196 | fyrox-ui/src/node/constructor.rs:201-207 | fyrox-ui/src/node/constructor.rs:208-216 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (6 lines × 3) fyrox-ui/src/inspector/editors/texture_slice.rs:611— fyrox-ui/src/inspector/editors/texture_slice.rs:611-616 | fyrox-ui/src/inspector/editors/texture_slice.rs:618-623 | fyrox-ui/src/inspector/editors/texture_slice.rs:625-630 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (3–5 lines × 3) editor/src/plugins/tilemap/palette.rs:1755— editor/src/plugins/tilemap/palette.rs:1755-1759 | editor/src/plugins/tilemap/palette.rs:1771-1775 | editor/src/plugins/tilemap/panel_preview.rs:227-229 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (10 lines × 6) editor/src/asset/item.rs:260— editor/src/asset/item.rs:260-269 | editor/src/plugins/inspector/editors/font.rs:98-109 | editor/src/plugins/inspector/editors/handle.rs:164-175 | editor/src/plugins/inspector/editors/resource.rs:192-203 | fyrox-ui/src/key.rs:230-240 | fyrox-ui/src/key.rs:443-453 — there are 6 copies across 5 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 6 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (5 lines × 4) fyrox-animation/src/machine/mask.rs:73— fyrox-animation/src/machine/mask.rs:73-77 | fyrox-core/src/pool/handle.rs:211-215 | fyrox-core/src/pool/mod.rs:173-177 | fyrox-core/src/variable.rs:441-445 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
Duplicated block (5 lines × 6) editor/src/plugins/tilemap/brush_macro.rs:513— editor/src/plugins/tilemap/brush_macro.rs:513-517 | editor/src/plugins/tilemap/brush_macro.rs:519-523 | editor/src/plugins/tilemap/commands.rs:408-412 | editor/src/plugins/tilemap/commands.rs:414-418 | editor/src/plugins/tilemap/commands.rs:466-470 | editor/src/plugins/tilemap/commands.rs:472-476 — there are 6 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 6 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (6 lines × 4) fyrox-ui/src/inspector/editors/texture_slice.rs:610— fyrox-ui/src/inspector/editors/texture_slice.rs:610-615 | fyrox-ui/src/inspector/editors/texture_slice.rs:617-622 | fyrox-ui/src/inspector/editors/texture_slice.rs:624-629 | fyrox-ui/src/inspector/editors/texture_slice.rs:631-636 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Documentation: contradicts the code template-core/src/android/README.md— Android build instructions point at `cargo-apk apk run` for armv7-linux-androideabi, but no cross-targeting or wasm-pack build instructions are present. Update the Android section to reflect current Rust target and wasm-pack commands.
No ADRs found — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`.
Split fyrox-impl — A generic fyrox implementation name that is large (71k LoC) and spans many unrelated subsystems like scene/tilemap, renderer, resource/gltf, and physics. Suggested:
D34 · Knowledge Freshness· Further orphaned files (smaller) · ×1
Further orphaned files (smaller) — 9 smaller file(s) also have no living knowledge — folded into the freshness score and metrics rather than raised one row each — most significant first: fyrox-impl/src/scene/terrain/brushstroke/brushraster.rs, fyrox-math/src/segment.rs, fyrox-impl/src/resource/gltf/simplify.rs, fyrox-core-derive/src/reflect/prop.rs, fyrox-impl/src/resource/gltf/uri.rs, fyrox-core/src/safelock.rs, fyrox-core-derive/src/visit/utils.rs, fyrox-impl/src/resource/gltf/iter.rs (and 1 more) (11 orphaned of 595 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated and example/demo trees and test files identified by path convention, largest first; 595 of the 646 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.
Logging is not universal — Only 14/15 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `template`.
Subsumed condition operand fyrox-impl/src/resource/fbx/mod.rs:390— `name.contains("ShininessExponent")` can never decide this `||` — every value satisfying `name.contains("ShininessExponent")` also satisfies `name.contains("Shininess")`, so the `||` chain is already decided by the latter. The expression is equivalent to the chain without it, which means it is wider than it reads. Delete the dead operand, or narrow the surviving one if IT is the accident.
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.
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 01a0eb7b-496b-7708-81df-bd87343f61dc · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 37 · Warnings: 1262 · Recommendations: 9 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 29-09-2026 @ 04:45 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.