Co-change coupling from Git history: bricks that keep changing in the same commits are coupled, whatever their requires say. The pairs worth reporting are those with no dependency path between them, which is coupling the source doesn't show.
Co-change coupling from Git history: bricks that keep changing in the same commits are coupled, whatever their requires say. The pairs worth reporting are those with no dependency path between them, which is coupling the source doesn't show.
(findings {:keys [min-shared max-bricks-per-commit]}
{:keys [bricks edges commits]})Hidden co-change coupling: pairs that changed together in at least min-shared commits, with no dependency path between them, with their strength as their value. Each is reported on the less changed brick, and marked :historical?, since it comes from history rather than from the code.
Hidden co-change coupling: pairs that changed together in at least min-shared commits, with no dependency path between them, with their strength as their value. Each is reported on the less changed brick, and marked :historical?, since it comes from history rather than from the code.
(pairs bricks commits max-bricks)Pairs of bricks that changed together, as maps of :bricks (the two names, the less changed first), :shared (commits touching both), :changes (commits touching the less changed), and :strength (shared / changes).
Pairs of bricks that changed together, as maps of :bricks (the two names, the less changed first), :shared (commits touching both), :changes (commits touching the less changed), and :strength (shared / changes).
cljdoc builds & hosts documentation for Clojure/Script libraries
| Ctrl+k | Jump to recent docs |
| ← | Move to previous article |
| → | Move to next article |
| Ctrl+/ | Jump to the search field |