Executive summary
lapce/floem is rated At risk because critical security findings are open, most of them in the build pipeline. It scores 59 out of 100, which the At risk rating leaves unchanged. We judged it as a preview release, against a lower bar.
Event Sourcing, at 49, is the weakest lens and counts most in the score. The best first step is making event replay repeatable, worth about 9 points. Recording design decisions is another step, worth about 3 points. Raising Event Sourcing to 65 would lift the score to about 66.
Ten pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Two known security holes in the packages the code depends on can be used by attackers. Pinning each tool to an exact version and updating the vulnerable packages would close both risks. The two sets of files in separate parts that keep changing together need that dependency made explicit.
The product code is 82,284 lines, about €130,000 to rebuild.
If Event Sourcing rose from 49 to 65, the lowest score rated Strong, the score would rise from 59 to about 66.
New since the last survey: 4 findings
- Dependency Hygiene · Yanked release: clipboard-win
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Supply-chain Provenance & Signing · REDACTED
Fixed since the last survey: 12 findings
- Knowledge Freshness · Orphaned knowledge src/event/listener.rs
- Knowledge Freshness · Orphaned knowledge editor-core/src/char_buffer.rs
- Knowledge Freshness · Orphaned knowledge src/event/drag_state.rs
- Knowledge Freshness · Orphaned knowledge src/text/layout.rs
- Knowledge Freshness · Orphaned knowledge reactive/src/context.rs
- Knowledge Freshness · Orphaned knowledge editor-core/src/buffer/mod.rs
- Knowledge Freshness · Orphaned knowledge editor-core/src/buffer/rope_text.rs
- Knowledge Freshness · Orphaned knowledge editor-core/src/word.rs
- Knowledge Freshness · Orphaned knowledge src/receiver_signal/common/executors.rs
- Knowledge Freshness · Orphaned knowledge src/views/navigation_stack.rs
- Supply-chain Provenance & Signing REDACTED
- Documentation (README) · README may be stale
Rebuild cost: about €130,000 · Estimate
| Cost to rebuild | €42,000 to €210,000, for 699 to 2,218 hours of work, about 0.9 person-years for 1 to 2 engineers |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 59. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Medium: 82,284 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 floem_editor_core.mode | 2 floem.event | 3 floem.style.props | 4 floem_editor_core.buffer | 5 floem.style.values | 6 floem_editor_core.cursor | 7 floem.style.unit | 8 floem.paint | 9 floem_renderer.text.attrs | 10 floem.view | 11 floem.style.custom | 12 floem.views.virtual_stack | 13 floem_reactive.signal | 14 floem_reactive.id | 15 floem_reactive.scope | 16 floem.style.cx | 17 floem.views.dropdown | 18 floem.views.editor.view | 19 floem.views.resizable | 20 floem.views.scroll | 21 floem.views.slider | 22 floem.views.editor | 23 floem.views.toggle_button | 24 floem.views.editor.actions | 25 floem.views.editor.text_document | 26 floem.views.text_editor | 27 floem.views.editor.text | 28 floem.views.text_input | 29 floem.views.label | 30 floem.style | 31 floem.inspector | 32 floem.view.state | 33 floem.window.state | 34 floem.message | 35 floem.views.list | 36 floem.event.dispatch | 37 floem.view.id | 38 floem.box_tree | 39 floem.window.handle | 40 floem.inspector.view |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 floem_editor_core.mode | ||||||||||||||||||||||||||||||||||||||||
| 2 floem.event | 6 | |||||||||||||||||||||||||||||||||||||||
| 3 floem.style.props | 3 | |||||||||||||||||||||||||||||||||||||||
| 4 floem_editor_core.buffer | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 5 floem.style.values | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 6 floem_editor_core.cursor | 2 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 7 floem.style.unit | 9 | |||||||||||||||||||||||||||||||||||||||
| 8 floem.paint | 1 | 2 | 3 | 5 | ||||||||||||||||||||||||||||||||||||
| 9 floem_renderer.text.attrs | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 10 floem.view | 1 | 1 | 2 | 2 | 1 | 1 | 1 | 1 | 1 | 4 | ||||||||||||||||||||||||||||||
| 11 floem.style.custom | 1 | |||||||||||||||||||||||||||||||||||||||
| 12 floem.views.virtual_stack | 1 | 1 | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 13 floem_reactive.signal | 2 | 2 | 4 | |||||||||||||||||||||||||||||||||||||
| 14 floem_reactive.id | 1 | |||||||||||||||||||||||||||||||||||||||
| 15 floem_reactive.scope | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 16 floem.style.cx | 1 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 17 floem.views.dropdown | 1 | 4 | 1 | 2 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||
| 18 floem.views.editor.view | 1 | 2 | 3 | 1 | 1 | 3 | 1 | 1 | 3 | 1 | 1 | 1 | ||||||||||||||||||||||||||||
| 19 floem.views.resizable | 1 | 5 | 1 | 1 | 2 | 2 | 2 | 2 | 3 | 2 | 2 | 3 | 2 | |||||||||||||||||||||||||||
| 20 floem.views.scroll | 3 | 6 | 3 | 1 | 2 | 3 | 2 | 1 | 3 | 3 | 4 | |||||||||||||||||||||||||||||
| 21 floem.views.slider | 1 | 6 | 1 | 2 | 1 | 1 | 2 | 1 | 2 | 1 | 1 | 1 | ||||||||||||||||||||||||||||
| 22 floem.views.editor | 1 | 2 | 4 | 3 | 2 | 2 | ||||||||||||||||||||||||||||||||||
| 23 floem.views.toggle_button | 1 | 2 | 1 | 2 | 1 | 1 | 1 | 2 | 1 | 2 | 2 | 2 | ||||||||||||||||||||||||||||
| 24 floem.views.editor.actions | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 25 floem.views.editor.text_document | 1 | 1 | 1 | 1 | 3 | 1 | 3 | |||||||||||||||||||||||||||||||||
| 26 floem.views.text_editor | 1 | 1 | 1 | 1 | 1 | 2 | 2 | 1 | ||||||||||||||||||||||||||||||||
| 27 floem.views.editor.text | 1 | 2 | 1 | 6 | 3 | 1 | 2 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||
| 28 floem.views.text_input | 1 | 4 | 1 | 1 | 1 | 1 | 3 | 1 | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||
| 29 floem.views.label | 1 | 2 | 1 | 1 | 1 | 1 | 1 | 2 | 1 | 1 | 3 | 1 | 1 | 1 | ||||||||||||||||||||||||||
| 30 floem.style | 3 | 4 | 1 | 1 | 1 | 2 | 1 | 2 | 1 | 2 | ||||||||||||||||||||||||||||||
| 31 floem.inspector | 1 | 3 | 2 | 1 | 1 | 3 | 1 | 4 | 1 | |||||||||||||||||||||||||||||||
| 32 floem.view.state | 1 | 1 | 2 | 2 | 1 | 2 | ||||||||||||||||||||||||||||||||||
| 33 floem.window.state | 1 | 1 | 2 | 5 | ||||||||||||||||||||||||||||||||||||
| 34 floem.message | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 35 floem.views.list | 4 | 2 | 2 | 1 | 2 | 1 | 2 | |||||||||||||||||||||||||||||||||
| 36 floem.event.dispatch | 6 | 3 | 1 | 2 | 10 | |||||||||||||||||||||||||||||||||||
| 37 floem.view.id | 1 | 1 | 1 | 1 | 2 | 1 | 1 | 4 | ||||||||||||||||||||||||||||||||
| 38 floem.box_tree | 1 | |||||||||||||||||||||||||||||||||||||||
| 39 floem.window.handle | 1 | 1 | 1 | 1 | 1 | 2 | 1 | 1 | 3 | |||||||||||||||||||||||||||||||
| 40 floem.inspector.view | 1 | 1 | 1 | 2 | 1 | 5 | 1 | 2 | 1 |
2→38 floem.event uses floem.box_tree part of a loop✕
- Connections
- 6 pairs of types, where a type in floem.event uses a type in floem.box_tree.
- The types involved
floem.event.DragEndEvent→floem.box_tree.ElementIdfloem.event.DragEnterEvent→floem.box_tree.ElementIdfloem.event.DragLeaveEvent→floem.box_tree.ElementIdfloem.event.DragMoveEvent→floem.box_tree.ElementIdfloem.event.DragTargetEvent→floem.box_tree.ElementIdfloem.event.ScrollTo→floem.box_tree.ElementId
- Direction
- floem.event uses floem.box_tree, so a change to floem.box_tree can break floem.event, while a change to floem.event can't break floem.box_tree.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
3→30 floem.style.props uses floem.style part of a loop✕
- Connections
- 3 pairs of types, where a type in floem.style.props uses a type in floem.style.
- The types involved
floem.style.props.ExtractorField→floem.style.Stylefloem.style.props.StyleDebugGroup→floem.style.Stylefloem.style.props.StylePropReader→floem.style.Style
- Direction
- floem.style.props uses floem.style, so a change to floem.style can break floem.style.props, while a change to floem.style.props can't break floem.style.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
4→1 floem_editor_core.buffer uses floem_editor_core.mode✕
- Connections
- 1 pair of types, where a type in floem_editor_core.buffer uses a type in floem_editor_core.mode.
- The types involved
floem_editor_core.buffer.Buffer→floem_editor_core.mode.Mode
- Direction
- floem_editor_core.buffer uses floem_editor_core.mode, so a change to floem_editor_core.mode can break floem_editor_core.buffer, while a change to floem_editor_core.buffer can't break floem_editor_core.mode.
- Position
- Below the diagonal: floem_editor_core.buffer uses a module listed above it, which is the healthy direction.
4→6 floem_editor_core.buffer uses floem_editor_core.cursor part of a loop✕
- Connections
- 2 pairs of types, where a type in floem_editor_core.buffer uses a type in floem_editor_core.cursor.
- The types involved
floem_editor_core.buffer.Buffer→floem_editor_core.cursor.CursorModefloem_editor_core.buffer.Revision→floem_editor_core.cursor.CursorMode
- Direction
- floem_editor_core.buffer uses floem_editor_core.cursor, so a change to floem_editor_core.cursor can break floem_editor_core.buffer, while a change to floem_editor_core.buffer can't break floem_editor_core.cursor.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
4→35 floem_editor_core.buffer uses floem.views.list part of a loop✕
- Connections
- 1 pair of types, where a type in floem_editor_core.buffer uses a type in floem.views.list.
- The types involved
floem_editor_core.buffer.InsertsValueIter→floem.views.list.Item
- Direction
- floem_editor_core.buffer uses floem.views.list, so a change to floem.views.list can break floem_editor_core.buffer, while a change to floem_editor_core.buffer can't break floem.views.list.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
5→3 floem.style.values uses floem.style.props✕
- Connections
- 2 pairs of types, where a type in floem.style.values uses a type in floem.style.props.
- The types involved
floem.style.values.values$module→floem.style.props.StyleDebugGroupInfofloem.style.values.values$module→floem.style.props.StylePropRef
- Direction
- floem.style.values uses floem.style.props, so a change to floem.style.props can break floem.style.values, while a change to floem.style.values can't break floem.style.props.
- Position
- Below the diagonal: floem.style.values uses a module listed above it, which is the healthy direction.
5→30 floem.style.values uses floem.style part of a loop✕
- Connections
- 2 pairs of types, where a type in floem.style.values uses a type in floem.style.
- The types involved
floem.style.values.ContextValue→floem.style.Stylefloem.style.values.values$module→floem.style.Style
- Direction
- floem.style.values uses floem.style, so a change to floem.style can break floem.style.values, while a change to floem.style.values can't break floem.style.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→1 floem_editor_core.cursor uses floem_editor_core.mode✕
- Connections
- 2 pairs of types, where a type in floem_editor_core.cursor uses a type in floem_editor_core.mode.
- The types involved
floem_editor_core.cursor.Cursor→floem_editor_core.mode.Modefloem_editor_core.cursor.Cursor→floem_editor_core.mode.MotionMode
- Direction
- floem_editor_core.cursor uses floem_editor_core.mode, so a change to floem_editor_core.mode can break floem_editor_core.cursor, while a change to floem_editor_core.cursor can't break floem_editor_core.mode.
- Position
- Below the diagonal: floem_editor_core.cursor uses a module listed above it, which is the healthy direction.
6→4 floem_editor_core.cursor uses floem_editor_core.buffer✕
- Connections
- 2 pairs of types, where a type in floem_editor_core.cursor uses a type in floem_editor_core.buffer.
- The types involved
floem_editor_core.cursor.Cursor→floem_editor_core.buffer.Bufferfloem_editor_core.cursor.cursor$module→floem_editor_core.buffer.Buffer
- Direction
- floem_editor_core.cursor uses floem_editor_core.buffer, so a change to floem_editor_core.buffer can break floem_editor_core.cursor, while a change to floem_editor_core.cursor can't break floem_editor_core.buffer.
- Position
- Below the diagonal: floem_editor_core.cursor uses a module listed above it, which is the healthy direction.
6→35 floem_editor_core.cursor uses floem.views.list part of a loop✕
- Connections
- 1 pair of types, where a type in floem_editor_core.cursor uses a type in floem.views.list.
- The types involved
floem_editor_core.cursor.RegionsIter→floem.views.list.Item
- Direction
- floem_editor_core.cursor uses floem.views.list, so a change to floem.views.list can break floem_editor_core.cursor, while a change to floem_editor_core.cursor can't break floem.views.list.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→5 floem.style.unit uses floem.style.values✕
- Connections
- 9 pairs of types, where a type in floem.style.unit uses a type in floem.style.values.
- The types involved
floem.style.unit.AnchorAbout→floem.style.values.StylePropValuefloem.style.unit.Angle→floem.style.values.StylePropValuefloem.style.unit.Length→floem.style.values.StylePropValuefloem.style.unit.LengthAuto→floem.style.values.StylePropValuefloem.style.unit.Pct→floem.style.values.StylePropValuefloem.style.unit.Pt→floem.style.values.StylePropValuefloem.style.unit.Px→floem.style.values.StylePropValuefloem.style.unit.PxPct→floem.style.values.StylePropValuefloem.style.unit.PxPctAuto→floem.style.values.StylePropValue
- Direction
- floem.style.unit uses floem.style.values, so a change to floem.style.values can break floem.style.unit, while a change to floem.style.unit can't break floem.style.values.
- Position
- Below the diagonal: floem.style.unit uses a module listed above it, which is the healthy direction.
8→7 floem.paint uses floem.style.unit✕
- Connections
- 1 pair of types, where a type in floem.paint uses a type in floem.style.unit.
- The types involved
floem.paint.PaintCx→floem.style.unit.FontSizeCx
- Direction
- floem.paint uses floem.style.unit, so a change to floem.style.unit can break floem.paint, while a change to floem.paint can't break floem.style.unit.
- Position
- Below the diagonal: floem.paint uses a module listed above it, which is the healthy direction.
8→33 floem.paint uses floem.window.state part of a loop✕
- Connections
- 2 pairs of types, where a type in floem.paint uses a type in floem.window.state.
- The types involved
floem.paint.GlobalPaintCx→floem.window.state.WindowStatefloem.paint.PaintCx→floem.window.state.WindowState
- Direction
- floem.paint uses floem.window.state, so a change to floem.window.state can break floem.paint, while a change to floem.paint can't break floem.window.state.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→37 floem.paint uses floem.view.id part of a loop✕
- Connections
- 3 pairs of types, where a type in floem.paint uses a type in floem.view.id.
- The types involved
floem.paint.GlobalPaintCx→floem.view.id.ViewIdfloem.paint.PaintOrderTracker→floem.view.id.ViewIdfloem.paint.paint$module→floem.view.id.ViewId
- Direction
- floem.paint uses floem.view.id, so a change to floem.view.id can break floem.paint, while a change to floem.paint can't break floem.view.id.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→38 floem.paint uses floem.box_tree part of a loop✕
- Connections
- 5 pairs of types, where a type in floem.paint uses a type in floem.box_tree.
- The types involved
floem.paint.GlobalPaintCx→floem.box_tree.BoxTreefloem.paint.GlobalPaintCx→floem.box_tree.ElementIdfloem.paint.PaintCx→floem.box_tree.ElementIdfloem.paint.paint$module→floem.box_tree.BoxTreefloem.paint.paint$module→floem.box_tree.ElementId
- Direction
- floem.paint uses floem.box_tree, so a change to floem.box_tree can break floem.paint, while a change to floem.paint can't break floem.box_tree.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→5 floem_renderer.text.attrs uses floem.style.values✕
- Connections
- 1 pair of types, where a type in floem_renderer.text.attrs uses a type in floem.style.values.
- The types involved
floem_renderer.text.attrs.LineHeightValue→floem.style.values.StylePropValue
- Direction
- floem_renderer.text.attrs uses floem.style.values, so a change to floem.style.values can break floem_renderer.text.attrs, while a change to floem_renderer.text.attrs can't break floem.style.values.
- Position
- Below the diagonal: floem_renderer.text.attrs uses a module listed above it, which is the healthy direction.
9→7 floem_renderer.text.attrs uses floem.style.unit✕
- Connections
- 2 pairs of types, where a type in floem_renderer.text.attrs uses a type in floem.style.unit.
- The types involved
floem_renderer.text.attrs.LineHeightValue→floem.style.unit.Ptfloem_renderer.text.attrs.LineHeightValue→floem.style.unit.Px
- Direction
- floem_renderer.text.attrs uses floem.style.unit, so a change to floem.style.unit can break floem_renderer.text.attrs, while a change to floem_renderer.text.attrs can't break floem.style.unit.
- Position
- Below the diagonal: floem_renderer.text.attrs uses a module listed above it, which is the healthy direction.
9→35 floem_renderer.text.attrs uses floem.views.list part of a loop✕
- Connections
- 1 pair of types, where a type in floem_renderer.text.attrs uses a type in floem.views.list.
- The types involved
floem_renderer.text.attrs.ParseList→floem.views.list.Item
- Direction
- floem_renderer.text.attrs uses floem.views.list, so a change to floem.views.list can break floem_renderer.text.attrs, while a change to floem_renderer.text.attrs can't break floem.views.list.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→2 floem.view uses floem.event✕
- Connections
- 1 pair of types, where a type in floem.view uses a type in floem.event.
- The types involved
floem.view.View→floem.event.EventPropagation
- Direction
- floem.view uses floem.event, so a change to floem.event can break floem.view, while a change to floem.view can't break floem.event.
- Position
- Below the diagonal: floem.view uses a module listed above it, which is the healthy direction.
10→3 floem.view uses floem.style.props✕
- Connections
- 1 pair of types, where a type in floem.view uses a type in floem.style.props.
- The types involved
floem.view.View→floem.style.props.StyleClassRef
- Direction
- floem.view uses floem.style.props, so a change to floem.style.props can break floem.view, while a change to floem.view can't break floem.style.props.
- Position
- Below the diagonal: floem.view uses a module listed above it, which is the healthy direction.
10→7 floem.view uses floem.style.unit✕
- Connections
- 2 pairs of types, where a type in floem.view uses a type in floem.style.unit.
- The types involved
floem.view.view$module→floem.style.unit.FontSizeCxfloem.view.view$module→floem.style.unit.Length
- Direction
- floem.view uses floem.style.unit, so a change to floem.style.unit can break floem.view, while a change to floem.view can't break floem.style.unit.
- Position
- Below the diagonal: floem.view uses a module listed above it, which is the healthy direction.
10→8 floem.view uses floem.paint✕
- Connections
- 2 pairs of types, where a type in floem.view uses a type in floem.paint.
- The types involved
floem.view.View→floem.paint.PaintCxfloem.view.view$module→floem.paint.PaintCx
- Direction
- floem.view uses floem.paint, so a change to floem.paint can break floem.view, while a change to floem.view can't break floem.paint.
- Position
- Below the diagonal: floem.view uses a module listed above it, which is the healthy direction.
10→15 floem.view uses floem_reactive.scope part of a loop✕
- Connections
- 1 pair of types, where a type in floem.view uses a type in floem_reactive.scope.
- The types involved
floem.view.ParentView→floem_reactive.scope.Scope
- Direction
- floem.view uses floem_reactive.scope, so a change to floem_reactive.scope can break floem.view, while a change to floem.view can't break floem_reactive.scope.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→16 floem.view uses floem.style.cx part of a loop✕
- Connections
- 1 pair of types, where a type in floem.view uses a type in floem.style.cx.
- The types involved
floem.view.View→floem.style.cx.StyleCx
- Direction
- floem.view uses floem.style.cx, so a change to floem.style.cx can break floem.view, while a change to floem.view can't break floem.style.cx.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→30 floem.view uses floem.style part of a loop✕
- Connections
- 1 pair of types, where a type in floem.view uses a type in floem.style.
- The types involved
floem.view.View→floem.style.Style
- Direction
- floem.view uses floem.style, so a change to floem.style can break floem.view, while a change to floem.view can't break floem.style.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→34 floem.view uses floem.message part of a loop✕
- Connections
- 1 pair of types, where a type in floem.view uses a type in floem.message.
- The types involved
floem.view.View→floem.message.UpdateCx
- Direction
- floem.view uses floem.message, so a change to floem.message can break floem.view, while a change to floem.view can't break floem.message.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→36 floem.view uses floem.event.dispatch part of a loop✕
- Connections
- 1 pair of types, where a type in floem.view uses a type in floem.event.dispatch.
- The types involved
floem.view.View→floem.event.dispatch.EventCx
- Direction
- floem.view uses floem.event.dispatch, so a change to floem.event.dispatch can break floem.view, while a change to floem.view can't break floem.event.dispatch.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→37 floem.view uses floem.view.id part of a loop✕
- Connections
- 4 pairs of types, where a type in floem.view uses a type in floem.view.id.
- The types involved
floem.view.HasViewId→floem.view.id.ViewIdfloem.view.LazyView→floem.view.id.ViewIdfloem.view.View→floem.view.id.ViewIdfloem.view.view$module→floem.view.id.ViewId
- Direction
- floem.view uses floem.view.id, so a change to floem.view.id can break floem.view, while a change to floem.view can't break floem.view.id.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→10 floem.style.custom uses floem.view✕
- Connections
- 1 pair of types, where a type in floem.style.custom uses a type in floem.view.
- The types involved
floem.style.custom.CustomStylable→floem.view.IntoView
- Direction
- floem.style.custom uses floem.view, so a change to floem.view can break floem.style.custom, while a change to floem.style.custom can't break floem.view.
- Position
- Below the diagonal: floem.style.custom uses a module listed above it, which is the healthy direction.
12→2 floem.views.virtual_stack uses floem.event✕
- Connections
- 1 pair of types, where a type in floem.views.virtual_stack uses a type in floem.event.
- The types involved
floem.views.virtual_stack.VirtualStack→floem.event.EventPropagation
- Direction
- floem.views.virtual_stack uses floem.event, so a change to floem.event can break floem.views.virtual_stack, while a change to floem.views.virtual_stack can't break floem.event.
- Position
- Below the diagonal: floem.views.virtual_stack uses a module listed above it, which is the healthy direction.
12→10 floem.views.virtual_stack uses floem.view✕
- Connections
- 1 pair of types, where a type in floem.views.virtual_stack uses a type in floem.view.
- The types involved
floem.views.virtual_stack.VirtualStack→floem.view.View
- Direction
- floem.views.virtual_stack uses floem.view, so a change to floem.view can break floem.views.virtual_stack, while a change to floem.views.virtual_stack can't break floem.view.
- Position
- Below the diagonal: floem.views.virtual_stack uses a module listed above it, which is the healthy direction.
12→13 floem.views.virtual_stack uses floem_reactive.signal part of a loop✕
- Connections
- 1 pair of types, where a type in floem.views.virtual_stack uses a type in floem_reactive.signal.
- The types involved
floem.views.virtual_stack.VirtualStack→floem_reactive.signal.RwSignal
- Direction
- floem.views.virtual_stack uses floem_reactive.signal, so a change to floem_reactive.signal can break floem.views.virtual_stack, while a change to floem.views.virtual_stack can't break floem_reactive.signal.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→16 floem.views.virtual_stack uses floem.style.cx part of a loop✕
- Connections
- 1 pair of types, where a type in floem.views.virtual_stack uses a type in floem.style.cx.
- The types involved
floem.views.virtual_stack.VirtualStack→floem.style.cx.StyleCx
- Direction
- floem.views.virtual_stack uses floem.style.cx, so a change to floem.style.cx can break floem.views.virtual_stack, while a change to floem.views.virtual_stack can't break floem.style.cx.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→34 floem.views.virtual_stack uses floem.message part of a loop✕
- Connections
- 1 pair of types, where a type in floem.views.virtual_stack uses a type in floem.message.
- The types involved
floem.views.virtual_stack.VirtualStack→floem.message.UpdateCx
- Direction
- floem.views.virtual_stack uses floem.message, so a change to floem.message can break floem.views.virtual_stack, while a change to floem.views.virtual_stack can't break floem.message.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→36 floem.views.virtual_stack uses floem.event.dispatch part of a loop✕
- Connections
- 1 pair of types, where a type in floem.views.virtual_stack uses a type in floem.event.dispatch.
- The types involved
floem.views.virtual_stack.VirtualStack→floem.event.dispatch.EventCx
- Direction
- floem.views.virtual_stack uses floem.event.dispatch, so a change to floem.event.dispatch can break floem.views.virtual_stack, while a change to floem.views.virtual_stack can't break floem.event.dispatch.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→37 floem.views.virtual_stack uses floem.view.id part of a loop✕
- Connections
- 1 pair of types, where a type in floem.views.virtual_stack uses a type in floem.view.id.
- The types involved
floem.views.virtual_stack.VirtualStack→floem.view.id.ViewId
- Direction
- floem.views.virtual_stack uses floem.view.id, so a change to floem.view.id can break floem.views.virtual_stack, while a change to floem.views.virtual_stack can't break floem.view.id.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→10 floem_reactive.signal uses floem.view✕
- Connections
- 2 pairs of types, where a type in floem_reactive.signal uses a type in floem.view.
- The types involved
floem_reactive.signal.ReadSignal→floem.view.IntoViewfloem_reactive.signal.RwSignal→floem.view.IntoView
- Direction
- floem_reactive.signal uses floem.view, so a change to floem.view can break floem_reactive.signal, while a change to floem_reactive.signal can't break floem.view.
- Position
- Below the diagonal: floem_reactive.signal uses a module listed above it, which is the healthy direction.
13→12 floem_reactive.signal uses floem.views.virtual_stack✕
- Connections
- 2 pairs of types, where a type in floem_reactive.signal uses a type in floem.views.virtual_stack.
- The types involved
floem_reactive.signal.ReadSignal→floem.views.virtual_stack.VirtualVectorfloem_reactive.signal.RwSignal→floem.views.virtual_stack.VirtualVector
- Direction
- floem_reactive.signal uses floem.views.virtual_stack, so a change to floem.views.virtual_stack can break floem_reactive.signal, while a change to floem_reactive.signal can't break floem.views.virtual_stack.
- Position
- Below the diagonal: floem_reactive.signal uses a module listed above it, which is the healthy direction.
13→14 floem_reactive.signal uses floem_reactive.id part of a loop✕
- Connections
- 4 pairs of types, where a type in floem_reactive.signal uses a type in floem_reactive.id.
- The types involved
floem_reactive.signal.ReadSignal→floem_reactive.id.Idfloem_reactive.signal.RwSignal→floem_reactive.id.Idfloem_reactive.signal.SignalState→floem_reactive.id.Idfloem_reactive.signal.WriteSignal→floem_reactive.id.Id
- Direction
- floem_reactive.signal uses floem_reactive.id, so a change to floem_reactive.id can break floem_reactive.signal, while a change to floem_reactive.signal can't break floem_reactive.id.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→13 floem_reactive.id uses floem_reactive.signal✕
- Connections
- 1 pair of types, where a type in floem_reactive.id uses a type in floem_reactive.signal.
- The types involved
floem_reactive.id.Id→floem_reactive.signal.SignalState
- Direction
- floem_reactive.id uses floem_reactive.signal, so a change to floem_reactive.signal can break floem_reactive.id, while a change to floem_reactive.id can't break floem_reactive.signal.
- Position
- Below the diagonal: floem_reactive.id uses a module listed above it, which is the healthy direction.
15→13 floem_reactive.scope uses floem_reactive.signal✕
- Connections
- 1 pair of types, where a type in floem_reactive.scope uses a type in floem_reactive.signal.
- The types involved
floem_reactive.scope.Scope→floem_reactive.signal.RwSignal
- Direction
- floem_reactive.scope uses floem_reactive.signal, so a change to floem_reactive.signal can break floem_reactive.scope, while a change to floem_reactive.scope can't break floem_reactive.signal.
- Position
- Below the diagonal: floem_reactive.scope uses a module listed above it, which is the healthy direction.
15→14 floem_reactive.scope uses floem_reactive.id✕
- Connections
- 1 pair of types, where a type in floem_reactive.scope uses a type in floem_reactive.id.
- The types involved
floem_reactive.scope.Scope→floem_reactive.id.Id
- Direction
- floem_reactive.scope uses floem_reactive.id, so a change to floem_reactive.id can break floem_reactive.scope, while a change to floem_reactive.scope can't break floem_reactive.id.
- Position
- Below the diagonal: floem_reactive.scope uses a module listed above it, which is the healthy direction.
16→15 floem.style.cx uses floem_reactive.scope✕
- Connections
- 1 pair of types, where a type in floem.style.cx uses a type in floem_reactive.scope.
- The types involved
floem.style.cx.cx$module→floem_reactive.scope.Scope
- Direction
- floem.style.cx uses floem_reactive.scope, so a change to floem_reactive.scope can break floem.style.cx, while a change to floem.style.cx can't break floem_reactive.scope.
- Position
- Below the diagonal: floem.style.cx uses a module listed above it, which is the healthy direction.
16→30 floem.style.cx uses floem.style part of a loop✕
- Connections
- 1 pair of types, where a type in floem.style.cx uses a type in floem.style.
- The types involved
floem.style.cx.StyleCx→floem.style.Style
- Direction
- floem.style.cx uses floem.style, so a change to floem.style can break floem.style.cx, while a change to floem.style.cx can't break floem.style.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→33 floem.style.cx uses floem.window.state part of a loop✕
- Connections
- 1 pair of types, where a type in floem.style.cx uses a type in floem.window.state.
- The types involved
floem.style.cx.StyleCx→floem.window.state.WindowState
- Direction
- floem.style.cx uses floem.window.state, so a change to floem.window.state can break floem.style.cx, while a change to floem.style.cx can't break floem.window.state.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→37 floem.style.cx uses floem.view.id part of a loop✕
- Connections
- 2 pairs of types, where a type in floem.style.cx uses a type in floem.view.id.
- The types involved
floem.style.cx.StyleCx→floem.view.id.ViewIdfloem.style.cx.cx$module→floem.view.id.ViewId
- Direction
- floem.style.cx uses floem.view.id, so a change to floem.view.id can break floem.style.cx, while a change to floem.style.cx can't break floem.view.id.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→2 floem.views.dropdown uses floem.event✕
- Connections
- 1 pair of types, where a type in floem.views.dropdown uses a type in floem.event.
- The types involved
floem.views.dropdown.Dropdown→floem.event.EventPropagation
- Direction
- floem.views.dropdown uses floem.event, so a change to floem.event can break floem.views.dropdown, while a change to floem.views.dropdown can't break floem.event.
- Position
- Below the diagonal: floem.views.dropdown uses a module listed above it, which is the healthy direction.
17→3 floem.views.dropdown uses floem.style.props✕
- Connections
- 4 pairs of types, where a type in floem.views.dropdown uses a type in floem.style.props.
- The types involved
floem.views.dropdown.DropdownClass→floem.style.props.StyleClassfloem.views.dropdown.DropdownClass→floem.style.props.StyleKeyfloem.views.dropdown.DropdownPreviewClass→floem.style.props.StyleClassfloem.views.dropdown.DropdownPreviewClass→floem.style.props.StyleKey
- Direction
- floem.views.dropdown uses floem.style.props, so a change to floem.style.props can break floem.views.dropdown, while a change to floem.views.dropdown can't break floem.style.props.
- Position
- Below the diagonal: floem.views.dropdown uses a module listed above it, which is the healthy direction.
17→10 floem.views.dropdown uses floem.view✕
- Connections
- 1 pair of types, where a type in floem.views.dropdown uses a type in floem.view.
- The types involved
floem.views.dropdown.Dropdown→floem.view.View
- Direction
- floem.views.dropdown uses floem.view, so a change to floem.view can break floem.views.dropdown, while a change to floem.views.dropdown can't break floem.view.
- Position
- Below the diagonal: floem.views.dropdown uses a module listed above it, which is the healthy direction.
17→11 floem.views.dropdown uses floem.style.custom✕
- Connections
- 2 pairs of types, where a type in floem.views.dropdown uses a type in floem.style.custom.
- The types involved
floem.views.dropdown.Dropdown→floem.style.custom.CustomStylablefloem.views.dropdown.DropdownCustomStyle→floem.style.custom.CustomStyle
- Direction
- floem.views.dropdown uses floem.style.custom, so a change to floem.style.custom can break floem.views.dropdown, while a change to floem.views.dropdown can't break floem.style.custom.
- Position
- Below the diagonal: floem.views.dropdown uses a module listed above it, which is the healthy direction.
17→13 floem.views.dropdown uses floem_reactive.signal✕
- Connections
- 1 pair of types, where a type in floem.views.dropdown uses a type in floem_reactive.signal.
- The types involved
floem.views.dropdown.Dropdown→floem_reactive.signal.RwSignal
- Direction
- floem.views.dropdown uses floem_reactive.signal, so a change to floem_reactive.signal can break floem.views.dropdown, while a change to floem.views.dropdown can't break floem_reactive.signal.
- Position
- Below the diagonal: floem.views.dropdown uses a module listed above it, which is the healthy direction.
17→15 floem.views.dropdown uses floem_reactive.scope✕
- Connections
- 1 pair of types, where a type in floem.views.dropdown uses a type in floem_reactive.scope.
- The types involved
floem.views.dropdown.Dropdown→floem_reactive.scope.Scope
- Direction
- floem.views.dropdown uses floem_reactive.scope, so a change to floem_reactive.scope can break floem.views.dropdown, while a change to floem.views.dropdown can't break floem_reactive.scope.
- Position
- Below the diagonal: floem.views.dropdown uses a module listed above it, which is the healthy direction.
17→16 floem.views.dropdown uses floem.style.cx✕
- Connections
- 1 pair of types, where a type in floem.views.dropdown uses a type in floem.style.cx.
- The types involved
floem.views.dropdown.Dropdown→floem.style.cx.StyleCx
- Direction
- floem.views.dropdown uses floem.style.cx, so a change to floem.style.cx can break floem.views.dropdown, while a change to floem.views.dropdown can't break floem.style.cx.
- Position
- Below the diagonal: floem.views.dropdown uses a module listed above it, which is the healthy direction.
17→30 floem.views.dropdown uses floem.style part of a loop✕
- Connections
- 1 pair of types, where a type in floem.views.dropdown uses a type in floem.style.
- The types involved
floem.views.dropdown.DropdownCustomStyle→floem.style.Style
- Direction
- floem.views.dropdown uses floem.style, so a change to floem.style can break floem.views.dropdown, while a change to floem.views.dropdown can't break floem.style.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→34 floem.views.dropdown uses floem.message part of a loop✕
- Connections
- 1 pair of types, where a type in floem.views.dropdown uses a type in floem.message.
- The types involved
floem.views.dropdown.Dropdown→floem.message.UpdateCx
- Direction
- floem.views.dropdown uses floem.message, so a change to floem.message can break floem.views.dropdown, while a change to floem.views.dropdown can't break floem.message.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→36 floem.views.dropdown uses floem.event.dispatch part of a loop✕
- Connections
- 1 pair of types, where a type in floem.views.dropdown uses a type in floem.event.dispatch.
- The types involved
floem.views.dropdown.Dropdown→floem.event.dispatch.EventCx
- Direction
- floem.views.dropdown uses floem.event.dispatch, so a change to floem.event.dispatch can break floem.views.dropdown, while a change to floem.views.dropdown can't break floem.event.dispatch.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→37 floem.views.dropdown uses floem.view.id part of a loop✕
- Connections
- 1 pair of types, where a type in floem.views.dropdown uses a type in floem.view.id.
- The types involved
floem.views.dropdown.Dropdown→floem.view.id.ViewId
- Direction
- floem.views.dropdown uses floem.view.id, so a change to floem.view.id can break floem.views.dropdown, while a change to floem.views.dropdown can't break floem.view.id.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→2 floem.views.editor.view uses floem.event✕
- Connections
- 1 pair of types, where a type in floem.views.editor.view uses a type in floem.event.
- The types involved
floem.views.editor.view.EditorView→floem.event.EventPropagation
- Direction
- floem.views.editor.view uses floem.event, so a change to floem.event can break floem.views.editor.view, while a change to floem.views.editor.view can't break floem.event.
- Position
- Below the diagonal: floem.views.editor.view uses a module listed above it, which is the healthy direction.
18→3 floem.views.editor.view uses floem.style.props✕
- Connections
- 2 pairs of types, where a type in floem.views.editor.view uses a type in floem.style.props.
- The types involved
floem.views.editor.view.EditorViewClass→floem.style.props.StyleClassfloem.views.editor.view.EditorViewClass→floem.style.props.StyleKey
- Direction
- floem.views.editor.view uses floem.style.props, so a change to floem.style.props can break floem.views.editor.view, while a change to floem.views.editor.view can't break floem.style.props.
- Position
- Below the diagonal: floem.views.editor.view uses a module listed above it, which is the healthy direction.
18→6 floem.views.editor.view uses floem_editor_core.cursor✕
- Connections
- 3 pairs of types, where a type in floem.views.editor.view uses a type in floem_editor_core.cursor.
- The types involved
floem.views.editor.view.EditorView→floem_editor_core.cursor.ColPositionfloem.views.editor.view.EditorView→floem_editor_core.cursor.CursorAffinityfloem.views.editor.view.view$module→floem_editor_core.cursor.CursorAffinity
- Direction
- floem.views.editor.view uses floem_editor_core.cursor, so a change to floem_editor_core.cursor can break floem.views.editor.view, while a change to floem.views.editor.view can't break floem_editor_core.cursor.
- Position
- Below the diagonal: floem.views.editor.view uses a module listed above it, which is the healthy direction.
18→8 floem.views.editor.view uses floem.paint✕
- Connections
- 1 pair of types, where a type in floem.views.editor.view uses a type in floem.paint.
- The types involved
floem.views.editor.view.EditorView→floem.paint.PaintCx
- Direction
- floem.views.editor.view uses floem.paint, so a change to floem.paint can break floem.views.editor.view, while a change to floem.views.editor.view can't break floem.paint.
- Position
- Below the diagonal: floem.views.editor.view uses a module listed above it, which is the healthy direction.
18→10 floem.views.editor.view uses floem.view✕
- Connections
- 1 pair of types, where a type in floem.views.editor.view uses a type in floem.view.
- The types involved
floem.views.editor.view.EditorView→floem.view.View
- Direction
- floem.views.editor.view uses floem.view, so a change to floem.view can break floem.views.editor.view, while a change to floem.views.editor.view can't break floem.view.
- Position
- Below the diagonal: floem.views.editor.view uses a module listed above it, which is the healthy direction.
18→13 floem.views.editor.view uses floem_reactive.signal✕
- Connections
- 3 pairs of types, where a type in floem.views.editor.view uses a type in floem_reactive.signal.
- The types involved
floem.views.editor.view.EditorView→floem_reactive.signal.RwSignalfloem.views.editor.view.ScreenLines→floem_reactive.signal.RwSignalfloem.views.editor.view.view$module→floem_reactive.signal.RwSignal
- Direction
- floem.views.editor.view uses floem_reactive.signal, so a change to floem_reactive.signal can break floem.views.editor.view, while a change to floem.views.editor.view can't break floem_reactive.signal.
- Position
- Below the diagonal: floem.views.editor.view uses a module listed above it, which is the healthy direction.
18→15 floem.views.editor.view uses floem_reactive.scope✕
- Connections
- 1 pair of types, where a type in floem.views.editor.view uses a type in floem_reactive.scope.
- The types involved
floem.views.editor.view.ScreenLines→floem_reactive.scope.Scope
- Direction
- floem.views.editor.view uses floem_reactive.scope, so a change to floem_reactive.scope can break floem.views.editor.view, while a change to floem.views.editor.view can't break floem_reactive.scope.
- Position
- Below the diagonal: floem.views.editor.view uses a module listed above it, which is the healthy direction.
18→16 floem.views.editor.view uses floem.style.cx✕
- Connections
- 1 pair of types, where a type in floem.views.editor.view uses a type in floem.style.cx.
- The types involved
floem.views.editor.view.EditorView→floem.style.cx.StyleCx
- Direction
- floem.views.editor.view uses floem.style.cx, so a change to floem.style.cx can break floem.views.editor.view, while a change to floem.views.editor.view can't break floem.style.cx.
- Position
- Below the diagonal: floem.views.editor.view uses a module listed above it, which is the healthy direction.
18→22 floem.views.editor.view uses floem.views.editor part of a loop✕
- Connections
- 3 pairs of types, where a type in floem.views.editor.view uses a type in floem.views.editor.
- The types involved
floem.views.editor.view.EditorView→floem.views.editor.Editorfloem.views.editor.view.ScreenLines→floem.views.editor.Editorfloem.views.editor.view.view$module→floem.views.editor.Editor
- Direction
- floem.views.editor.view uses floem.views.editor, so a change to floem.views.editor can break floem.views.editor.view, while a change to floem.views.editor.view can't break floem.views.editor.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→34 floem.views.editor.view uses floem.message part of a loop✕
- Connections
- 1 pair of types, where a type in floem.views.editor.view uses a type in floem.message.
- The types involved
floem.views.editor.view.EditorView→floem.message.UpdateCx
- Direction
- floem.views.editor.view uses floem.message, so a change to floem.message can break floem.views.editor.view, while a change to floem.views.editor.view can't break floem.message.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→36 floem.views.editor.view uses floem.event.dispatch part of a loop✕
- Connections
- 1 pair of types, where a type in floem.views.editor.view uses a type in floem.event.dispatch.
- The types involved
floem.views.editor.view.EditorView→floem.event.dispatch.EventCx
- Direction
- floem.views.editor.view uses floem.event.dispatch, so a change to floem.event.dispatch can break floem.views.editor.view, while a change to floem.views.editor.view can't break floem.event.dispatch.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→37 floem.views.editor.view uses floem.view.id part of a loop✕
- Connections
- 1 pair of types, where a type in floem.views.editor.view uses a type in floem.view.id.
- The types involved
floem.views.editor.view.EditorView→floem.view.id.ViewId
- Direction
- floem.views.editor.view uses floem.view.id, so a change to floem.view.id can break floem.views.editor.view, while a change to floem.views.editor.view can't break floem.view.id.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→2 floem.views.resizable uses floem.event✕
- Connections
- 1 pair of types, where a type in floem.views.resizable uses a type in floem.event.
- The types involved
floem.views.resizable.Resizable→floem.event.EventPropagation
- Direction
- floem.views.resizable uses floem.event, so a change to floem.event can break floem.views.resizable, while a change to floem.views.resizable can't break floem.event.
- Position
- Below the diagonal: floem.views.resizable uses a module listed above it, which is the healthy direction.
19→3 floem.views.resizable uses floem.style.props✕
- Connections
- 5 pairs of types, where a type in floem.views.resizable uses a type in floem.style.props.
- The types involved
floem.views.resizable.Resizable→floem.style.props.StyleClassReffloem.views.resizable.ResizableClass→floem.style.props.StyleClassfloem.views.resizable.ResizableClass→floem.style.props.StyleKeyfloem.views.resizable.ResizableHandleClass→floem.style.props.StyleClassfloem.views.resizable.ResizableHandleClass→floem.style.props.StyleKey
- Direction
- floem.views.resizable uses floem.style.props, so a change to floem.style.props can break floem.views.resizable, while a change to floem.views.resizable can't break floem.style.props.
- Position
- Below the diagonal: floem.views.resizable uses a module listed above it, which is the healthy direction.
19→5 floem.views.resizable uses floem.style.values✕
- Connections
- 1 pair of types, where a type in floem.views.resizable uses a type in floem.style.values.
- The types involved
floem.views.resizable.ResizableCustomExprStyle→floem.style.values.ContextValue
- Direction
- floem.views.resizable uses floem.style.values, so a change to floem.style.values can break floem.views.resizable, while a change to floem.views.resizable can't break floem.style.values.
- Position
- Below the diagonal: floem.views.resizable uses a module listed above it, which is the healthy direction.
19→7 floem.views.resizable uses floem.style.unit✕
- Connections
- 1 pair of types, where a type in floem.views.resizable uses a type in floem.style.unit.
- The types involved
floem.views.resizable.ResizeChild→floem.style.unit.Pct
- Direction
- floem.views.resizable uses floem.style.unit, so a change to floem.style.unit can break floem.views.resizable, while a change to floem.views.resizable can't break floem.style.unit.
- Position
- Below the diagonal: floem.views.resizable uses a module listed above it, which is the healthy direction.
19→8 floem.views.resizable uses floem.paint✕
- Connections
- 2 pairs of types, where a type in floem.views.resizable uses a type in floem.paint.
- The types involved
floem.views.resizable.Handle→floem.paint.PaintCxfloem.views.resizable.Resizable→floem.paint.PaintCx
- Direction
- floem.views.resizable uses floem.paint, so a change to floem.paint can break floem.views.resizable, while a change to floem.views.resizable can't break floem.paint.
- Position
- Below the diagonal: floem.views.resizable uses a module listed above it, which is the healthy direction.
19→10 floem.views.resizable uses floem.view✕
- Connections
- 2 pairs of types, where a type in floem.views.resizable uses a type in floem.view.
- The types involved
floem.views.resizable.Resizable→floem.view.Viewfloem.views.resizable.ResizeChild→floem.view.View
- Direction
- floem.views.resizable uses floem.view, so a change to floem.view can break floem.views.resizable, while a change to floem.views.resizable can't break floem.view.
- Position
- Below the diagonal: floem.views.resizable uses a module listed above it, which is the healthy direction.
19→11 floem.views.resizable uses floem.style.custom✕
- Connections
- 2 pairs of types, where a type in floem.views.resizable uses a type in floem.style.custom.
- The types involved
floem.views.resizable.Resizable→floem.style.custom.CustomStylablefloem.views.resizable.ResizableCustomStyle→floem.style.custom.CustomStyle
- Direction
- floem.views.resizable uses floem.style.custom, so a change to floem.style.custom can break floem.views.resizable, while a change to floem.views.resizable can't break floem.style.custom.
- Position
- Below the diagonal: floem.views.resizable uses a module listed above it, which is the healthy direction.
19→16 floem.views.resizable uses floem.style.cx✕
- Connections
- 2 pairs of types, where a type in floem.views.resizable uses a type in floem.style.cx.
- The types involved
floem.views.resizable.Handle→floem.style.cx.StyleCxfloem.views.resizable.Resizable→floem.style.cx.StyleCx
- Direction
- floem.views.resizable uses floem.style.cx, so a change to floem.style.cx can break floem.views.resizable, while a change to floem.views.resizable can't break floem.style.cx.
- Position
- Below the diagonal: floem.views.resizable uses a module listed above it, which is the healthy direction.
19→30 floem.views.resizable uses floem.style part of a loop✕
- Connections
- 3 pairs of types, where a type in floem.views.resizable uses a type in floem.style.
- The types involved
floem.views.resizable.ResizableCustomExprStyle→floem.style.Stylefloem.views.resizable.ResizableCustomStyle→floem.style.Stylefloem.views.resizable.ResizeChild→floem.style.Style
- Direction
- floem.views.resizable uses floem.style, so a change to floem.style can break floem.views.resizable, while a change to floem.views.resizable can't break floem.style.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→34 floem.views.resizable uses floem.message part of a loop✕
- Connections
- 2 pairs of types, where a type in floem.views.resizable uses a type in floem.message.
- The types involved
floem.views.resizable.Resizable→floem.message.UpdateCxfloem.views.resizable.ResizeChild→floem.message.UpdateCx
- Direction
- floem.views.resizable uses floem.message, so a change to floem.message can break floem.views.resizable, while a change to floem.views.resizable can't break floem.message.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→36 floem.views.resizable uses floem.event.dispatch part of a loop✕
- Connections
- 2 pairs of types, where a type in floem.views.resizable uses a type in floem.event.dispatch.
- The types involved
floem.views.resizable.Handle→floem.event.dispatch.EventCxfloem.views.resizable.Resizable→floem.event.dispatch.EventCx
- Direction
- floem.views.resizable uses floem.event.dispatch, so a change to floem.event.dispatch can break floem.views.resizable, while a change to floem.views.resizable can't break floem.event.dispatch.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→37 floem.views.resizable uses floem.view.id part of a loop✕
- Connections
- 3 pairs of types, where a type in floem.views.resizable uses a type in floem.view.id.
- The types involved
floem.views.resizable.Handle→floem.view.id.ViewIdfloem.views.resizable.Resizable→floem.view.id.ViewIdfloem.views.resizable.ResizeChild→floem.view.id.ViewId
- Direction
- floem.views.resizable uses floem.view.id, so a change to floem.view.id can break floem.views.resizable, while a change to floem.views.resizable can't break floem.view.id.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→38 floem.views.resizable uses floem.box_tree part of a loop✕
- Connections
- 2 pairs of types, where a type in floem.views.resizable uses a type in floem.box_tree.
- The types involved
floem.views.resizable.Handle→floem.box_tree.BoxTreefloem.views.resizable.Handle→floem.box_tree.ElementId
- Direction
- floem.views.resizable uses floem.box_tree, so a change to floem.box_tree can break floem.views.resizable, while a change to floem.views.resizable can't break floem.box_tree.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→2 floem.views.scroll uses floem.event✕
- Connections
- 3 pairs of types, where a type in floem.views.scroll uses a type in floem.event.
- The types involved
floem.views.scroll.Scroll→floem.event.EventPropagationfloem.views.scroll.Scroll→floem.event.ScrollTofloem.views.scroll.ScrollEventResult→floem.event.EventPropagation
- Direction
- floem.views.scroll uses floem.event, so a change to floem.event can break floem.views.scroll, while a change to floem.views.scroll can't break floem.event.
- Position
- Below the diagonal: floem.views.scroll uses a module listed above it, which is the healthy direction.
20→3 floem.views.scroll uses floem.style.props✕
- Connections
- 6 pairs of types, where a type in floem.views.scroll uses a type in floem.style.props.
- The types involved
floem.views.scroll.Handle→floem.style.props.StyleClassfloem.views.scroll.Handle→floem.style.props.StyleKeyfloem.views.scroll.ScrollClass→floem.style.props.StyleClassfloem.views.scroll.ScrollClass→floem.style.props.StyleKeyfloem.views.scroll.Track→floem.style.props.StyleClassfloem.views.scroll.Track→floem.style.props.StyleKey
- Direction
- floem.views.scroll uses floem.style.props, so a change to floem.style.props can break floem.views.scroll, while a change to floem.views.scroll can't break floem.style.props.
- Position
- Below the diagonal: floem.views.scroll uses a module listed above it, which is the healthy direction.
20→8 floem.views.scroll uses floem.paint✕
- Connections
- 3 pairs of types, where a type in floem.views.scroll uses a type in floem.paint.
- The types involved
floem.views.scroll.Scroll→floem.paint.PaintCxfloem.views.scroll.ScrollHandle→floem.paint.PaintCxfloem.views.scroll.ScrollTrack→floem.paint.PaintCx
- Direction
- floem.views.scroll uses floem.paint, so a change to floem.paint can break floem.views.scroll, while a change to floem.views.scroll can't break floem.paint.
- Position
- Below the diagonal: floem.views.scroll uses a module listed above it, which is the healthy direction.
20→10 floem.views.scroll uses floem.view✕
- Connections
- 1 pair of types, where a type in floem.views.scroll uses a type in floem.view.
- The types involved
floem.views.scroll.Scroll→floem.view.View
- Direction
- floem.views.scroll uses floem.view, so a change to floem.view can break floem.views.scroll, while a change to floem.views.scroll can't break floem.view.
- Position
- Below the diagonal: floem.views.scroll uses a module listed above it, which is the healthy direction.
20→11 floem.views.scroll uses floem.style.custom✕
- Connections
- 2 pairs of types, where a type in floem.views.scroll uses a type in floem.style.custom.
- The types involved
floem.views.scroll.Scroll→floem.style.custom.CustomStylablefloem.views.scroll.ScrollCustomStyle→floem.style.custom.CustomStyle
- Direction
- floem.views.scroll uses floem.style.custom, so a change to floem.style.custom can break floem.views.scroll, while a change to floem.views.scroll can't break floem.style.custom.
- Position
- Below the diagonal: floem.views.scroll uses a module listed above it, which is the healthy direction.
20→16 floem.views.scroll uses floem.style.cx✕
- Connections
- 3 pairs of types, where a type in floem.views.scroll uses a type in floem.style.cx.
- The types involved
floem.views.scroll.Scroll→floem.style.cx.StyleCxfloem.views.scroll.ScrollHandle→floem.style.cx.StyleCxfloem.views.scroll.ScrollTrack→floem.style.cx.StyleCx
- Direction
- floem.views.scroll uses floem.style.cx, so a change to floem.style.cx can break floem.views.scroll, while a change to floem.views.scroll can't break floem.style.cx.
- Position
- Below the diagonal: floem.views.scroll uses a module listed above it, which is the healthy direction.
20→30 floem.views.scroll uses floem.style part of a loop✕
- Connections
- 2 pairs of types, where a type in floem.views.scroll uses a type in floem.style.
- The types involved
floem.views.scroll.Scroll→floem.style.Stylefloem.views.scroll.ScrollCustomStyle→floem.style.Style
- Direction
- floem.views.scroll uses floem.style, so a change to floem.style can break floem.views.scroll, while a change to floem.views.scroll can't break floem.style.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→34 floem.views.scroll uses floem.message part of a loop✕
- Connections
- 1 pair of types, where a type in floem.views.scroll uses a type in floem.message.
- The types involved
floem.views.scroll.Scroll→floem.message.UpdateCx
- Direction
- floem.views.scroll uses floem.message, so a change to floem.message can break floem.views.scroll, while a change to floem.views.scroll can't break floem.message.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→36 floem.views.scroll uses floem.event.dispatch part of a loop✕
- Connections
- 3 pairs of types, where a type in floem.views.scroll uses a type in floem.event.dispatch.
- The types involved
floem.views.scroll.Scroll→floem.event.dispatch.EventCxfloem.views.scroll.ScrollHandle→floem.event.dispatch.EventCxfloem.views.scroll.ScrollTrack→floem.event.dispatch.EventCx
- Direction
- floem.views.scroll uses floem.event.dispatch, so a change to floem.event.dispatch can break floem.views.scroll, while a change to floem.views.scroll can't break floem.event.dispatch.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→37 floem.views.scroll uses floem.view.id part of a loop✕
- Connections
- 3 pairs of types, where a type in floem.views.scroll uses a type in floem.view.id.
- The types involved
floem.views.scroll.Scroll→floem.view.id.ViewIdfloem.views.scroll.ScrollHandle→floem.view.id.ViewIdfloem.views.scroll.ScrollTrack→floem.view.id.ViewId
- Direction
- floem.views.scroll uses floem.view.id, so a change to floem.view.id can break floem.views.scroll, while a change to floem.views.scroll can't break floem.view.id.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→38 floem.views.scroll uses floem.box_tree part of a loop✕
- Connections
- 4 pairs of types, where a type in floem.views.scroll uses a type in floem.box_tree.
- The types involved
floem.views.scroll.ScrollHandle→floem.box_tree.BoxTreefloem.views.scroll.ScrollHandle→floem.box_tree.ElementIdfloem.views.scroll.ScrollTrack→floem.box_tree.BoxTreefloem.views.scroll.ScrollTrack→floem.box_tree.ElementId
- Direction
- floem.views.scroll uses floem.box_tree, so a change to floem.box_tree can break floem.views.scroll, while a change to floem.views.scroll can't break floem.box_tree.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
21→2 floem.views.slider uses floem.event✕
- Connections
- 1 pair of types, where a type in floem.views.slider uses a type in floem.event.
- The types involved
floem.views.slider.Slider→floem.event.EventPropagation
- Direction
- floem.views.slider uses floem.event, so a change to floem.event can break floem.views.slider, while a change to floem.views.slider can't break floem.event.
- Position
- Below the diagonal: floem.views.slider uses a module listed above it, which is the healthy direction.
21→3 floem.views.slider uses floem.style.props✕
- Connections
- 6 pairs of types, where a type in floem.views.slider uses a type in floem.style.props.
- The types involved
floem.views.slider.AccentBarClass→floem.style.props.StyleClassfloem.views.slider.AccentBarClass→floem.style.props.StyleKeyfloem.views.slider.BarClass→floem.style.props.StyleClassfloem.views.slider.BarClass→floem.style.props.StyleKeyfloem.views.slider.SliderClass→floem.style.props.StyleClassfloem.views.slider.SliderClass→floem.style.props.StyleKey
- Direction
- floem.views.slider uses floem.style.props, so a change to floem.style.props can break floem.views.slider, while a change to floem.views.slider can't break floem.style.props.
- Position
- Below the diagonal: floem.views.slider uses a module listed above it, which is the healthy direction.
21→5 floem.views.slider uses floem.style.values✕
- Connections
- 1 pair of types, where a type in floem.views.slider uses a type in floem.style.values.
- The types involved
floem.views.slider.SliderCustomExprStyle→floem.style.values.ContextValue
- Direction
- floem.views.slider uses floem.style.values, so a change to floem.style.values can break floem.views.slider, while a change to floem.views.slider can't break floem.style.values.
- Position
- Below the diagonal: floem.views.slider uses a module listed above it, which is the healthy direction.
21→7 floem.views.slider uses floem.style.unit✕
- Connections
- 2 pairs of types, where a type in floem.views.slider uses a type in floem.style.unit.
- The types involved
floem.views.slider.SliderState→floem.style.unit.Pctfloem.views.slider.slider$module→floem.style.unit.FontSizeCx
- Direction
- floem.views.slider uses floem.style.unit, so a change to floem.style.unit can break floem.views.slider, while a change to floem.views.slider can't break floem.style.unit.
- Position
- Below the diagonal: floem.views.slider uses a module listed above it, which is the healthy direction.
21→8 floem.views.slider uses floem.paint✕
- Connections
- 1 pair of types, where a type in floem.views.slider uses a type in floem.paint.
- The types involved
floem.views.slider.Slider→floem.paint.PaintCx
- Direction
- floem.views.slider uses floem.paint, so a change to floem.paint can break floem.views.slider, while a change to floem.views.slider can't break floem.paint.
- Position
- Below the diagonal: floem.views.slider uses a module listed above it, which is the healthy direction.
21→10 floem.views.slider uses floem.view✕
- Connections
- 1 pair of types, where a type in floem.views.slider uses a type in floem.view.
- The types involved
floem.views.slider.Slider→floem.view.View
- Direction
- floem.views.slider uses floem.view, so a change to floem.view can break floem.views.slider, while a change to floem.views.slider can't break floem.view.
- Position
- Below the diagonal: floem.views.slider uses a module listed above it, which is the healthy direction.
21→11 floem.views.slider uses floem.style.custom✕
- Connections
- 2 pairs of types, where a type in floem.views.slider uses a type in floem.style.custom.
- The types involved
floem.views.slider.Slider→floem.style.custom.CustomStylablefloem.views.slider.SliderCustomStyle→floem.style.custom.CustomStyle
- Direction
- floem.views.slider uses floem.style.custom, so a change to floem.style.custom can break floem.views.slider, while a change to floem.views.slider can't break floem.style.custom.
- Position
- Below the diagonal: floem.views.slider uses a module listed above it, which is the healthy direction.
21→16 floem.views.slider uses floem.style.cx✕
- Connections
- 1 pair of types, where a type in floem.views.slider uses a type in floem.style.cx.
- The types involved
floem.views.slider.Slider→floem.style.cx.StyleCx
- Direction
- floem.views.slider uses floem.style.cx, so a change to floem.style.cx can break floem.views.slider, while a change to floem.views.slider can't break floem.style.cx.
- Position
- Below the diagonal: floem.views.slider uses a module listed above it, which is the healthy direction.
21→30 floem.views.slider uses floem.style part of a loop✕
- Connections
- 2 pairs of types, where a type in floem.views.slider uses a type in floem.style.
- The types involved
floem.views.slider.SliderCustomExprStyle→floem.style.Stylefloem.views.slider.SliderCustomStyle→floem.style.Style
- Direction
- floem.views.slider uses floem.style, so a change to floem.style can break floem.views.slider, while a change to floem.views.slider can't break floem.style.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
21→34 floem.views.slider uses floem.message part of a loop✕
- Connections
- 1 pair of types, where a type in floem.views.slider uses a type in floem.message.
- The types involved
floem.views.slider.Slider→floem.message.UpdateCx
- Direction
- floem.views.slider uses floem.message, so a change to floem.message can break floem.views.slider, while a change to floem.views.slider can't break floem.message.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
21→36 floem.views.slider uses floem.event.dispatch part of a loop✕
- Connections
- 1 pair of types, where a type in floem.views.slider uses a type in floem.event.dispatch.
- The types involved
floem.views.slider.Slider→floem.event.dispatch.EventCx
- Direction
- floem.views.slider uses floem.event.dispatch, so a change to floem.event.dispatch can break floem.views.slider, while a change to floem.views.slider can't break floem.event.dispatch.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
21→37 floem.views.slider uses floem.view.id part of a loop✕
- Connections
- 1 pair of types, where a type in floem.views.slider uses a type in floem.view.id.
- The types involved
floem.views.slider.Slider→floem.view.id.ViewId
- Direction
- floem.views.slider uses floem.view.id, so a change to floem.view.id can break floem.views.slider, while a change to floem.views.slider can't break floem.view.id.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
22→1 floem.views.editor uses floem_editor_core.mode✕
- Connections
- 1 pair of types, where a type in floem.views.editor uses a type in floem_editor_core.mode.
- The types involved
floem.views.editor.Editor→floem_editor_core.mode.Mode
- Direction
- floem.views.editor uses floem_editor_core.mode, so a change to floem_editor_core.mode can break floem.views.editor, while a change to floem.views.editor can't break floem_editor_core.mode.
- Position
- Below the diagonal: floem.views.editor uses a module listed above it, which is the healthy direction.
22→6 floem.views.editor uses floem_editor_core.cursor✕
- Connections
- 2 pairs of types, where a type in floem.views.editor uses a type in floem_editor_core.cursor.
- The types involved
floem.views.editor.Editor→floem_editor_core.cursor.ColPositionfloem.views.editor.Editor→floem_editor_core.cursor.CursorAffinity
- Direction
- floem.views.editor uses floem_editor_core.cursor, so a change to floem_editor_core.cursor can break floem.views.editor, while a change to floem.views.editor can't break floem_editor_core.cursor.
- Position
- Below the diagonal: floem.views.editor uses a module listed above it, which is the healthy direction.
22→13 floem.views.editor uses floem_reactive.signal✕
- Connections
- 4 pairs of types, where a type in floem.views.editor uses a type in floem_reactive.signal.
- The types involved
floem.views.editor.CursorInfo→floem_reactive.signal.RwSignalfloem.views.editor.Editor→floem_reactive.signal.RwSignalfloem.views.editor.EditorFontSizes→floem_reactive.signal.ReadSignalfloem.views.editor.editor$module→floem_reactive.signal.RwSignal
- Direction
- floem.views.editor uses floem_reactive.signal, so a change to floem_reactive.signal can break floem.views.editor, while a change to floem.views.editor can't break floem_reactive.signal.
- Position
- Below the diagonal: floem.views.editor uses a module listed above it, which is the healthy direction.
22→15 floem.views.editor uses floem_reactive.scope✕
- Connections
- 3 pairs of types, where a type in floem.views.editor uses a type in floem_reactive.scope.
- The types involved
floem.views.editor.CursorInfo→floem_reactive.scope.Scopefloem.views.editor.Editor→floem_reactive.scope.Scopefloem.views.editor.editor$module→floem_reactive.scope.Scope
- Direction
- floem.views.editor uses floem_reactive.scope, so a change to floem_reactive.scope can break floem.views.editor, while a change to floem.views.editor can't break floem_reactive.scope.
- Position
- Below the diagonal: floem.views.editor uses a module listed above it, which is the healthy direction.
22→18 floem.views.editor uses floem.views.editor.view✕
- Connections
- 2 pairs of types, where a type in floem.views.editor uses a type in floem.views.editor.view.
- The types involved
floem.views.editor.Editor→floem.views.editor.view.ScreenLinesfloem.views.editor.editor$module→floem.views.editor.view.ScreenLines
- Direction
- floem.views.editor uses floem.views.editor.view, so a change to floem.views.editor.view can break floem.views.editor, while a change to floem.views.editor can't break floem.views.editor.view.
- Position
- Below the diagonal: floem.views.editor uses a module listed above it, which is the healthy direction.
22→27 floem.views.editor uses floem.views.editor.text part of a loop✕
- Connections
- 2 pairs of types, where a type in floem.views.editor uses a type in floem.views.editor.text.
- The types involved
floem.views.editor.Editor→floem.views.editor.text.PreeditDatafloem.views.editor.Editor→floem.views.editor.text.RenderWhitespace
- Direction
- floem.views.editor uses floem.views.editor.text, so a change to floem.views.editor.text can break floem.views.editor, while a change to floem.views.editor can't break floem.views.editor.text.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
23→2 floem.views.toggle_button uses floem.event✕
- Connections
- 1 pair of types, where a type in floem.views.toggle_button uses a type in floem.event.
- The types involved
floem.views.toggle_button.ToggleButton→floem.event.EventPropagation
- Direction
- floem.views.toggle_button uses floem.event, so a change to floem.event can break floem.views.toggle_button, while a change to floem.views.toggle_button can't break floem.event.
- Position
- Below the diagonal: floem.views.toggle_button uses a module listed above it, which is the healthy direction.
23→3 floem.views.toggle_button uses floem.style.props✕
- Connections
- 2 pairs of types, where a type in floem.views.toggle_button uses a type in floem.style.props.
- The types involved
floem.views.toggle_button.ToggleButtonClass→floem.style.props.StyleClassfloem.views.toggle_button.ToggleButtonClass→floem.style.props.StyleKey
- Direction
- floem.views.toggle_button uses floem.style.props, so a change to floem.style.props can break floem.views.toggle_button, while a change to floem.views.toggle_button can't break floem.style.props.
- Position
- Below the diagonal: floem.views.toggle_button uses a module listed above it, which is the healthy direction.
23→7 floem.views.toggle_button uses floem.style.unit✕
- Connections
- 1 pair of types, where a type in floem.views.toggle_button uses a type in floem.style.unit.
- The types involved
floem.views.toggle_button.ToggleButton→floem.style.unit.FontSizeCx
- Direction
- floem.views.toggle_button uses floem.style.unit, so a change to floem.style.unit can break floem.views.toggle_button, while a change to floem.views.toggle_button can't break floem.style.unit.
- Position
- Below the diagonal: floem.views.toggle_button uses a module listed above it, which is the healthy direction.
23→8 floem.views.toggle_button uses floem.paint✕
- Connections
- 2 pairs of types, where a type in floem.views.toggle_button uses a type in floem.paint.
- The types involved
floem.views.toggle_button.Handle→floem.paint.PaintCxfloem.views.toggle_button.ToggleButton→floem.paint.PaintCx
- Direction
- floem.views.toggle_button uses floem.paint, so a change to floem.paint can break floem.views.toggle_button, while a change to floem.views.toggle_button can't break floem.paint.
- Position
- Below the diagonal: floem.views.toggle_button uses a module listed above it, which is the healthy direction.
23→10 floem.views.toggle_button uses floem.view✕
- Connections
- 1 pair of types, where a type in floem.views.toggle_button uses a type in floem.view.
- The types involved
floem.views.toggle_button.ToggleButton→floem.view.View
- Direction
- floem.views.toggle_button uses floem.view, so a change to floem.view can break floem.views.toggle_button, while a change to floem.views.toggle_button can't break floem.view.
- Position
- Below the diagonal: floem.views.toggle_button uses a module listed above it, which is the healthy direction.
23→16 floem.views.toggle_button uses floem.style.cx✕
- Connections
- 1 pair of types, where a type in floem.views.toggle_button uses a type in floem.style.cx.
- The types involved
floem.views.toggle_button.ToggleButton→floem.style.cx.StyleCx
- Direction
- floem.views.toggle_button uses floem.style.cx, so a change to floem.style.cx can break floem.views.toggle_button, while a change to floem.views.toggle_button can't break floem.style.cx.
- Position
- Below the diagonal: floem.views.toggle_button uses a module listed above it, which is the healthy direction.
23→19 floem.views.toggle_button uses floem.views.resizable✕
- Connections
- 1 pair of types, where a type in floem.views.toggle_button uses a type in floem.views.resizable.
- The types involved
floem.views.toggle_button.ToggleButton→floem.views.resizable.Handle
- Direction
- floem.views.toggle_button uses floem.views.resizable, so a change to floem.views.resizable can break floem.views.toggle_button, while a change to floem.views.toggle_button can't break floem.views.resizable.
- Position
- Below the diagonal: floem.views.toggle_button uses a module listed above it, which is the healthy direction.
23→30 floem.views.toggle_button uses floem.style part of a loop✕
- Connections
- 2 pairs of types, where a type in floem.views.toggle_button uses a type in floem.style.
- The types involved
floem.views.toggle_button.ToggleButton→floem.style.Stylefloem.views.toggle_button.ToggleButtonCustomStyle→floem.style.Style
- Direction
- floem.views.toggle_button uses floem.style, so a change to floem.style can break floem.views.toggle_button, while a change to floem.views.toggle_button can't break floem.style.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
23→34 floem.views.toggle_button uses floem.message part of a loop✕
- Connections
- 1 pair of types, where a type in floem.views.toggle_button uses a type in floem.message.
- The types involved
floem.views.toggle_button.ToggleButton→floem.message.UpdateCx
- Direction
- floem.views.toggle_button uses floem.message, so a change to floem.message can break floem.views.toggle_button, while a change to floem.views.toggle_button can't break floem.message.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
23→36 floem.views.toggle_button uses floem.event.dispatch part of a loop✕
- Connections
- 2 pairs of types, where a type in floem.views.toggle_button uses a type in floem.event.dispatch.
- The types involved
floem.views.toggle_button.Handle→floem.event.dispatch.EventCxfloem.views.toggle_button.ToggleButton→floem.event.dispatch.EventCx
- Direction
- floem.views.toggle_button uses floem.event.dispatch, so a change to floem.event.dispatch can break floem.views.toggle_button, while a change to floem.views.toggle_button can't break floem.event.dispatch.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
23→37 floem.views.toggle_button uses floem.view.id part of a loop✕
- Connections
- 2 pairs of types, where a type in floem.views.toggle_button uses a type in floem.view.id.
- The types involved
floem.views.toggle_button.Handle→floem.view.id.ViewIdfloem.views.toggle_button.ToggleButton→floem.view.id.ViewId
- Direction
- floem.views.toggle_button uses floem.view.id, so a change to floem.view.id can break floem.views.toggle_button, while a change to floem.views.toggle_button can't break floem.view.id.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
23→38 floem.views.toggle_button uses floem.box_tree part of a loop✕
- Connections
- 2 pairs of types, where a type in floem.views.toggle_button uses a type in floem.box_tree.
- The types involved
floem.views.toggle_button.Handle→floem.box_tree.BoxTreefloem.views.toggle_button.Handle→floem.box_tree.ElementId
- Direction
- floem.views.toggle_button uses floem.box_tree, so a change to floem.box_tree can break floem.views.toggle_button, while a change to floem.views.toggle_button can't break floem.box_tree.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
24→1 floem.views.editor.actions uses floem_editor_core.mode✕
- Connections
- 1 pair of types, where a type in floem.views.editor.actions uses a type in floem_editor_core.mode.
- The types involved
floem.views.editor.actions.CommonAction→floem_editor_core.mode.MotionMode
- Direction
- floem.views.editor.actions uses floem_editor_core.mode, so a change to floem_editor_core.mode can break floem.views.editor.actions, while a change to floem.views.editor.actions can't break floem_editor_core.mode.
- Position
- Below the diagonal: floem.views.editor.actions uses a module listed above it, which is the healthy direction.
24→6 floem.views.editor.actions uses floem_editor_core.cursor✕
- Connections
- 1 pair of types, where a type in floem.views.editor.actions uses a type in floem_editor_core.cursor.
- The types involved
floem.views.editor.actions.CommonAction→floem_editor_core.cursor.Cursor
- Direction
- floem.views.editor.actions uses floem_editor_core.cursor, so a change to floem_editor_core.cursor can break floem.views.editor.actions, while a change to floem.views.editor.actions can't break floem_editor_core.cursor.
- Position
- Below the diagonal: floem.views.editor.actions uses a module listed above it, which is the healthy direction.
24→22 floem.views.editor.actions uses floem.views.editor✕
- Connections
- 2 pairs of types, where a type in floem.views.editor.actions uses a type in floem.views.editor.
- The types involved
floem.views.editor.actions.CommonAction→floem.views.editor.Editorfloem.views.editor.actions.actions$module→floem.views.editor.Editor
- Direction
- floem.views.editor.actions uses floem.views.editor, so a change to floem.views.editor can break floem.views.editor.actions, while a change to floem.views.editor.actions can't break floem.views.editor.
- Position
- Below the diagonal: floem.views.editor.actions uses a module listed above it, which is the healthy direction.
25→1 floem.views.editor.text_document uses floem_editor_core.mode✕
- Connections
- 1 pair of types, where a type in floem.views.editor.text_document uses a type in floem_editor_core.mode.
- The types involved
floem.views.editor.text_document.TextDocument→floem_editor_core.mode.MotionMode
- Direction
- floem.views.editor.text_document uses floem_editor_core.mode, so a change to floem_editor_core.mode can break floem.views.editor.text_document, while a change to floem.views.editor.text_document can't break floem_editor_core.mode.
- Position
- Below the diagonal: floem.views.editor.text_document uses a module listed above it, which is the healthy direction.
25→6 floem.views.editor.text_document uses floem_editor_core.cursor✕
- Connections
- 1 pair of types, where a type in floem.views.editor.text_document uses a type in floem_editor_core.cursor.
- The types involved
floem.views.editor.text_document.TextDocument→floem_editor_core.cursor.Cursor
- Direction
- floem.views.editor.text_document uses floem_editor_core.cursor, so a change to floem_editor_core.cursor can break floem.views.editor.text_document, while a change to floem.views.editor.text_document can't break floem_editor_core.cursor.
- Position
- Below the diagonal: floem.views.editor.text_document uses a module listed above it, which is the healthy direction.
25→13 floem.views.editor.text_document uses floem_reactive.signal✕
- Connections
- 1 pair of types, where a type in floem.views.editor.text_document uses a type in floem_reactive.signal.
- The types involved
floem.views.editor.text_document.TextDocument→floem_reactive.signal.RwSignal
- Direction
- floem.views.editor.text_document uses floem_reactive.signal, so a change to floem_reactive.signal can break floem.views.editor.text_document, while a change to floem.views.editor.text_document can't break floem_reactive.signal.
- Position
- Below the diagonal: floem.views.editor.text_document uses a module listed above it, which is the healthy direction.
25→15 floem.views.editor.text_document uses floem_reactive.scope✕
- Connections
- 1 pair of types, where a type in floem.views.editor.text_document uses a type in floem_reactive.scope.
- The types involved
floem.views.editor.text_document.TextDocument→floem_reactive.scope.Scope
- Direction
- floem.views.editor.text_document uses floem_reactive.scope, so a change to floem_reactive.scope can break floem.views.editor.text_document, while a change to floem.views.editor.text_document can't break floem_reactive.scope.
- Position
- Below the diagonal: floem.views.editor.text_document uses a module listed above it, which is the healthy direction.
25→22 floem.views.editor.text_document uses floem.views.editor✕
- Connections
- 3 pairs of types, where a type in floem.views.editor.text_document uses a type in floem.views.editor.
- The types involved
floem.views.editor.text_document.OnUpdate→floem.views.editor.Editorfloem.views.editor.text_document.PreCommand→floem.views.editor.Editorfloem.views.editor.text_document.TextDocument→floem.views.editor.Editor
- Direction
- floem.views.editor.text_document uses floem.views.editor, so a change to floem.views.editor can break floem.views.editor.text_document, while a change to floem.views.editor.text_document can't break floem.views.editor.
- Position
- Below the diagonal: floem.views.editor.text_document uses a module listed above it, which is the healthy direction.
25→24 floem.views.editor.text_document uses floem.views.editor.actions✕
- Connections
- 1 pair of types, where a type in floem.views.editor.text_document uses a type in floem.views.editor.actions.
- The types involved
floem.views.editor.text_document.TextDocument→floem.views.editor.actions.CommonAction
- Direction
- floem.views.editor.text_document uses floem.views.editor.actions, so a change to floem.views.editor.actions can break floem.views.editor.text_document, while a change to floem.views.editor.text_document can't break floem.views.editor.actions.
- Position
- Below the diagonal: floem.views.editor.text_document uses a module listed above it, which is the healthy direction.
25→27 floem.views.editor.text_document uses floem.views.editor.text part of a loop✕
- Connections
- 3 pairs of types, where a type in floem.views.editor.text_document uses a type in floem.views.editor.text.
- The types involved
floem.views.editor.text_document.TextDocument→floem.views.editor.text.Documentfloem.views.editor.text_document.TextDocument→floem.views.editor.text.DocumentPhantomfloem.views.editor.text_document.TextDocument→floem.views.editor.text.PreeditData
- Direction
- floem.views.editor.text_document uses floem.views.editor.text, so a change to floem.views.editor.text can break floem.views.editor.text_document, while a change to floem.views.editor.text_document can't break floem.views.editor.text.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
26→8 floem.views.text_editor uses floem.paint✕
- Connections
- 1 pair of types, where a type in floem.views.text_editor uses a type in floem.paint.
- The types involved
floem.views.text_editor.TextEditor→floem.paint.PaintCx
- Direction
- floem.views.text_editor uses floem.paint, so a change to floem.paint can break floem.views.text_editor, while a change to floem.views.text_editor can't break floem.paint.
- Position
- Below the diagonal: floem.views.text_editor uses a module listed above it, which is the healthy direction.
26→10 floem.views.text_editor uses floem.view✕
- Connections
- 1 pair of types, where a type in floem.views.text_editor uses a type in floem.view.
- The types involved
floem.views.text_editor.TextEditor→floem.view.View
- Direction
- floem.views.text_editor uses floem.view, so a change to floem.view can break floem.views.text_editor, while a change to floem.views.text_editor can't break floem.view.
- Position
- Below the diagonal: floem.views.text_editor uses a module listed above it, which is the healthy direction.
26→15 floem.views.text_editor uses floem_reactive.scope✕
- Connections
- 1 pair of types, where a type in floem.views.text_editor uses a type in floem_reactive.scope.
- The types involved
floem.views.text_editor.TextEditor→floem_reactive.scope.Scope
- Direction
- floem.views.text_editor uses floem_reactive.scope, so a change to floem_reactive.scope can break floem.views.text_editor, while a change to floem.views.text_editor can't break floem_reactive.scope.
- Position
- Below the diagonal: floem.views.text_editor uses a module listed above it, which is the healthy direction.
26→22 floem.views.text_editor uses floem.views.editor✕
- Connections
- 1 pair of types, where a type in floem.views.text_editor uses a type in floem.views.editor.
- The types involved
floem.views.text_editor.TextEditor→floem.views.editor.Editor
- Direction
- floem.views.text_editor uses floem.views.editor, so a change to floem.views.editor can break floem.views.text_editor, while a change to floem.views.text_editor can't break floem.views.editor.
- Position
- Below the diagonal: floem.views.text_editor uses a module listed above it, which is the healthy direction.
26→25 floem.views.text_editor uses floem.views.editor.text_document✕
- Connections
- 1 pair of types, where a type in floem.views.text_editor uses a type in floem.views.editor.text_document.
- The types involved
floem.views.text_editor.TextEditor→floem.views.editor.text_document.TextDocument
- Direction
- floem.views.text_editor uses floem.views.editor.text_document, so a change to floem.views.editor.text_document can break floem.views.text_editor, while a change to floem.views.text_editor can't break floem.views.editor.text_document.
- Position
- Below the diagonal: floem.views.text_editor uses a module listed above it, which is the healthy direction.
26→27 floem.views.text_editor uses floem.views.editor.text part of a loop✕
- Connections
- 2 pairs of types, where a type in floem.views.text_editor uses a type in floem.views.editor.text.
- The types involved
floem.views.text_editor.EditorCustomStyle→floem.views.editor.text.RenderWhitespacefloem.views.text_editor.EditorCustomStyle→floem.views.editor.text.WrapMethod
- Direction
- floem.views.text_editor uses floem.views.editor.text, so a change to floem.views.editor.text can break floem.views.text_editor, while a change to floem.views.text_editor can't break floem.views.editor.text.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
26→30 floem.views.text_editor uses floem.style part of a loop✕
- Connections
- 2 pairs of types, where a type in floem.views.text_editor uses a type in floem.style.
- The types involved
floem.views.text_editor.EditorCustomStyle→floem.style.Stylefloem.views.text_editor.TextEditor→floem.style.Style
- Direction
- floem.views.text_editor uses floem.style, so a change to floem.style can break floem.views.text_editor, while a change to floem.views.text_editor can't break floem.style.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
26→37 floem.views.text_editor uses floem.view.id part of a loop✕
- Connections
- 1 pair of types, where a type in floem.views.text_editor uses a type in floem.view.id.
- The types involved
floem.views.text_editor.TextEditor→floem.view.id.ViewId
- Direction
- floem.views.text_editor uses floem.view.id, so a change to floem.view.id can break floem.views.text_editor, while a change to floem.views.text_editor can't break floem.view.id.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
27→1 floem.views.editor.text uses floem_editor_core.mode✕
- Connections
- 1 pair of types, where a type in floem.views.editor.text uses a type in floem_editor_core.mode.
- The types involved
floem.views.editor.text.ExtCmdDocument→floem_editor_core.mode.MotionMode
- Direction
- floem.views.editor.text uses floem_editor_core.mode, so a change to floem_editor_core.mode can break floem.views.editor.text, while a change to floem.views.editor.text can't break floem_editor_core.mode.
- Position
- Below the diagonal: floem.views.editor.text uses a module listed above it, which is the healthy direction.
27→5 floem.views.editor.text uses floem.style.values✕
- Connections
- 2 pairs of types, where a type in floem.views.editor.text uses a type in floem.style.values.
- The types involved
floem.views.editor.text.RenderWhitespace→floem.style.values.StylePropValuefloem.views.editor.text.WrapMethod→floem.style.values.StylePropValue
- Direction
- floem.views.editor.text uses floem.style.values, so a change to floem.style.values can break floem.views.editor.text, while a change to floem.views.editor.text can't break floem.style.values.
- Position
- Below the diagonal: floem.views.editor.text uses a module listed above it, which is the healthy direction.
27→6 floem.views.editor.text uses floem_editor_core.cursor✕
- Connections
- 1 pair of types, where a type in floem.views.editor.text uses a type in floem_editor_core.cursor.
- The types involved
floem.views.editor.text.ExtCmdDocument→floem_editor_core.cursor.Cursor
- Direction
- floem.views.editor.text uses floem_editor_core.cursor, so a change to floem_editor_core.cursor can break floem.views.editor.text, while a change to floem.views.editor.text can't break floem_editor_core.cursor.
- Position
- Below the diagonal: floem.views.editor.text uses a module listed above it, which is the healthy direction.
27→9 floem.views.editor.text uses floem_renderer.text.attrs✕
- Connections
- 6 pairs of types, where a type in floem.views.editor.text uses a type in floem_renderer.text.attrs.
- The types involved
floem.views.editor.text.SimpleStyling→floem_renderer.text.attrs.Attrsfloem.views.editor.text.SimpleStyling→floem_renderer.text.attrs.AttrsListfloem.views.editor.text.SimpleStyling→floem_renderer.text.attrs.FamilyOwnedfloem.views.editor.text.SimpleStylingBuilder→floem_renderer.text.attrs.FamilyOwnedfloem.views.editor.text.Styling→floem_renderer.text.attrs.Attrsfloem.views.editor.text.Styling→floem_renderer.text.attrs.AttrsList
- Direction
- floem.views.editor.text uses floem_renderer.text.attrs, so a change to floem_renderer.text.attrs can break floem.views.editor.text, while a change to floem.views.editor.text can't break floem_renderer.text.attrs.
- Position
- Below the diagonal: floem.views.editor.text uses a module listed above it, which is the healthy direction.
27→13 floem.views.editor.text uses floem_reactive.signal✕
- Connections
- 3 pairs of types, where a type in floem.views.editor.text uses a type in floem_reactive.signal.
- The types involved
floem.views.editor.text.Document→floem_reactive.signal.RwSignalfloem.views.editor.text.ExtCmdDocument→floem_reactive.signal.RwSignalfloem.views.editor.text.PreeditData→floem_reactive.signal.RwSignal
- Direction
- floem.views.editor.text uses floem_reactive.signal, so a change to floem_reactive.signal can break floem.views.editor.text, while a change to floem.views.editor.text can't break floem_reactive.signal.
- Position
- Below the diagonal: floem.views.editor.text uses a module listed above it, which is the healthy direction.
27→15 floem.views.editor.text uses floem_reactive.scope✕
- Connections
- 1 pair of types, where a type in floem.views.editor.text uses a type in floem_reactive.scope.
- The types involved
floem.views.editor.text.PreeditData→floem_reactive.scope.Scope
- Direction
- floem.views.editor.text uses floem_reactive.scope, so a change to floem_reactive.scope can break floem.views.editor.text, while a change to floem.views.editor.text can't break floem_reactive.scope.
- Position
- Below the diagonal: floem.views.editor.text uses a module listed above it, which is the healthy direction.
27→18 floem.views.editor.text uses floem.views.editor.view✕
- Connections
- 2 pairs of types, where a type in floem.views.editor.text uses a type in floem.views.editor.view.
- The types involved
floem.views.editor.text.Document→floem.views.editor.view.ScreenLinesfloem.views.editor.text.ExtCmdDocument→floem.views.editor.view.ScreenLines
- Direction
- floem.views.editor.text uses floem.views.editor.view, so a change to floem.views.editor.view can break floem.views.editor.text, while a change to floem.views.editor.text can't break floem.views.editor.view.
- Position
- Below the diagonal: floem.views.editor.text uses a module listed above it, which is the healthy direction.
27→22 floem.views.editor.text uses floem.views.editor✕
- Connections
- 2 pairs of types, where a type in floem.views.editor.text uses a type in floem.views.editor.
- The types involved
floem.views.editor.text.Document→floem.views.editor.Editorfloem.views.editor.text.ExtCmdDocument→floem.views.editor.Editor
- Direction
- floem.views.editor.text uses floem.views.editor, so a change to floem.views.editor can break floem.views.editor.text, while a change to floem.views.editor.text can't break floem.views.editor.
- Position
- Below the diagonal: floem.views.editor.text uses a module listed above it, which is the healthy direction.
27→24 floem.views.editor.text uses floem.views.editor.actions✕
- Connections
- 1 pair of types, where a type in floem.views.editor.text uses a type in floem.views.editor.actions.
- The types involved
floem.views.editor.text.ExtCmdDocument→floem.views.editor.actions.CommonAction
- Direction
- floem.views.editor.text uses floem.views.editor.actions, so a change to floem.views.editor.actions can break floem.views.editor.text, while a change to floem.views.editor.text can't break floem.views.editor.actions.
- Position
- Below the diagonal: floem.views.editor.text uses a module listed above it, which is the healthy direction.
27→26 floem.views.editor.text uses floem.views.text_editor✕
- Connections
- 1 pair of types, where a type in floem.views.editor.text uses a type in floem.views.text_editor.
- The types involved
floem.views.editor.text.text$module→floem.views.text_editor.EditorCustomStyle
- Direction
- floem.views.editor.text uses floem.views.text_editor, so a change to floem.views.text_editor can break floem.views.editor.text, while a change to floem.views.editor.text can't break floem.views.text_editor.
- Position
- Below the diagonal: floem.views.editor.text uses a module listed above it, which is the healthy direction.
28→2 floem.views.text_input uses floem.event✕
- Connections
- 1 pair of types, where a type in floem.views.text_input uses a type in floem.event.
- The types involved
floem.views.text_input.TextInput→floem.event.EventPropagation
- Direction
- floem.views.text_input uses floem.event, so a change to floem.event can break floem.views.text_input, while a change to floem.views.text_input can't break floem.event.
- Position
- Below the diagonal: floem.views.text_input uses a module listed above it, which is the healthy direction.
28→3 floem.views.text_input uses floem.style.props✕
- Connections
- 4 pairs of types, where a type in floem.views.text_input uses a type in floem.style.props.
- The types involved
floem.views.text_input.PlaceholderTextClass→floem.style.props.StyleClassfloem.views.text_input.PlaceholderTextClass→floem.style.props.StyleKeyfloem.views.text_input.TextInputClass→floem.style.props.StyleClassfloem.views.text_input.TextInputClass→floem.style.props.StyleKey
- Direction
- floem.views.text_input uses floem.style.props, so a change to floem.style.props can break floem.views.text_input, while a change to floem.views.text_input can't break floem.style.props.
- Position
- Below the diagonal: floem.views.text_input uses a module listed above it, which is the healthy direction.
28→6 floem.views.text_input uses floem_editor_core.cursor✕
- Connections
- 1 pair of types, where a type in floem.views.text_input uses a type in floem_editor_core.cursor.
- The types involved
floem.views.text_input.TextInput→floem_editor_core.cursor.Cursor
- Direction
- floem.views.text_input uses floem_editor_core.cursor, so a change to floem_editor_core.cursor can break floem.views.text_input, while a change to floem.views.text_input can't break floem_editor_core.cursor.
- Position
- Below the diagonal: floem.views.text_input uses a module listed above it, which is the healthy direction.
28→8 floem.views.text_input uses floem.paint✕
- Connections
- 1 pair of types, where a type in floem.views.text_input uses a type in floem.paint.
- The types involved
floem.views.text_input.TextInput→floem.paint.PaintCx
- Direction
- floem.views.text_input uses floem.paint, so a change to floem.paint can break floem.views.text_input, while a change to floem.views.text_input can't break floem.paint.
- Position
- Below the diagonal: floem.views.text_input uses a module listed above it, which is the healthy direction.
28→9 floem.views.text_input uses floem_renderer.text.attrs✕
- Connections
- 1 pair of types, where a type in floem.views.text_input uses a type in floem_renderer.text.attrs.
- The types involved
floem.views.text_input.TextInput→floem_renderer.text.attrs.AttrsList
- Direction
- floem.views.text_input uses floem_renderer.text.attrs, so a change to floem_renderer.text.attrs can break floem.views.text_input, while a change to floem.views.text_input can't break floem_renderer.text.attrs.
- Position
- Below the diagonal: floem.views.text_input uses a module listed above it, which is the healthy direction.
28→10 floem.views.text_input uses floem.view✕
- Connections
- 1 pair of types, where a type in floem.views.text_input uses a type in floem.view.
- The types involved
floem.views.text_input.TextInput→floem.view.View
- Direction
- floem.views.text_input uses floem.view, so a change to floem.view can break floem.views.text_input, while a change to floem.views.text_input can't break floem.view.
- Position
- Below the diagonal: floem.views.text_input uses a module listed above it, which is the healthy direction.
28→13 floem.views.text_input uses floem_reactive.signal✕
- Connections
- 3 pairs of types, where a type in floem.views.text_input uses a type in floem_reactive.signal.
- The types involved
floem.views.text_input.BufferState→floem_reactive.signal.RwSignalfloem.views.text_input.TextInput→floem_reactive.signal.RwSignalfloem.views.text_input.text_input$module→floem_reactive.signal.RwSignal
- Direction
- floem.views.text_input uses floem_reactive.signal, so a change to floem_reactive.signal can break floem.views.text_input, while a change to floem.views.text_input can't break floem_reactive.signal.
- Position
- Below the diagonal: floem.views.text_input uses a module listed above it, which is the healthy direction.
28→16 floem.views.text_input uses floem.style.cx✕
- Connections
- 1 pair of types, where a type in floem.views.text_input uses a type in floem.style.cx.
- The types involved
floem.views.text_input.TextInput→floem.style.cx.StyleCx
- Direction
- floem.views.text_input uses floem.style.cx, so a change to floem.style.cx can break floem.views.text_input, while a change to floem.views.text_input can't break floem.style.cx.
- Position
- Below the diagonal: floem.views.text_input uses a module listed above it, which is the healthy direction.
28→27 floem.views.text_input uses floem.views.editor.text✕
- Connections
- 1 pair of types, where a type in floem.views.text_input uses a type in floem.views.editor.text.
- The types involved
floem.views.text_input.TextInput→floem.views.editor.text.Preedit
- Direction
- floem.views.text_input uses floem.views.editor.text, so a change to floem.views.editor.text can break floem.views.text_input, while a change to floem.views.text_input can't break floem.views.editor.text.
- Position
- Below the diagonal: floem.views.text_input uses a module listed above it, which is the healthy direction.
28→33 floem.views.text_input uses floem.window.state part of a loop✕
- Connections
- 1 pair of types, where a type in floem.views.text_input uses a type in floem.window.state.
- The types involved
floem.views.text_input.TextInput→floem.window.state.WindowState
- Direction
- floem.views.text_input uses floem.window.state, so a change to floem.window.state can break floem.views.text_input, while a change to floem.views.text_input can't break floem.window.state.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
28→34 floem.views.text_input uses floem.message part of a loop✕
- Connections
- 1 pair of types, where a type in floem.views.text_input uses a type in floem.message.
- The types involved
floem.views.text_input.TextInput→floem.message.UpdateCx
- Direction
- floem.views.text_input uses floem.message, so a change to floem.message can break floem.views.text_input, while a change to floem.views.text_input can't break floem.message.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
28→36 floem.views.text_input uses floem.event.dispatch part of a loop✕
- Connections
- 1 pair of types, where a type in floem.views.text_input uses a type in floem.event.dispatch.
- The types involved
floem.views.text_input.TextInput→floem.event.dispatch.EventCx
- Direction
- floem.views.text_input uses floem.event.dispatch, so a change to floem.event.dispatch can break floem.views.text_input, while a change to floem.views.text_input can't break floem.event.dispatch.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
28→37 floem.views.text_input uses floem.view.id part of a loop✕
- Connections
- 1 pair of types, where a type in floem.views.text_input uses a type in floem.view.id.
- The types involved
floem.views.text_input.TextInput→floem.view.id.ViewId
- Direction
- floem.views.text_input uses floem.view.id, so a change to floem.view.id can break floem.views.text_input, while a change to floem.views.text_input can't break floem.view.id.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
29→2 floem.views.label uses floem.event✕
- Connections
- 1 pair of types, where a type in floem.views.label uses a type in floem.event.
- The types involved
floem.views.label.Label→floem.event.EventPropagation
- Direction
- floem.views.label uses floem.event, so a change to floem.event can break floem.views.label, while a change to floem.views.label can't break floem.event.
- Position
- Below the diagonal: floem.views.label uses a module listed above it, which is the healthy direction.
29→3 floem.views.label uses floem.style.props✕
- Connections
- 2 pairs of types, where a type in floem.views.label uses a type in floem.style.props.
- The types involved
floem.views.label.LabelClass→floem.style.props.StyleClassfloem.views.label.LabelClass→floem.style.props.StyleKey
- Direction
- floem.views.label uses floem.style.props, so a change to floem.style.props can break floem.views.label, while a change to floem.views.label can't break floem.style.props.
- Position
- Below the diagonal: floem.views.label uses a module listed above it, which is the healthy direction.
29→5 floem.views.label uses floem.style.values✕
- Connections
- 1 pair of types, where a type in floem.views.label uses a type in floem.style.values.
- The types involved
floem.views.label.LabelCustomExprStyle→floem.style.values.ContextValue
- Direction
- floem.views.label uses floem.style.values, so a change to floem.style.values can break floem.views.label, while a change to floem.views.label can't break floem.style.values.
- Position
- Below the diagonal: floem.views.label uses a module listed above it, which is the healthy direction.
29→6 floem.views.label uses floem_editor_core.cursor✕
- Connections
- 1 pair of types, where a type in floem.views.label uses a type in floem_editor_core.cursor.
- The types involved
floem.views.label.Label→floem_editor_core.cursor.Cursor
- Direction
- floem.views.label uses floem_editor_core.cursor, so a change to floem_editor_core.cursor can break floem.views.label, while a change to floem.views.label can't break floem_editor_core.cursor.
- Position
- Below the diagonal: floem.views.label uses a module listed above it, which is the healthy direction.
29→8 floem.views.label uses floem.paint✕
- Connections
- 1 pair of types, where a type in floem.views.label uses a type in floem.paint.
- The types involved
floem.views.label.Label→floem.paint.PaintCx
- Direction
- floem.views.label uses floem.paint, so a change to floem.paint can break floem.views.label, while a change to floem.views.label can't break floem.paint.
- Position
- Below the diagonal: floem.views.label uses a module listed above it, which is the healthy direction.
29→9 floem.views.label uses floem_renderer.text.attrs✕
- Connections
- 1 pair of types, where a type in floem.views.label uses a type in floem_renderer.text.attrs.
- The types involved
floem.views.label.Label→floem_renderer.text.attrs.AttrsList
- Direction
- floem.views.label uses floem_renderer.text.attrs, so a change to floem_renderer.text.attrs can break floem.views.label, while a change to floem.views.label can't break floem_renderer.text.attrs.
- Position
- Below the diagonal: floem.views.label uses a module listed above it, which is the healthy direction.
29→10 floem.views.label uses floem.view✕
- Connections
- 1 pair of types, where a type in floem.views.label uses a type in floem.view.
- The types involved
floem.views.label.Label→floem.view.View
- Direction
- floem.views.label uses floem.view, so a change to floem.view can break floem.views.label, while a change to floem.views.label can't break floem.view.
- Position
- Below the diagonal: floem.views.label uses a module listed above it, which is the healthy direction.
29→11 floem.views.label uses floem.style.custom✕
- Connections
- 2 pairs of types, where a type in floem.views.label uses a type in floem.style.custom.
- The types involved
floem.views.label.Label→floem.style.custom.CustomStylablefloem.views.label.LabelCustomStyle→floem.style.custom.CustomStyle
- Direction
- floem.views.label uses floem.style.custom, so a change to floem.style.custom can break floem.views.label, while a change to floem.views.label can't break floem.style.custom.
- Position
- Below the diagonal: floem.views.label uses a module listed above it, which is the healthy direction.
29→16 floem.views.label uses floem.style.cx✕
- Connections
- 1 pair of types, where a type in floem.views.label uses a type in floem.style.cx.
- The types involved
floem.views.label.Label→floem.style.cx.StyleCx
- Direction
- floem.views.label uses floem.style.cx, so a change to floem.style.cx can break floem.views.label, while a change to floem.views.label can't break floem.style.cx.
- Position
- Below the diagonal: floem.views.label uses a module listed above it, which is the healthy direction.
29→28 floem.views.label uses floem.views.text_input✕
- Connections
- 1 pair of types, where a type in floem.views.label uses a type in floem.views.text_input.
- The types involved
floem.views.label.Label→floem.views.text_input.TextCommand
- Direction
- floem.views.label uses floem.views.text_input, so a change to floem.views.text_input can break floem.views.label, while a change to floem.views.label can't break floem.views.text_input.
- Position
- Below the diagonal: floem.views.label uses a module listed above it, which is the healthy direction.
29→30 floem.views.label uses floem.style part of a loop✕
- Connections
- 3 pairs of types, where a type in floem.views.label uses a type in floem.style.
- The types involved
floem.views.label.Label→floem.style.Stylefloem.views.label.LabelCustomExprStyle→floem.style.Stylefloem.views.label.LabelCustomStyle→floem.style.Style
- Direction
- floem.views.label uses floem.style, so a change to floem.style can break floem.views.label, while a change to floem.views.label can't break floem.style.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
29→34 floem.views.label uses floem.message part of a loop✕
- Connections
- 1 pair of types, where a type in floem.views.label uses a type in floem.message.
- The types involved
floem.views.label.Label→floem.message.UpdateCx
- Direction
- floem.views.label uses floem.message, so a change to floem.message can break floem.views.label, while a change to floem.views.label can't break floem.message.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
29→36 floem.views.label uses floem.event.dispatch part of a loop✕
- Connections
- 1 pair of types, where a type in floem.views.label uses a type in floem.event.dispatch.
- The types involved
floem.views.label.Label→floem.event.dispatch.EventCx
- Direction
- floem.views.label uses floem.event.dispatch, so a change to floem.event.dispatch can break floem.views.label, while a change to floem.views.label can't break floem.event.dispatch.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
29→37 floem.views.label uses floem.view.id part of a loop✕
- Connections
- 1 pair of types, where a type in floem.views.label uses a type in floem.view.id.
- The types involved
floem.views.label.Label→floem.view.id.ViewId
- Direction
- floem.views.label uses floem.view.id, so a change to floem.view.id can break floem.views.label, while a change to floem.views.label can't break floem.view.id.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
30→3 floem.style uses floem.style.props✕
- Connections
- 3 pairs of types, where a type in floem.style uses a type in floem.style.props.
- The types involved
floem.style.Style→floem.style.props.StyleClassReffloem.style.Style→floem.style.props.StyleKeyfloem.style.style$module→floem.style.props.StyleKey
- Direction
- floem.style uses floem.style.props, so a change to floem.style.props can break floem.style, while a change to floem.style can't break floem.style.props.
- Position
- Below the diagonal: floem.style uses a module listed above it, which is the healthy direction.
30→5 floem.style uses floem.style.values✕
- Connections
- 4 pairs of types, where a type in floem.style uses a type in floem.style.values.
- The types involved
floem.style.ContextRef→floem.style.values.ContextValuefloem.style.ExprStyle→floem.style.values.ContextValuefloem.style.Style→floem.style.values.ContextValuefloem.style.Style→floem.style.values.StyleValue
- Direction
- floem.style uses floem.style.values, so a change to floem.style.values can break floem.style, while a change to floem.style can't break floem.style.values.
- Position
- Below the diagonal: floem.style uses a module listed above it, which is the healthy direction.
30→7 floem.style uses floem.style.unit✕
- Connections
- 1 pair of types, where a type in floem.style uses a type in floem.style.unit.
- The types involved
floem.style.Style→floem.style.unit.FontSizeCx
- Direction
- floem.style uses floem.style.unit, so a change to floem.style.unit can break floem.style, while a change to floem.style can't break floem.style.unit.
- Position
- Below the diagonal: floem.style uses a module listed above it, which is the healthy direction.
30→16 floem.style uses floem.style.cx✕
- Connections
- 1 pair of types, where a type in floem.style uses a type in floem.style.cx.
- The types involved
floem.style.style$module→floem.style.cx.InteractionState
- Direction
- floem.style uses floem.style.cx, so a change to floem.style.cx can break floem.style, while a change to floem.style can't break floem.style.cx.
- Position
- Below the diagonal: floem.style uses a module listed above it, which is the healthy direction.
30→17 floem.style uses floem.views.dropdown✕
- Connections
- 1 pair of types, where a type in floem.style uses a type in floem.views.dropdown.
- The types involved
floem.style.Style→floem.views.dropdown.DropdownCustomStyle
- Direction
- floem.style uses floem.views.dropdown, so a change to floem.views.dropdown can break floem.style, while a change to floem.style can't break floem.views.dropdown.
- Position
- Below the diagonal: floem.style uses a module listed above it, which is the healthy direction.
30→19 floem.style uses floem.views.resizable✕
- Connections
- 2 pairs of types, where a type in floem.style uses a type in floem.views.resizable.
- The types involved
floem.style.Style→floem.views.resizable.ResizableCustomExprStylefloem.style.Style→floem.views.resizable.ResizableCustomStyle
- Direction
- floem.style uses floem.views.resizable, so a change to floem.views.resizable can break floem.style, while a change to floem.style can't break floem.views.resizable.
- Position
- Below the diagonal: floem.style uses a module listed above it, which is the healthy direction.
30→20 floem.style uses floem.views.scroll✕
- Connections
- 1 pair of types, where a type in floem.style uses a type in floem.views.scroll.
- The types involved
floem.style.Style→floem.views.scroll.ScrollCustomStyle
- Direction
- floem.style uses floem.views.scroll, so a change to floem.views.scroll can break floem.style, while a change to floem.style can't break floem.views.scroll.
- Position
- Below the diagonal: floem.style uses a module listed above it, which is the healthy direction.
30→21 floem.style uses floem.views.slider✕
- Connections
- 2 pairs of types, where a type in floem.style uses a type in floem.views.slider.
- The types involved
floem.style.Style→floem.views.slider.SliderCustomExprStylefloem.style.Style→floem.views.slider.SliderCustomStyle
- Direction
- floem.style uses floem.views.slider, so a change to floem.views.slider can break floem.style, while a change to floem.style can't break floem.views.slider.
- Position
- Below the diagonal: floem.style uses a module listed above it, which is the healthy direction.
30→23 floem.style uses floem.views.toggle_button✕
- Connections
- 1 pair of types, where a type in floem.style uses a type in floem.views.toggle_button.
- The types involved
floem.style.Style→floem.views.toggle_button.ToggleButtonCustomStyle
- Direction
- floem.style uses floem.views.toggle_button, so a change to floem.views.toggle_button can break floem.style, while a change to floem.style can't break floem.views.toggle_button.
- Position
- Below the diagonal: floem.style uses a module listed above it, which is the healthy direction.
30→29 floem.style uses floem.views.label✕
- Connections
- 2 pairs of types, where a type in floem.style uses a type in floem.views.label.
- The types involved
floem.style.Style→floem.views.label.LabelCustomExprStylefloem.style.Style→floem.views.label.LabelCustomStyle
- Direction
- floem.style uses floem.views.label, so a change to floem.views.label can break floem.style, while a change to floem.style can't break floem.views.label.
- Position
- Below the diagonal: floem.style uses a module listed above it, which is the healthy direction.
31→5 floem.inspector uses floem.style.values✕
- Connections
- 1 pair of types, where a type in floem.inspector uses a type in floem.style.values.
- The types involved
floem.inspector.inspector$module→floem.style.values.StrokeWrap
- Direction
- floem.inspector uses floem.style.values, so a change to floem.style.values can break floem.inspector, while a change to floem.inspector can't break floem.style.values.
- Position
- Below the diagonal: floem.inspector uses a module listed above it, which is the healthy direction.
31→7 floem.inspector uses floem.style.unit✕
- Connections
- 3 pairs of types, where a type in floem.inspector uses a type in floem.style.unit.
- The types involved
floem.inspector.inspector$module→floem.style.unit.FontSizeCxfloem.inspector.inspector$module→floem.style.unit.Lengthfloem.inspector.inspector$module→floem.style.unit.LengthAuto
- Direction
- floem.inspector uses floem.style.unit, so a change to floem.style.unit can break floem.inspector, while a change to floem.inspector can't break floem.style.unit.
- Position
- Below the diagonal: floem.inspector uses a module listed above it, which is the healthy direction.
31→13 floem.inspector uses floem_reactive.signal✕
- Connections
- 2 pairs of types, where a type in floem.inspector uses a type in floem_reactive.signal.
- The types involved
floem.inspector.CaptureView→floem_reactive.signal.RwSignalfloem.inspector.inspector$module→floem_reactive.signal.RwSignal
- Direction
- floem.inspector uses floem_reactive.signal, so a change to floem_reactive.signal can break floem.inspector, while a change to floem.inspector can't break floem_reactive.signal.
- Position
- Below the diagonal: floem.inspector uses a module listed above it, which is the healthy direction.
31→16 floem.inspector uses floem.style.cx✕
- Connections
- 1 pair of types, where a type in floem.inspector uses a type in floem.style.cx.
- The types involved
floem.inspector.CaptureState→floem.style.cx.StyleCx
- Direction
- floem.inspector uses floem.style.cx, so a change to floem.style.cx can break floem.inspector, while a change to floem.inspector can't break floem.style.cx.
- Position
- Below the diagonal: floem.inspector uses a module listed above it, which is the healthy direction.
31→29 floem.inspector uses floem.views.label✕
- Connections
- 1 pair of types, where a type in floem.inspector uses a type in floem.views.label.
- The types involved
floem.inspector.inspector$module→floem.views.label.Label
- Direction
- floem.inspector uses floem.views.label, so a change to floem.views.label can break floem.inspector, while a change to floem.inspector can't break floem.views.label.
- Position
- Below the diagonal: floem.inspector uses a module listed above it, which is the healthy direction.
31→30 floem.inspector uses floem.style✕
- Connections
- 3 pairs of types, where a type in floem.inspector uses a type in floem.style.
- The types involved
floem.inspector.CaptureState→floem.style.Stylefloem.inspector.CapturedView→floem.style.Stylefloem.inspector.inspector$module→floem.style.Style
- Direction
- floem.inspector uses floem.style, so a change to floem.style can break floem.inspector, while a change to floem.inspector can't break floem.style.
- Position
- Below the diagonal: floem.inspector uses a module listed above it, which is the healthy direction.
31→33 floem.inspector uses floem.window.state part of a loop✕
- Connections
- 1 pair of types, where a type in floem.inspector uses a type in floem.window.state.
- The types involved
floem.inspector.CapturedView→floem.window.state.WindowState
- Direction
- floem.inspector uses floem.window.state, so a change to floem.window.state can break floem.inspector, while a change to floem.inspector can't break floem.window.state.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
31→37 floem.inspector uses floem.view.id part of a loop✕
- Connections
- 4 pairs of types, where a type in floem.inspector uses a type in floem.view.id.
- The types involved
floem.inspector.CaptureState→floem.view.id.ViewIdfloem.inspector.CapturedView→floem.view.id.ViewIdfloem.inspector.RelativeViewId→floem.view.id.ViewIdfloem.inspector.inspector$module→floem.view.id.ViewId
- Direction
- floem.inspector uses floem.view.id, so a change to floem.view.id can break floem.inspector, while a change to floem.inspector can't break floem.view.id.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
31→38 floem.inspector uses floem.box_tree part of a loop✕
- Connections
- 1 pair of types, where a type in floem.inspector uses a type in floem.box_tree.
- The types involved
floem.inspector.BoxModelRegionIds→floem.box_tree.ElementId
- Direction
- floem.inspector uses floem.box_tree, so a change to floem.box_tree can break floem.inspector, while a change to floem.inspector can't break floem.box_tree.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
32→3 floem.view.state uses floem.style.props✕
- Connections
- 1 pair of types, where a type in floem.view.state uses a type in floem.style.props.
- The types involved
floem.view.state.ViewState→floem.style.props.StyleClassRef
- Direction
- floem.view.state uses floem.style.props, so a change to floem.style.props can break floem.view.state, while a change to floem.view.state can't break floem.style.props.
- Position
- Below the diagonal: floem.view.state uses a module listed above it, which is the healthy direction.
32→15 floem.view.state uses floem_reactive.scope✕
- Connections
- 1 pair of types, where a type in floem.view.state uses a type in floem_reactive.scope.
- The types involved
floem.view.state.ViewState→floem_reactive.scope.Scope
- Direction
- floem.view.state uses floem_reactive.scope, so a change to floem_reactive.scope can break floem.view.state, while a change to floem.view.state can't break floem_reactive.scope.
- Position
- Below the diagonal: floem.view.state uses a module listed above it, which is the healthy direction.
32→16 floem.view.state uses floem.style.cx✕
- Connections
- 2 pairs of types, where a type in floem.view.state uses a type in floem.style.cx.
- The types involved
floem.view.state.ViewState→floem.style.cx.InheritedInteractionCxfloem.view.state.ViewState→floem.style.cx.InteractionState
- Direction
- floem.view.state uses floem.style.cx, so a change to floem.style.cx can break floem.view.state, while a change to floem.view.state can't break floem.style.cx.
- Position
- Below the diagonal: floem.view.state uses a module listed above it, which is the healthy direction.
32→30 floem.view.state uses floem.style✕
- Connections
- 2 pairs of types, where a type in floem.view.state uses a type in floem.style.
- The types involved
floem.view.state.StyleStack→floem.style.Stylefloem.view.state.ViewState→floem.style.Style
- Direction
- floem.view.state uses floem.style, so a change to floem.style can break floem.view.state, while a change to floem.view.state can't break floem.style.
- Position
- Below the diagonal: floem.view.state uses a module listed above it, which is the healthy direction.
32→37 floem.view.state uses floem.view.id part of a loop✕
- Connections
- 1 pair of types, where a type in floem.view.state uses a type in floem.view.id.
- The types involved
floem.view.state.ViewState→floem.view.id.ViewId
- Direction
- floem.view.state uses floem.view.id, so a change to floem.view.id can break floem.view.state, while a change to floem.view.state can't break floem.view.id.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
32→38 floem.view.state uses floem.box_tree part of a loop✕
- Connections
- 2 pairs of types, where a type in floem.view.state uses a type in floem.box_tree.
- The types involved
floem.view.state.ViewState→floem.box_tree.BoxTreefloem.view.state.ViewState→floem.box_tree.ElementId
- Direction
- floem.view.state uses floem.box_tree, so a change to floem.box_tree can break floem.view.state, while a change to floem.view.state can't break floem.box_tree.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
33→30 floem.window.state uses floem.style✕
- Connections
- 1 pair of types, where a type in floem.window.state uses a type in floem.style.
- The types involved
floem.window.state.WindowState→floem.style.Style
- Direction
- floem.window.state uses floem.style, so a change to floem.style can break floem.window.state, while a change to floem.window.state can't break floem.style.
- Position
- Below the diagonal: floem.window.state uses a module listed above it, which is the healthy direction.
33→31 floem.window.state uses floem.inspector✕
- Connections
- 1 pair of types, where a type in floem.window.state uses a type in floem.inspector.
- The types involved
floem.window.state.WindowState→floem.inspector.CaptureState
- Direction
- floem.window.state uses floem.inspector, so a change to floem.inspector can break floem.window.state, while a change to floem.window.state can't break floem.inspector.
- Position
- Below the diagonal: floem.window.state uses a module listed above it, which is the healthy direction.
33→37 floem.window.state uses floem.view.id part of a loop✕
- Connections
- 2 pairs of types, where a type in floem.window.state uses a type in floem.view.id.
- The types involved
floem.window.state.WindowState→floem.view.id.ViewIdfloem.window.state.state$module→floem.view.id.ViewId
- Direction
- floem.window.state uses floem.view.id, so a change to floem.view.id can break floem.window.state, while a change to floem.window.state can't break floem.view.id.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
33→38 floem.window.state uses floem.box_tree part of a loop✕
- Connections
- 5 pairs of types, where a type in floem.window.state uses a type in floem.box_tree.
- The types involved
floem.window.state.ViewBoxProperties→floem.box_tree.ElementIdfloem.window.state.WindowState→floem.box_tree.BoxTreefloem.window.state.WindowState→floem.box_tree.ElementIdfloem.window.state.state$module→floem.box_tree.BoxTreefloem.window.state.state$module→floem.box_tree.ElementId
- Direction
- floem.window.state uses floem.box_tree, so a change to floem.box_tree can break floem.window.state, while a change to floem.window.state can't break floem.box_tree.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
34→15 floem.message uses floem_reactive.scope✕
- Connections
- 2 pairs of types, where a type in floem.message uses a type in floem_reactive.scope.
- The types involved
floem.message.DeferredChild→floem_reactive.scope.Scopefloem.message.DeferredChildren→floem_reactive.scope.Scope
- Direction
- floem.message uses floem_reactive.scope, so a change to floem_reactive.scope can break floem.message, while a change to floem.message can't break floem_reactive.scope.
- Position
- Below the diagonal: floem.message uses a module listed above it, which is the healthy direction.
34→33 floem.message uses floem.window.state✕
- Connections
- 1 pair of types, where a type in floem.message uses a type in floem.window.state.
- The types involved
floem.message.UpdateCx→floem.window.state.WindowState
- Direction
- floem.message uses floem.window.state, so a change to floem.window.state can break floem.message, while a change to floem.message can't break floem.window.state.
- Position
- Below the diagonal: floem.message uses a module listed above it, which is the healthy direction.
34→37 floem.message uses floem.view.id part of a loop✕
- Connections
- 1 pair of types, where a type in floem.message uses a type in floem.view.id.
- The types involved
floem.message.DeferredReactiveSetup→floem.view.id.ViewId
- Direction
- floem.message uses floem.view.id, so a change to floem.view.id can break floem.message, while a change to floem.message can't break floem.view.id.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
35→3 floem.views.list uses floem.style.props✕
- Connections
- 4 pairs of types, where a type in floem.views.list uses a type in floem.style.props.
- The types involved
floem.views.list.ListClass→floem.style.props.StyleClassfloem.views.list.ListClass→floem.style.props.StyleKeyfloem.views.list.ListItemClass→floem.style.props.StyleClassfloem.views.list.ListItemClass→floem.style.props.StyleKey
- Direction
- floem.views.list uses floem.style.props, so a change to floem.style.props can break floem.views.list, while a change to floem.views.list can't break floem.style.props.
- Position
- Below the diagonal: floem.views.list uses a module listed above it, which is the healthy direction.
35→10 floem.views.list uses floem.view✕
- Connections
- 2 pairs of types, where a type in floem.views.list uses a type in floem.view.
- The types involved
floem.views.list.Item→floem.view.Viewfloem.views.list.List→floem.view.View
- Direction
- floem.views.list uses floem.view, so a change to floem.view can break floem.views.list, while a change to floem.views.list can't break floem.view.
- Position
- Below the diagonal: floem.views.list uses a module listed above it, which is the healthy direction.
35→13 floem.views.list uses floem_reactive.signal✕
- Connections
- 2 pairs of types, where a type in floem.views.list uses a type in floem_reactive.signal.
- The types involved
floem.views.list.Item→floem_reactive.signal.RwSignalfloem.views.list.List→floem_reactive.signal.RwSignal
- Direction
- floem.views.list uses floem_reactive.signal, so a change to floem_reactive.signal can break floem.views.list, while a change to floem.views.list can't break floem_reactive.signal.
- Position
- Below the diagonal: floem.views.list uses a module listed above it, which is the healthy direction.
35→16 floem.views.list uses floem.style.cx✕
- Connections
- 1 pair of types, where a type in floem.views.list uses a type in floem.style.cx.
- The types involved
floem.views.list.Item→floem.style.cx.StyleCx
- Direction
- floem.views.list uses floem.style.cx, so a change to floem.style.cx can break floem.views.list, while a change to floem.views.list can't break floem.style.cx.
- Position
- Below the diagonal: floem.views.list uses a module listed above it, which is the healthy direction.
35→30 floem.views.list uses floem.style✕
- Connections
- 2 pairs of types, where a type in floem.views.list uses a type in floem.style.
- The types involved
floem.views.list.Item→floem.style.Stylefloem.views.list.List→floem.style.Style
- Direction
- floem.views.list uses floem.style, so a change to floem.style can break floem.views.list, while a change to floem.views.list can't break floem.style.
- Position
- Below the diagonal: floem.views.list uses a module listed above it, which is the healthy direction.
35→34 floem.views.list uses floem.message✕
- Connections
- 1 pair of types, where a type in floem.views.list uses a type in floem.message.
- The types involved
floem.views.list.List→floem.message.UpdateCx
- Direction
- floem.views.list uses floem.message, so a change to floem.message can break floem.views.list, while a change to floem.views.list can't break floem.message.
- Position
- Below the diagonal: floem.views.list uses a module listed above it, which is the healthy direction.
35→37 floem.views.list uses floem.view.id part of a loop✕
- Connections
- 2 pairs of types, where a type in floem.views.list uses a type in floem.view.id.
- The types involved
floem.views.list.Item→floem.view.id.ViewIdfloem.views.list.List→floem.view.id.ViewId
- Direction
- floem.views.list uses floem.view.id, so a change to floem.view.id can break floem.views.list, while a change to floem.views.list can't break floem.view.id.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
36→2 floem.event.dispatch uses floem.event✕
- Connections
- 6 pairs of types, where a type in floem.event.dispatch uses a type in floem.event.
- The types involved
floem.event.dispatch.Dispatch→floem.event.Phasefloem.event.dispatch.EventCx→floem.event.DragTokenfloem.event.dispatch.EventCx→floem.event.Eventfloem.event.dispatch.EventCx→floem.event.Phasefloem.event.dispatch.GlobalEventCx→floem.event.Eventfloem.event.dispatch.RouteCx→floem.event.Event
- Direction
- floem.event.dispatch uses floem.event, so a change to floem.event can break floem.event.dispatch, while a change to floem.event.dispatch can't break floem.event.
- Position
- Below the diagonal: floem.event.dispatch uses a module listed above it, which is the healthy direction.
36→33 floem.event.dispatch uses floem.window.state✕
- Connections
- 3 pairs of types, where a type in floem.event.dispatch uses a type in floem.window.state.
- The types involved
floem.event.dispatch.EventCx→floem.window.state.WindowStatefloem.event.dispatch.GlobalEventCx→floem.window.state.WindowStatefloem.event.dispatch.RouteCx→floem.window.state.WindowState
- Direction
- floem.event.dispatch uses floem.window.state, so a change to floem.window.state can break floem.event.dispatch, while a change to floem.event.dispatch can't break floem.window.state.
- Position
- Below the diagonal: floem.event.dispatch uses a module listed above it, which is the healthy direction.
36→35 floem.event.dispatch uses floem.views.list✕
- Connections
- 1 pair of types, where a type in floem.event.dispatch uses a type in floem.views.list.
- The types involved
floem.event.dispatch.DispatchSequenceIter→floem.views.list.Item
- Direction
- floem.event.dispatch uses floem.views.list, so a change to floem.views.list can break floem.event.dispatch, while a change to floem.event.dispatch can't break floem.views.list.
- Position
- Below the diagonal: floem.event.dispatch uses a module listed above it, which is the healthy direction.
36→37 floem.event.dispatch uses floem.view.id part of a loop✕
- Connections
- 2 pairs of types, where a type in floem.event.dispatch uses a type in floem.view.id.
- The types involved
floem.event.dispatch.Dispatch→floem.view.id.ViewIdfloem.event.dispatch.RouteCx→floem.view.id.ViewId
- Direction
- floem.event.dispatch uses floem.view.id, so a change to floem.view.id can break floem.event.dispatch, while a change to floem.event.dispatch can't break floem.view.id.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
36→38 floem.event.dispatch uses floem.box_tree part of a loop✕
- Connections
- 10 pairs of types, where a type in floem.event.dispatch uses a type in floem.box_tree.
- The types involved
floem.event.dispatch.Dispatch→floem.box_tree.ElementIdfloem.event.dispatch.EventCx→floem.box_tree.ElementIdfloem.event.dispatch.GlobalEventCx→floem.box_tree.ElementIdfloem.event.dispatch.RouteCx→floem.box_tree.BoxTreefloem.event.dispatch.RouteCx→floem.box_tree.ElementIdfloem.event.dispatch.RouteCx→floem.box_tree.ElementMetafloem.event.dispatch.RouteData→floem.box_tree.ElementIdfloem.event.dispatch.RouteKind→floem.box_tree.ElementIdfloem.event.dispatch.dispatch$module→floem.box_tree.BoxTreefloem.event.dispatch.dispatch$module→floem.box_tree.ElementId
- Direction
- floem.event.dispatch uses floem.box_tree, so a change to floem.box_tree can break floem.event.dispatch, while a change to floem.event.dispatch can't break floem.box_tree.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
37→2 floem.view.id uses floem.event✕
- Connections
- 1 pair of types, where a type in floem.view.id uses a type in floem.event.
- The types involved
floem.view.id.ViewId→floem.event.Event
- Direction
- floem.view.id uses floem.event, so a change to floem.event can break floem.view.id, while a change to floem.view.id can't break floem.event.
- Position
- Below the diagonal: floem.view.id uses a module listed above it, which is the healthy direction.
37→3 floem.view.id uses floem.style.props✕
- Connections
- 1 pair of types, where a type in floem.view.id uses a type in floem.style.props.
- The types involved
floem.view.id.ViewId→floem.style.props.StyleClassRef
- Direction
- floem.view.id uses floem.style.props, so a change to floem.style.props can break floem.view.id, while a change to floem.view.id can't break floem.style.props.
- Position
- Below the diagonal: floem.view.id uses a module listed above it, which is the healthy direction.
37→15 floem.view.id uses floem_reactive.scope✕
- Connections
- 1 pair of types, where a type in floem.view.id uses a type in floem_reactive.scope.
- The types involved
floem.view.id.ViewId→floem_reactive.scope.Scope
- Direction
- floem.view.id uses floem_reactive.scope, so a change to floem_reactive.scope can break floem.view.id, while a change to floem.view.id can't break floem_reactive.scope.
- Position
- Below the diagonal: floem.view.id uses a module listed above it, which is the healthy direction.
37→30 floem.view.id uses floem.style✕
- Connections
- 1 pair of types, where a type in floem.view.id uses a type in floem.style.
- The types involved
floem.view.id.ViewId→floem.style.Style
- Direction
- floem.view.id uses floem.style, so a change to floem.style can break floem.view.id, while a change to floem.view.id can't break floem.style.
- Position
- Below the diagonal: floem.view.id uses a module listed above it, which is the healthy direction.
37→32 floem.view.id uses floem.view.state✕
- Connections
- 2 pairs of types, where a type in floem.view.id uses a type in floem.view.state.
- The types involved
floem.view.id.ViewId→floem.view.state.StackOffsetfloem.view.id.ViewId→floem.view.state.ViewState
- Direction
- floem.view.id uses floem.view.state, so a change to floem.view.state can break floem.view.id, while a change to floem.view.id can't break floem.view.state.
- Position
- Below the diagonal: floem.view.id uses a module listed above it, which is the healthy direction.
37→34 floem.view.id uses floem.message✕
- Connections
- 1 pair of types, where a type in floem.view.id uses a type in floem.message.
- The types involved
floem.view.id.ViewId→floem.message.UpdateMessage
- Direction
- floem.view.id uses floem.message, so a change to floem.message can break floem.view.id, while a change to floem.view.id can't break floem.message.
- Position
- Below the diagonal: floem.view.id uses a module listed above it, which is the healthy direction.
37→36 floem.view.id uses floem.event.dispatch✕
- Connections
- 1 pair of types, where a type in floem.view.id uses a type in floem.event.dispatch.
- The types involved
floem.view.id.ViewId→floem.event.dispatch.RouteKind
- Direction
- floem.view.id uses floem.event.dispatch, so a change to floem.event.dispatch can break floem.view.id, while a change to floem.view.id can't break floem.event.dispatch.
- Position
- Below the diagonal: floem.view.id uses a module listed above it, which is the healthy direction.
37→38 floem.view.id uses floem.box_tree part of a loop✕
- Connections
- 4 pairs of types, where a type in floem.view.id uses a type in floem.box_tree.
- The types involved
floem.view.id.ViewId→floem.box_tree.BoxTreefloem.view.id.ViewId→floem.box_tree.ElementIdfloem.view.id.ViewId→floem.box_tree.FocusNavMetafloem.view.id.id$module→floem.box_tree.ElementId
- Direction
- floem.view.id uses floem.box_tree, so a change to floem.box_tree can break floem.view.id, while a change to floem.view.id can't break floem.box_tree.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
38→37 floem.box_tree uses floem.view.id✕
- Connections
- 1 pair of types, where a type in floem.box_tree uses a type in floem.view.id.
- The types involved
floem.box_tree.ElementId→floem.view.id.ViewId
- Direction
- floem.box_tree uses floem.view.id, so a change to floem.view.id can break floem.box_tree, while a change to floem.box_tree can't break floem.view.id.
- Position
- Below the diagonal: floem.box_tree uses a module listed above it, which is the healthy direction.
39→2 floem.window.handle uses floem.event✕
- Connections
- 1 pair of types, where a type in floem.window.handle uses a type in floem.event.
- The types involved
floem.window.handle.WindowHandle→floem.event.Event
- Direction
- floem.window.handle uses floem.event, so a change to floem.event can break floem.window.handle, while a change to floem.window.handle can't break floem.event.
- Position
- Below the diagonal: floem.window.handle uses a module listed above it, which is the healthy direction.
39→8 floem.window.handle uses floem.paint✕
- Connections
- 1 pair of types, where a type in floem.window.handle uses a type in floem.paint.
- The types involved
floem.window.handle.WindowHandle→floem.paint.PaintState
- Direction
- floem.window.handle uses floem.paint, so a change to floem.paint can break floem.window.handle, while a change to floem.window.handle can't break floem.paint.
- Position
- Below the diagonal: floem.window.handle uses a module listed above it, which is the healthy direction.
39→10 floem.window.handle uses floem.view✕
- Connections
- 1 pair of types, where a type in floem.window.handle uses a type in floem.view.
- The types involved
floem.window.handle.WindowView→floem.view.View
- Direction
- floem.window.handle uses floem.view, so a change to floem.view can break floem.window.handle, while a change to floem.window.handle can't break floem.view.
- Position
- Below the diagonal: floem.window.handle uses a module listed above it, which is the healthy direction.
39→13 floem.window.handle uses floem_reactive.signal✕
- Connections
- 1 pair of types, where a type in floem.window.handle uses a type in floem_reactive.signal.
- The types involved
floem.window.handle.WindowHandle→floem_reactive.signal.RwSignal
- Direction
- floem.window.handle uses floem_reactive.signal, so a change to floem_reactive.signal can break floem.window.handle, while a change to floem.window.handle can't break floem_reactive.signal.
- Position
- Below the diagonal: floem.window.handle uses a module listed above it, which is the healthy direction.
39→15 floem.window.handle uses floem_reactive.scope✕
- Connections
- 1 pair of types, where a type in floem.window.handle uses a type in floem_reactive.scope.
- The types involved
floem.window.handle.WindowHandle→floem_reactive.scope.Scope
- Direction
- floem.window.handle uses floem_reactive.scope, so a change to floem_reactive.scope can break floem.window.handle, while a change to floem.window.handle can't break floem_reactive.scope.
- Position
- Below the diagonal: floem.window.handle uses a module listed above it, which is the healthy direction.
39→30 floem.window.handle uses floem.style✕
- Connections
- 2 pairs of types, where a type in floem.window.handle uses a type in floem.style.
- The types involved
floem.window.handle.WindowHandle→floem.style.Stylefloem.window.handle.WindowView→floem.style.Style
- Direction
- floem.window.handle uses floem.style, so a change to floem.style can break floem.window.handle, while a change to floem.window.handle can't break floem.style.
- Position
- Below the diagonal: floem.window.handle uses a module listed above it, which is the healthy direction.
39→31 floem.window.handle uses floem.inspector✕
- Connections
- 1 pair of types, where a type in floem.window.handle uses a type in floem.inspector.
- The types involved
floem.window.handle.WindowHandle→floem.inspector.Capture
- Direction
- floem.window.handle uses floem.inspector, so a change to floem.inspector can break floem.window.handle, while a change to floem.window.handle can't break floem.inspector.
- Position
- Below the diagonal: floem.window.handle uses a module listed above it, which is the healthy direction.
39→33 floem.window.handle uses floem.window.state✕
- Connections
- 1 pair of types, where a type in floem.window.handle uses a type in floem.window.state.
- The types involved
floem.window.handle.WindowHandle→floem.window.state.WindowState
- Direction
- floem.window.handle uses floem.window.state, so a change to floem.window.state can break floem.window.handle, while a change to floem.window.handle can't break floem.window.state.
- Position
- Below the diagonal: floem.window.handle uses a module listed above it, which is the healthy direction.
39→37 floem.window.handle uses floem.view.id✕
- Connections
- 3 pairs of types, where a type in floem.window.handle uses a type in floem.view.id.
- The types involved
floem.window.handle.WindowHandle→floem.view.id.ViewIdfloem.window.handle.WindowView→floem.view.id.ViewIdfloem.window.handle.handle$module→floem.view.id.ViewId
- Direction
- floem.window.handle uses floem.view.id, so a change to floem.view.id can break floem.window.handle, while a change to floem.window.handle can't break floem.view.id.
- Position
- Below the diagonal: floem.window.handle uses a module listed above it, which is the healthy direction.
40→2 floem.inspector.view uses floem.event✕
- Connections
- 1 pair of types, where a type in floem.inspector.view uses a type in floem.event.
- The types involved
floem.inspector.view.InspectorImageView→floem.event.EventPropagation
- Direction
- floem.inspector.view uses floem.event, so a change to floem.event can break floem.inspector.view, while a change to floem.inspector.view can't break floem.event.
- Position
- Below the diagonal: floem.inspector.view uses a module listed above it, which is the healthy direction.
40→8 floem.inspector.view uses floem.paint✕
- Connections
- 1 pair of types, where a type in floem.inspector.view uses a type in floem.paint.
- The types involved
floem.inspector.view.InspectorImageView→floem.paint.PaintCx
- Direction
- floem.inspector.view uses floem.paint, so a change to floem.paint can break floem.inspector.view, while a change to floem.inspector.view can't break floem.paint.
- Position
- Below the diagonal: floem.inspector.view uses a module listed above it, which is the healthy direction.
40→10 floem.inspector.view uses floem.view✕
- Connections
- 1 pair of types, where a type in floem.inspector.view uses a type in floem.view.
- The types involved
floem.inspector.view.InspectorImageView→floem.view.View
- Direction
- floem.inspector.view uses floem.view, so a change to floem.view can break floem.inspector.view, while a change to floem.inspector.view can't break floem.view.
- Position
- Below the diagonal: floem.inspector.view uses a module listed above it, which is the healthy direction.
40→13 floem.inspector.view uses floem_reactive.signal✕
- Connections
- 2 pairs of types, where a type in floem.inspector.view uses a type in floem_reactive.signal.
- The types involved
floem.inspector.view.InspectorImageView→floem_reactive.signal.RwSignalfloem.inspector.view.view$module→floem_reactive.signal.RwSignal
- Direction
- floem.inspector.view uses floem_reactive.signal, so a change to floem_reactive.signal can break floem.inspector.view, while a change to floem.inspector.view can't break floem_reactive.signal.
- Position
- Below the diagonal: floem.inspector.view uses a module listed above it, which is the healthy direction.
40→16 floem.inspector.view uses floem.style.cx✕
- Connections
- 1 pair of types, where a type in floem.inspector.view uses a type in floem.style.cx.
- The types involved
floem.inspector.view.InspectorImageView→floem.style.cx.StyleCx
- Direction
- floem.inspector.view uses floem.style.cx, so a change to floem.style.cx can break floem.inspector.view, while a change to floem.inspector.view can't break floem.style.cx.
- Position
- Below the diagonal: floem.inspector.view uses a module listed above it, which is the healthy direction.
40→31 floem.inspector.view uses floem.inspector✕
- Connections
- 5 pairs of types, where a type in floem.inspector.view uses a type in floem.inspector.
- The types involved
floem.inspector.view.InspectorImageView→floem.inspector.Capturefloem.inspector.view.InspectorImageView→floem.inspector.CaptureViewfloem.inspector.view.view$module→floem.inspector.Capturefloem.inspector.view.view$module→floem.inspector.CaptureViewfloem.inspector.view.view$module→floem.inspector.CapturedView
- Direction
- floem.inspector.view uses floem.inspector, so a change to floem.inspector can break floem.inspector.view, while a change to floem.inspector.view can't break floem.inspector.
- Position
- Below the diagonal: floem.inspector.view uses a module listed above it, which is the healthy direction.
40→36 floem.inspector.view uses floem.event.dispatch✕
- Connections
- 1 pair of types, where a type in floem.inspector.view uses a type in floem.event.dispatch.
- The types involved
floem.inspector.view.InspectorImageView→floem.event.dispatch.EventCx
- Direction
- floem.inspector.view uses floem.event.dispatch, so a change to floem.event.dispatch can break floem.inspector.view, while a change to floem.inspector.view can't break floem.event.dispatch.
- Position
- Below the diagonal: floem.inspector.view uses a module listed above it, which is the healthy direction.
40→37 floem.inspector.view uses floem.view.id✕
- Connections
- 2 pairs of types, where a type in floem.inspector.view uses a type in floem.view.id.
- The types involved
floem.inspector.view.InspectorImageView→floem.view.id.ViewIdfloem.inspector.view.view$module→floem.view.id.ViewId
- Direction
- floem.inspector.view uses floem.view.id, so a change to floem.view.id can break floem.inspector.view, while a change to floem.inspector.view can't break floem.view.id.
- Position
- Below the diagonal: floem.inspector.view uses a module listed above it, which is the healthy direction.
40→38 floem.inspector.view uses floem.box_tree✕
- Connections
- 1 pair of types, where a type in floem.inspector.view uses a type in floem.box_tree.
- The types involved
floem.inspector.view.InspectorImageView→floem.box_tree.ElementId
- Direction
- floem.inspector.view uses floem.box_tree, so a change to floem.box_tree can break floem.inspector.view, while a change to floem.inspector.view can't break floem.box_tree.
- Position
- Below the diagonal: floem.inspector.view uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Event-Driven
At a glance — Event Sourcing
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 36 | High / Critical |
| A05:2025 — Injection | 10 | High / Critical |
Roadmap
First, ensure event recovery is deterministic by stamping clock and random values into commands so the fold remains a pure function. Next, document significant design decisions in the docs/adr folder and add a quick-start build section to the root README for new contributors. Finally, resolve the 80 orphaned files starting with mod.rs, builder.rs, and movement.rs, and address the single yanked dependency to maintain code hygiene.
| 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. | +9.2 pts | Medium | Fold determinism |
| Resolve the 1 Yanked release finding(s) in Dependency Hygiene. | +1.6 pts | Low | Dependency Hygiene |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +2.9 pts | Medium | Architecture documentation |
| Resolve the 80 Orphaned file finding(s) in Knowledge Freshness — start with mod.rs (7), builder.rs (4), movement.rs (2). | +2.6 pts | Medium | Knowledge Freshness |
| Add a build/run (quick start) section to the root README — the first thing a newcomer needs. | +1.6 pts | Medium | Documentation (README) |
| Enable Dependabot/Renovate or a dependency-review gate. | +0.8 pts | Medium | Security & performance tooling |
| Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where Watchdog can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it. | +0.8 pts | Medium | Deployment & Rollback |
| Keep implementation types off the public surface (Rust: `pub(crate)`, or keep the module private) so internals can change without breaking consumers. | +0.7 pts | Medium | Library API & versioning |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 1.6 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| vello/src/lib.rs | 2.4 | Slop | Change Coupling: Boundary-crossing change coupling: lib.rs ↔ lib.rs |
| REDACTED | 2.4 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| src/views/label.rs | 4.8 | Mixed | Cyclomatic Complexity: Label::event (cyclomatic 19) |
| src/views/scroll.rs | 5.6 | Mixed | Cyclomatic Complexity: Scroll::event (cyclomatic 22) |
| editor-core/src/editor.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/style/cx.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/style/mod.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/views/text_input.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/animate/mod.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/views/editor/movement.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| editor-core/src/cursor.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| editor-core/src/buffer/mod.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/window/state.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/views/editor/gutter.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/views/editor/view.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/inspector/mod.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| tiny_skia/src/lib.rs | 6.0 | Mixed | Explicit Debt: FixmeComment |
| src/view/id.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
How the grades work
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.
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.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
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. 48 of 48 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.9 — 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.
What we checked — 48 dimensions across the health lenses
- 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, 634 of 677 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- 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.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Watchdog duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
| LLM (sampled · advisory) | Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement | — | ◐ LLM · sampled · advisory |
Run transparency — what happened this run
- 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, 84 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.
- D19 Documentation Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D21 Naming Consistency — 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. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — 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. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- D24 Comment Value — 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.
- D27 Navigability — 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. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- 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.
- 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 reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Rust is not read yet, 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.
- 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 reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's Rust is not read yet, 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.
- 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 reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in 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.
- 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 reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in 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.
- 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 reads C# syntax, and JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala or Kotlin was found in 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.
- 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 reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in 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.
- 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 reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala or PHP was found in 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.
- 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 reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala or PHP was found in 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.
- 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 reads C# syntax, and Java, TypeScript/JavaScript, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded, and this repository's Rust is not read yet, 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.
- 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 reads C# syntax, and JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin or PHP was found in 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.
- 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 reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in 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.
- 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 reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart and Ruby source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart or Ruby was found in 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.
- 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 reads C# syntax, and PHP, Java, Kotlin, Python, Ruby, Scala, Dart, Swift, Erlang, Go and JavaScript/TypeScript source only, and no C# was loaded and no PHP, Java, Kotlin, Python, Ruby, Scala, Dart, Swift, Erlang, Go, JavaScript or TypeScript was found in 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.
- 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 reads C# syntax and MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, and Kotlin source only, and no C# was loaded, no TypeScript was found, and this repository's Rust is not read yet, 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.
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
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- 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.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
34 function(s) exceeded the cyclomatic complexity threshold of 15; the worst was Action::do_edit at 124. A further 6 function(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 Event::listener_keys at 65 — they are counted neither in the figure above nor in this dimension's score. 5 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: src/event/mod.rs (Event::listener_keys at 65), editor-core/src/command.rs (MoveCommand::to_movement at 23), src/style/values.rs (ObjectPosition::debug_view at 19), src/views/img.rs (Img::object_fit_dest_rect_with at 18), tiny_skia/src/lib.rs (floem_tiny_skia_renderer::mix_to_tiny_blend_mode at 16). 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.
What to do
- Bring the 2 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with Action::do_edit (cyclomatic 124), ApplicationHandle::handle_window_event (cyclomatic 64). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cyclomatic Complexity from 5.8 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
- Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
72 function(s) exceeded the cognitive complexity threshold of 15; the worst was Action::do_edit at 237.
What to do
- Bring the 1 body over 120 down to 120 or less in Cognitive Complexity — start with Action::do_edit (cognitive 237). — Refactoring it lifts Cognitive Complexity from 5.1 to about 5.8/10.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
79 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 28 FileTooLong finding(s) in God Classes — start with mod.rs (7), lib.rs (2), handle.rs (2). — One of this dimension's main actionable groups (28 warning-level).
- Resolve the 16 ClassTooLong finding(s) in God Classes — start with mod.rs (4), lib.rs (4), handle.rs (2). — One of this dimension's main actionable groups (16 warning-level).
- Resolve the 14 TooManyMethods finding(s) in God Classes — start with mod.rs (5), id.rs, state.rs. — One of this dimension's main actionable groups (14 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.
D4 · Code Duplication
123 duplicated block group(s) detected. A further 12 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.
What to do
- Resolve the 11 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with headless.rs (3), layout_state.rs (2), drag_state.rs. — One of this dimension's main actionable groups (11 warning-level).
- Resolve the 9 Duplicated block (12 lines × 2) finding(s) in Code Duplication — start with context.rs (2), cursor.rs, editor.rs. — One of this dimension's main actionable groups (9 warning-level).
- Resolve the 9 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with editor.rs (2), values.rs (2), cursor.rs. — One of this dimension's main actionable groups (9 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.
D5 · Coupling
10 production modules (Cargo), 0 dependency cycle(s), 1 unstable depended-on module(s). Read from the build's own module declarations; 3 module(s) off the main sequence, with abstractness counted on 8 of the 10 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What to do
- Resolve the 3 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 1 Unstable project floem 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.
D6 · Cohesion (LCOM4)
5 of 170 classes have LCOM4 above 3.
What to do
- Resolve the 5 Low cohesion finding(s) in Cohesion (LCOM4) — start with mod.rs (2), id.rs (2), state.rs. — One of this dimension's main actionable groups (5 warning-level).
- Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D9 · Test Distribution
980 test methods: 261 unit, 719 integration, 0 BDD, 0 e2e. The Rust suite contributes 980 `#[test]` function(s) across 84 file(s) declaring at least one; its unit/integration split is Cargo's own — 51 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.
D12 · Dependency Hygiene
27 outdated, 1 yanked direct Cargo dependencies. Only DIRECT edges are graded: a transitive crate cannot be moved past what its parent's requirement admits, so reporting one would be advice its owner cannot take. A newer release is reported only where this repository's OWN requirement already admits it, so the remedy is `cargo update` and never a manifest edit — which means a release outside the declared range is deliberately NOT charged, because a written-down constraint is a decision rather than a defect. Note that a bare requirement is a CARET, and for a 0.x crate its ceiling is the minor. Whether any crate is UNMAINTAINED is not graded — crates.io publishes no maintenance status, and release age does not stand in for one. Known CVEs in this dependency graph are D30's question, read from REDACTED there.
What to do
- Resolve the 1 Yanked release finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 702 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository's REDACTED closed over its manifests' `[dependencies]` and `[build-dependencies]`. Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository. A further 20 crate(s) in the closure resolve from git, a path or a private registry and publish no licence this pass can read; they are outside this verdict. This repository publishes itself under MIT, which is its own choice and is not judged here.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D16 · Bus Factor
4 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is src/text/layout_state.rs. Counted over 147 of the 176 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D17 · Explicit Debt
174 deducted task-comment markers across 82284 LoC (0.2/KLoC) → score 9.6. 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.
What to do
- Resolve the 164 TodoComment finding(s) in Explicit Debt — start with mod.rs (48), visual_line.rs (32), view.rs (22). — One of this dimension's main actionable groups (164 warning-level).
- Resolve the 7 FixmeComment finding(s) in Explicit Debt — start with lib.rs (3), rope_text.rs (2), profiler.rs. — One of this dimension's main actionable groups (7 warning-level).
- Resolve the 2 XxxComment finding(s) in Explicit Debt — start with id.rs (2). — One of this dimension's main actionable groups (2 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.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 4 document(s) read across 1 unit(s).
D26 · Project Cohesion
1 of 9 build units (Cargo) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
10 finding(s): 0 critical, 10 high, 0 medium, 0 low. 10 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) — `src/inspector/view.rs` (line 478, line 524, lines 595–596, …) — 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.
What to do
- No action in Static Analysis (SAST) — all 10 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 (10 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
30 finding(s): 1 critical, 1 high, 28 medium, 0 low.
What to do
- Resolve the 13 Medium advisory (unmaintained) finding(s) in Dependency Vulnerabilities — start with REDACTED (13). — One of this dimension's main actionable groups (13 warning-level).
- Resolve the 1 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D34 · Knowledge Freshness
83 of 147 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is editor-core/src/editor.rs. Counted over 147 of the 176 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 80 Orphaned file finding(s) in Knowledge Freshness — start with mod.rs (7), builder.rs (4), movement.rs (2). — One of this dimension's main actionable groups (80 recommendation-level).
- Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with editor.rs, listener.rs, char_buffer.rs. — One of this dimension's main actionable groups (3 recommendation-level).
- Resolve the 1 Concentrated knowledge decay finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
Strongest change-coupling: container.rs↔stack.rs 73%; clip.rs↔scroll.rs 67%; tuple.rs↔label.rs 60%
What to do
- Resolve the 2 Boundary-crossing change coupling finding(s) in Change Coupling — start with tuple.rs, lib.rs. — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 4 Change coupling finding(s) in Change Coupling — start with label.rs (2), container.rs, mod.rs. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 1 Change-coupling hub finding(s) in Change Coupling — start with scroll.rs. — One of this dimension's main actionable groups (1 warning-level).
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
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.
AX3 · Project dependency cycles
AX4 · Dependency direction
AX9 · CQS / query purity
ED3 · Event naming
- `UpdatePhase` is an imperative name inside a domain-event set whose siblings are past-tense facts — it reads as an intent, not something that happened. Name it for the event that occurred (e.g. `ItemAdded`) so the event log records facts. — src/event/mod.rs:701
What to do
- Name domain-event cases in the past tense — they record facts that already happened.
ES1 · Fold determinism
- `WindowEventReducer.reduce` 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. — ui-events-winit/src/lib.rs:98
What to do
- Stamp clock/random values into the event in the command; the recovery fold must be a pure function of the event.
ES2 · Immutable events
M1 · Documentation (README)
What to do
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- Add a README to the 29 of 39 project(s) that lack one — worth up to 1.5 pts.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
- 556/721 types (77%) declared in the published library are public. For a library, every public type is a stability contract — keep implementation types off the surface and expose only the intended API.
What to do
- Keep implementation types off the public surface (Rust: `pub(crate)`, or keep the module private) so internals can change without breaking consumers.
P3 · Security & performance tooling
What to do
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
What to do
- Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where Watchdog can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it.
P6 · Release Hygiene
PF1 · Benchmark discipline
X1 · Async correctness
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X21 · Side-effecting pattern guard
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X30 · Support guard that admits what it rejects
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 85% | Strong | Solid. |
| Architecture | 94% | Exemplary | Solid. |
| Maturity | 62% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 67% | Strong | Solid. |
| Security | 71% | Adequate — gated by D30, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Event-Driven | 100% | Exemplary | Strongest area. |
| Event Sourcing | 49% | Adequate — gated by ES1 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 85% | Exemplary | Solid. |
Unscored — 1 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 71 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: Rust with no dependency-injection crate has no container to hand one lifetime's instance to another — every value is owned by the code that builds it, and the borrow checker rejects a longer-lived value keeping a borrow of a shorter-lived one.
- AX2 Stateful singletons — Not applicable: Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written.
- 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 — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no data at rest for these controls to protect.
- C2 Access Controls — No access-control surface detected in the analyzed source — this repository starts no server another machine can reach (no actix-web HttpServer, axum::serve, Rocket launch, warp::serve, poem or salvo Server, tonic Server::builder, hyper or tiny_http server outside examples and tests, none bound beyond loopback). Access control is therefore N/A here — a crate is authorized by the application that serves it, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~36339 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
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency — Naming consistency is measured on C# only; Rust not measured.
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed Rust surface was not measured.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ projects each declaring an entity of their own. Aggregate roots were found in only one source directory (ui-events-winit), which is a layered codebase, not two contexts. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C# and Visual Basic comments 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.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.rs), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — 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.
- 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.
- 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 (3 signals for this style, 3 needed — the count is met but a required primary signal is absent): 4 aggregate root(s) (types guarding their own state behind command methods — this language has no AggregateRoot base to inherit); 34 value object(s); 6 domain event(s); its domain events are published by services or handlers — no domain entity raises one; no aggregate is declared and no domain structure surrounds the state-guarding types: not claimed as DDD
- 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 — no mutating command handlers or message consumers detected — idempotency check not applicable
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. 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
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P2 Observability — This repository's Rust source (9 module(s), 179 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the 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
- PF2 Allocation hygiene — Not applicable: Rust spells out every heap allocation and makes borrowed slices (&[T], &str) its ordinary parameter types, so the allocation-aware style this card rewards elsewhere is the language's baseline rather than a rung to climb.
- PF3 Async & latency hygiene — Not applicable: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
- S1 Web-Security Posture — No web surface: 177 Rust file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation and obsolete TLS versions, and none was found. This repository serves no HTTP of its own — no HTTP-server crate (actix-web, axum, Rocket, warp, poem, tide, salvo, tonic, a hyper server, …) among its Cargo manifests' run-time dependencies, and no server started in its production source — so HTTPS enforcement, HSTS, cookie flags and input validation are N/A here, as they are for a C# library or worker. If this codebase starts serving HTTP, the dimension reactivates automatically.
- X12 Unreachable branch — 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
- X13 Undrained process stream — 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
- X16 Unfloored truncation loop — 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
- X17 Uncapped recursion over a caller-supplied document — 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
- X18 Disposal-pattern 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
- X19 Unrestored process-global state — 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
- X2 Cancellation propagation — no C# was loaded; this repository's Rust was read, and no request in it can be cancelled by a caller — a Rust request takes no token: a future is cancelled by dropping it, from outside the call (select!, a timeout, an aborted task), and reqwest, hyper and tonic take none
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X22 Contradicted release guard — 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
- X23 Unguarded diagnostic materialisation — 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
- X24 Document value interpolated into markup unescaped — 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
- X25 Inert configuration knob — 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
- X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. Rust's compiler refuses the unsynchronised version: a collection shared between a callback's thread and the waiting body must be `Sync`, which a `Vec`, `VecDeque` or `HashMap` is only behind a `Mutex`/`RwLock`, so the race this check looks for cannot be written in safe Rust. Not a gap in the analyzer and 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
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Rust was read, and it logs through none: the `log` crate's macros take one finished message (as log4net does in C#; its `kv` values are an opt-in its backends mostly drop), `println!`/`eprintln!` are not loggers, or it makes no log call outside its tests and examples at all. Calls through `tracing` (`tracing::info!`, or `info!` imported from it) would be judged.
- 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 — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 15 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Boundary-crossing change coupling: tuple.rs ↔ label.rs src/view/tuple.rs:1
- Boundary-crossing change coupling: lib.rs ↔ lib.rs vello/src/lib.rs:1
- REDACTED
- REDACTED
- Non-deterministic recovery fold: WindowEventReducer.reduce ui-events-winit/src/lib.rs:98
Serious — 539 finding(s)
- TodoComment vello/src/lib.rs:37
- TodoComment vello/src/lib.rs:308
- TodoComment test/tests/position_consistency.rs:1
- TodoComment src/action.rs:134
- TodoComment src/lib.rs:122
- TodoComment src/window/mod.rs:468
- TodoComment src/window/state.rs:148
- TodoComment src/views/dropdown.rs:317
- TodoComment src/views/navigation_stack.rs:87
- TodoComment src/views/text_editor.rs:405
- TodoComment src/views/text_input.rs:75
- TodoComment src/views/text_input.rs:146
- TodoComment src/views/text_input.rs:738
- TodoComment src/views/text_input.rs:1261
- TodoComment src/views/editor/actions.rs:55
- TodoComment src/views/editor/actions.rs:77
- TodoComment src/views/editor/actions.rs:117
- TodoComment src/views/editor/mod.rs:1435
- TodoComment src/views/editor/actions.rs:164
- TodoComment src/views/editor/actions.rs:175
- TodoComment src/views/editor/gutter.rs:99
- TodoComment src/views/editor/gutter.rs:119
- TodoComment src/views/editor/view.rs:650
- TodoComment src/views/editor/gutter.rs:128
- TodoComment src/views/editor/view.rs:660
- FileTooLong: style/mod.rs src/style/mod.rs
- FileTooLong: style/values.rs src/style/values.rs
- FileTooLong: event/dispatch.rs src/event/dispatch.rs
- FileTooLong: src/lib.rs tiny_skia/src/lib.rs
- FileTooLong: src/editor.rs editor-core/src/editor.rs
- FileTooLong: window/handle.rs src/window/handle.rs
- FileTooLong: editor/visual_line.rs src/views/editor/visual_line.rs
- FileTooLong: editor/mod.rs src/views/editor/mod.rs
- FileTooLong: views/text_input.rs src/views/text_input.rs
- FileTooLong: editor/view.rs src/views/editor/view.rs
- FileTooLong: window/state.rs src/window/state.rs
- FileTooLong: view/id.rs src/view/id.rs
- FileTooLong: inspector/mod.rs src/inspector/mod.rs
- FileTooLong: views/scroll.rs src/views/scroll.rs
- FileTooLong: animate/mod.rs src/animate/mod.rs
- FileTooLong: event/mod.rs src/event/mod.rs
- FileTooLong: style/theme.rs src/style/theme.rs
- FileTooLong: app/handle.rs src/app/handle.rs
- FileTooLong: src/signal.rs reactive/src/signal.rs
- FileTooLong: view/mod.rs src/view/mod.rs
- FileTooLong: inspector/view.rs src/inspector/view.rs
- FileTooLong: style/components.rs src/style/components.rs
- FileTooLong: src/lib.rs vger/src/lib.rs
- FileTooLong: style/cx.rs src/style/cx.rs
- FileTooLong: event/listener.rs src/event/listener.rs
- ClassTooLong: WindowHandle src/window/handle.rs:74
- ClassTooLong: RouteCx src/event/dispatch.rs:501
- ClassTooLong: Style src/style/mod.rs:862
- ClassTooLong: TextInput src/views/text_input.rs:127
- ClassTooLong: Editor src/views/editor/mod.rs:151
- ClassTooLong: ViewId src/view/id.rs:58
- ClassTooLong: WindowState src/window/state.rs:100
- ClassTooLong: ApplicationHandle src/app/handle.rs:45
- ClassTooLong: Animation src/animate/mod.rs:359
- ClassTooLong: VgerRenderer vger/src/lib.rs:31
- ClassTooLong: EditorView src/views/editor/view.rs:347
- ClassTooLong: TinySkiaRenderer tiny_skia/src/lib.rs:870
- ClassTooLong: StyleCx src/style/cx.rs:86
- ClassTooLong: Layer tiny_skia/src/lib.rs:252
- ClassTooLong: Buffer editor-core/src/buffer/mod.rs:75
- ClassTooLong: VelloRenderer vello/src/lib.rs:25
- floem::style::resolve_selectors (cognitive 68) src/style/mod.rs:704
- floem::view::paint_border (cognitive 43) src/view/mod.rs:1291
- floem::views::virtual_stack::virtual_stack (cognitive 37) src/views/virtual_stack.rs:263
- floem::views::editor::movement::do_multi_selection (cognitive 36) src/views/editor/movement.rs:663
- floem::inspector::view::capture_view (cognitive 25) src/inspector/view.rs:180
- floem::views::list::list (cognitive 23) src/views/list.rs:83
- floem::platform::context_menu::context_menu_view::view_fn (cognitive 20) src/platform/context_menu.rs:120
- floem::inspector::add_event (cognitive 18) src/inspector/mod.rs:595
- floem::views::dyn_stack::diff (cognitive 18) src/views/dyn_stack.rs:194
- floem::views::editor::view::editor_view (cognitive 18) src/views/editor/view.rs:1082
- floem::views::svg::brush_to_css_string (cognitive 18) src/views/svg.rs:350
- floem::inspector::view::capture (cognitive 17) src/inspector/view.rs:41
- floem::paint::collect_visual_order (cognitive 17) src/paint/mod.rs:146
- floem::view::apply_keyed_diff (cognitive 17) src/view/mod.rs:620
- floem::window::state::build_focus_space_for_scope (cognitive 17) src/window/state.rs:46
- TooManyMethods: Style src/style/mod.rs:862
- TooManyMethods: ViewId src/view/id.rs:58
- TooManyMethods: Editor src/views/editor/mod.rs:151
- TooManyMethods: WindowState src/window/state.rs:100
- TooManyMethods: Animation src/animate/mod.rs:359
- TooManyMethods: HeadlessHarness src/headless.rs:101
- TooManyMethods: WindowHandle src/window/handle.rs:74
- TooManyMethods: ExprStyle src/style/mod.rs:239
- TooManyMethods: StyleReason src/style/recalc.rs:82
- TooManyMethods: RouteCx src/event/dispatch.rs:501
- TooManyMethods: TextLayout src/text/layout.rs:154
- TooManyMethods: Buffer editor-core/src/buffer/mod.rs:75
- TooManyMethods: Lines src/views/editor/visual_line.rs:295
- TooManyMethods: Selection editor-core/src/selection.rs:38
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (11 lines × 2) src/event/drag_state.rs:615
- Duplicated block (11 lines × 2) src/headless.rs:568
- Duplicated block (11 lines × 2) src/headless.rs:615
- Duplicated block (11 lines × 2) src/headless.rs:688
- Duplicated block (11 lines × 2) src/style/cx.rs:817
- Duplicated block (11 lines × 2) src/style/theme.rs:129
- Duplicated block (11 lines × 2) src/text/layout_state.rs:156
- Duplicated block (11 lines × 2) src/text/layout_state.rs:236
- Duplicated block (11 lines × 2) src/view/mod.rs:389
- Duplicated block (11 lines × 2) src/views/container.rs:106
- Duplicated block (11 lines × 2) src/views/slider.rs:443
- FunctionTooLong: floem::style::theme::default_theme src/style/theme.rs:550
- FunctionTooLong: floem::inspector::view::capture_view src/inspector/view.rs:180
- FunctionTooLong: floem::platform::context_menu::context_menu_view src/platform/context_menu.rs:102
- FunctionTooLong: floem::views::virtual_stack::virtual_stack src/views/virtual_stack.rs:263
- FunctionTooLong: floem::inspector::profiler::profile_view src/inspector/profiler.rs:74
- FunctionTooLong: floem::inspector::selected_view src/inspector/mod.rs:725
- FunctionTooLong: floem_editor_core::buffer::diff::rope_diff editor-core/src/buffer/diff.rs:77
- FunctionTooLong: floem::inspector::box_model_view src/inspector/mod.rs:352
- FunctionTooLong: floem::views::editor::view::editor_content src/views/editor/view.rs:1364
- FunctionTooLong: floem::view::paint_border src/view/mod.rs:1291
- MethodTooLong: StyleCx.style_view src/style/cx.rs:241
- MethodTooLong: WindowHandle.process_update_messages src/window/handle.rs:1102
- MethodTooLong: SkiaRenderer.replay skia/src/lib.rs:151
- MethodTooLong: TextInput.handle_key_down src/views/text_input.rs:890
- MethodTooLong: TextInput.event src/views/text_input.rs:1254
- MethodTooLong: ApplicationHandle.handle_window_event src/app/handle.rs:246
- MethodTooLong: ObjectPosition.debug_view src/style/values.rs:469
- MethodTooLong: BorderPathIter.next src/paint/border_path_iter.rs:95
- MethodTooLong: Event.listener_keys src/event/mod.rs:2023
- Duplicated block (12 lines × 2) editor-core/src/cursor.rs:325
- Duplicated block (12 lines × 2) editor-core/src/editor.rs:1268
- Duplicated block (12 lines × 2) reactive/src/context.rs:46
- Duplicated block (12 lines × 2) reactive/src/context.rs:91
- Duplicated block (12 lines × 2) src/event/drag_state.rs:600
- Duplicated block (12 lines × 2) src/headless.rs:743
- Duplicated block (12 lines × 2) src/receiver_signal/common/executors.rs:695
- Duplicated block (12 lines × 2) src/views/scroll.rs:239
- Duplicated block (12 lines × 2) vger/src/lib.rs:606
- Duplicated block (5 lines × 2) editor-core/src/cursor.rs:318
- Duplicated block (5 lines × 2) editor-core/src/editor.rs:234
- Duplicated block (5 lines × 2) editor-core/src/word.rs:206
- Duplicated block (5 lines × 2) src/animate/mod.rs:1110
- Duplicated block (5 lines × 2) src/paint/renderer.rs:96
- Duplicated block (5 lines × 2) src/view/state.rs:544
- Duplicated block (5 lines × 2) editor-core/src/editor.rs:400
- Duplicated block (5 lines × 2) src/style/values.rs:916
- Duplicated block (5 lines × 2) src/style/values.rs:941
- Duplicated block (8 lines × 2) editor-core/src/buffer/rope_text.rs:128
- Duplicated block (8 lines × 2) reactive/src/context.rs:83
- Duplicated block (8 lines × 2) src/event/drag_state.rs:537
- Duplicated block (8 lines × 2) src/platform/context_menu.rs:58
- Duplicated block (8 lines × 2) src/receiver_signal/future_signal/builder.rs:140
- Duplicated block (8 lines × 2) src/views/editor/mod.rs:378
- Duplicated block (8 lines × 2) src/receiver_signal/channel_signal/builder.rs:96
- Duplicated block (8 lines × 2) src/receiver_signal/channel_signal/builder.rs:109
- floem::style::resolve_selectors (cyclomatic 35) src/style/mod.rs:704
- floem::view::paint_border (cyclomatic 23) src/view/mod.rs:1291
- floem::views::virtual_stack::virtual_stack (cyclomatic 21) src/views/virtual_stack.rs:263
- floem::views::editor::movement::do_multi_selection (cyclomatic 19) src/views/editor/movement.rs:663
- floem::platform::context_menu::context_menu_view (cyclomatic 18) src/platform/context_menu.rs:102
- floem::inspector::view::capture (cyclomatic 17) src/inspector/view.rs:41
- floem::inspector::view::capture_view (cyclomatic 17) src/inspector/view.rs:180
- FixmeComment tiny_skia/src/lib.rs:817
- FixmeComment tiny_skia/src/lib.rs:1484
- FixmeComment tiny_skia/src/lib.rs:1669
- FixmeComment src/inspector/profiler.rs:308
- FixmeComment editor-core/src/buffer/rope_text.rs:306
- FixmeComment editor-core/src/buffer/rope_text.rs:339
- FixmeComment editor-core/src/buffer/test.rs:79
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (13 lines × 2) editor-core/src/editor.rs:1127
- Duplicated block (13 lines × 2) src/animate/mod.rs:1004
- Duplicated block (13 lines × 2) src/event/dispatch.rs:1400
- Duplicated block (13 lines × 2) src/receiver_signal/common/executors.rs:423
- Duplicated block (13 lines × 2) src/receiver_signal/common/executors.rs:439
- Duplicated block (13 lines × 2) src/view/id.rs:393
- Duplicated block (13 lines × 2) src/view/mod.rs:335
- Duplicated block (9 lines × 2) editor-core/src/editor.rs:1199
- Duplicated block (9 lines × 2) src/inspector/view.rs:763
- Duplicated block (9 lines × 2) src/style/values.rs:1971
- Duplicated block (9 lines × 2) src/text/layout.rs:746
- Duplicated block (9 lines × 2) src/views/editor/movement.rs:680
- Duplicated block (9 lines × 2) src/views/text_editor.rs:79
- Duplicated block (9 lines × 2) src/views/text_input.rs:1014
- RouteCx::element_tab_navigation (cognitive 47) src/event/dispatch.rs:1717
- RouteCx::handle_default_behaviors (cognitive 30) src/event/dispatch.rs:1094
- RouteCx::dispatch_directed (cognitive 26) src/event/dispatch.rs:679
- RouteCx::handle_pointer_state_updates (cognitive 22) src/event/dispatch.rs:2059
- RouteCx::push_hover_events (cognitive 18) src/event/dispatch.rs:2001
- RouteCx::element_arrow_navigation (cognitive 17) src/event/dispatch.rs:1851
- RouteCx::handle_default_behaviors (cyclomatic 24) src/event/dispatch.rs:1094
- RouteCx::element_arrow_navigation (cyclomatic 18) src/event/dispatch.rs:1851
- RouteCx::handle_pointer_state_updates (cyclomatic 18) src/event/dispatch.rs:2059
- RouteCx::element_tab_navigation (cyclomatic 17) src/event/dispatch.rs:1717
- RouteCx::dispatch_directed (cyclomatic 16) src/event/dispatch.rs:679
- Action::do_edit (cognitive 237) editor-core/src/editor.rs:775
- Action::insert (cognitive 95) editor-core/src/editor.rs:89
- Action::do_paste (cognitive 28) editor-core/src/editor.rs:567
- Action::do_outdent (cognitive 20) editor-core/src/editor.rs:697
- Action::do_indent (cognitive 16) editor-core/src/editor.rs:667
- Duplicated block (18 lines × 2) reactive/src/scope.rs:297
- Duplicated block (18 lines × 2) src/app/handle.rs:918
- Duplicated block (18 lines × 2) src/event/mod.rs:1960
- Duplicated block (18 lines × 2) src/receiver_signal/common/executors.rs:477
- Duplicated block (18 lines × 2) src/receiver_signal/resource/builder.rs:582
- Duplicated block (7 lines × 2) editor-core/src/editor.rs:1337
- Duplicated block (7 lines × 2) src/views/list.rs:59
- Duplicated block (7 lines × 2) src/animate/easing.rs:273
- Duplicated block (7 lines × 2) src/views/editor/mod.rs:1311
- Duplicated block (7 lines × 2) src/views/editor/text.rs:378
- Duplicated block (6 lines × 2) src/event/dispatch.rs:728
- Duplicated block (6 lines × 2) src/inspector/view.rs:744
- Duplicated block (6 lines × 2) src/platform/context_menu.rs:34
- Duplicated block (6 lines × 2) src/style/values.rs:329
- Duplicated block (6 lines × 2) src/views/virtual_stack.rs:204
- Low cohesion: Style (LCOM4 13) src/style/mod.rs:862
- Low cohesion: ViewId (LCOM4 7) src/view/id.rs:58
- Low cohesion: Id (LCOM4 4) reactive/src/id.rs:12
- Low cohesion: Animation (LCOM4 4) src/animate/mod.rs:359
- Low cohesion: WindowState (LCOM4 4) src/window/state.rs:100
- floem_editor_core::buffer::diff::rope_diff (cognitive 67) editor-core/src/buffer/diff.rs:77
- floem_editor_core::buffer::diff::expand_diff_lines (cognitive 30) editor-core/src/buffer/diff.rs:39
- floem_editor_core::indent::auto_detect_indent_style (cognitive 30) editor-core/src/indent.rs:101
- floem_editor_core::util::has_unmatched_pair (cognitive 17) editor-core/src/util.rs:85
- ApplicationHandle::handle_update_event (cognitive 45) src/app/handle.rs:131
- ApplicationHandle::new_window (cognitive 33) src/app/handle.rs:429
- ApplicationHandle::handle_window_event (cognitive 18) src/app/handle.rs:246
- ApplicationHandle::handle_updates_for_all_windows_budgeted (cognitive 16) src/app/handle.rs:672
- Cursor::yank (cognitive 34) editor-core/src/cursor.rs:384
- Cursor::set_offset (cognitive 33) editor-core/src/cursor.rs:509
- Cursor::edit_selection (cognitive 20) editor-core/src/cursor.rs:293
- Cursor::add_region (cognitive 17) editor-core/src/cursor.rs:609
- Change coupling: container.rs ↔ stack.rs src/views/container.rs:1
- Change coupling: mod.rs ↔ context.rs src/app/mod.rs:1
- Change coupling: label.rs ↔ stack.rs src/views/label.rs:1
- Change coupling: label.rs ↔ tab.rs src/views/label.rs:1
- Duplicated block (14 lines × 2) src/receiver_signal/common/executors.rs:460
- Duplicated block (14 lines × 2) src/receiver_signal/resource/builder.rs:471
- Duplicated block (14 lines × 2) src/style/values.rs:2301
- Duplicated block (14 lines × 2) src/paint/border_path_iter.rs:147
- Duplicated block (10 lines × 2) src/headless.rs:608
- Duplicated block (10 lines × 2) src/headless.rs:629
- Duplicated block (10 lines × 2) src/receiver_signal/common/executors.rs:684
- Duplicated block (10 lines × 2) src/views/container.rs:62
- ApplicationHandle::handle_window_event (cyclomatic 64) src/app/handle.rs:246
- ApplicationHandle::handle_update_event (cyclomatic 29) src/app/handle.rs:131
- ApplicationHandle::new_window (cyclomatic 29) src/app/handle.rs:429
- TextInput::handle_key_down (cognitive 46) src/views/text_input.rs:890
- TextInput::event (cognitive 45) src/views/text_input.rs:1254
- TextInput::move_cursor (cognitive 20) src/views/text_input.rs:396
- Members sharing a duplicated core (4 members, 50+ identical tokens) src/receiver_signal/common/executors.rs:422
- Members sharing a duplicated core (4 members, 50+ identical tokens) src/style/components.rs:225
- Members sharing a duplicated core (4 members, 50+ identical tokens) src/style/components.rs:262
- Duplicated block (8 lines × 3) editor-core/src/editor.rs:1268
- Duplicated block (8 lines × 3) src/views/editor/view.rs:438
- Duplicated block (8 lines × 3) reactive/src/effect.rs:45
- Duplicated block (5 lines × 4) editor-core/src/editor.rs:1266
- Duplicated block (5 lines × 4) src/style/components.rs:229
- Duplicated block (5 lines × 4) src/style/components.rs:265
- Off the main sequence: floem-editor-core
- Off the main sequence: floem_renderer
- Off the main sequence: floem_reactive
- Action::do_edit (cyclomatic 124) editor-core/src/editor.rs:775
- Action::insert (cyclomatic 33) editor-core/src/editor.rs:89
- WindowHandle::process_update_messages (cyclomatic 49) src/window/handle.rs:1102
- WindowHandle::set_cursor (cyclomatic 28) src/window/handle.rs:1424
- floem_editor_core::buffer::diff::rope_diff (cyclomatic 34) editor-core/src/buffer/diff.rs:77
- floem_editor_core::indent::auto_detect_indent_style (cyclomatic 21) editor-core/src/indent.rs:101
- TextInput::event (cyclomatic 31) src/views/text_input.rs:1254
- TextInput::handle_key_down (cyclomatic 29) src/views/text_input.rs:890
- XxxComment src/window/id.rs:332
- XxxComment src/window/id.rs:341
- Style::apply_iter (cognitive 44) src/style/mod.rs:1301
- Style::inherited_equal (cognitive 16) src/style/cache.rs:569
- Scroll::event (cognitive 38) src/views/scroll.rs:959
- Scroll::paint (cognitive 17) src/views/scroll.rs:1046
- WindowHandle::process_update_messages (cognitive 38) src/window/handle.rs:1102
- WindowHandle::process_update_budgeted (cognitive 21) src/window/handle.rs:943
- Animation::advance (cognitive 32) src/animate/mod.rs:816
- Animation::animate_into (cognitive 20) src/animate/mod.rs:1075
- EditorView::paint_normal_selection (cognitive 21) src/views/editor/view.rs:467
- EditorView::paint_text (cognitive 19) src/views/editor/view.rs:871
- DragTracker::on_pointer_move (cognitive 19) src/event/drag_state.rs:474
- DragTracker::on_pointer_up (cognitive 18) src/event/drag_state.rs:596
- TooManyFields: WindowState src/window/state.rs:100
- TooManyFields: ViewState src/view/state.rs:321
- Members sharing a duplicated core (5 members, 50+ identical tokens) src/style/components.rs:234
- Members sharing a duplicated core (5 members, 50+ identical tokens) src/views/editor/gutter.rs:187
- Duplicated block (21 lines × 2) src/receiver_signal/common/executors.rs:226
- Duplicated block (21 lines × 2) src/receiver_signal/resource/builder.rs:485
- Duplicated block (17 lines × 2) editor-core/src/editor.rs:800
- Duplicated block (17 lines × 2) src/animate/easing.rs:254
- Duplicated block (12–13 lines × 2) editor-core/src/editor.rs:1352
- Duplicated block (12–13 lines × 2) vello/src/lib.rs:112
- Duplicated block (11 lines × 6) src/receiver_signal/common/executors.rs:37
- Duplicated block (11 lines × 6) src/style/mod.rs:3252
- Duplicated block (7 lines × 3) src/receiver_signal/resource/builder.rs:468
- Duplicated block (7 lines × 3) src/style/transition.rs:185
- Duplicated block (6–7 lines × 2) src/paint/border_path_iter.rs:167
- Duplicated block (6–7 lines × 2) src/style/mod.rs:932
- Duplicated block (6 lines × 3) editor-core/src/editor.rs:1250
- Duplicated block (6 lines × 3) src/views/label.rs:214
- StyleCx::style_view (cyclomatic 51) src/style/cx.rs:241
- GlobalEventCx::route_window_event (cyclomatic 24) src/event/dispatch.rs:358
- Scroll::event (cyclomatic 22) src/views/scroll.rs:959
- Animation::advance (cyclomatic 20) src/animate/mod.rs:816
- BorderPathIter::next (cyclomatic 20) src/paint/border_path_iter.rs:95
- Style::apply_iter (cyclomatic 20) src/style/mod.rs:1301
- Label::event (cyclomatic 19) src/views/label.rs:396
- StylePropInfo::new (cyclomatic 17) src/style/props.rs:205
- Cursor::set_offset (cyclomatic 16) editor-core/src/cursor.rs:509
- ParseList::next (cyclomatic 16) renderer/src/text/attrs.rs:655
- SvgLayoutData::create_taffy_layout_fn (cyclomatic 16) src/views/svg.rs:60
- Yanked release: clipboard-win
- HackComment src/views/editor/view.rs:158
- StyleCx::style_view (cognitive 88) src/style/cx.rs:241
- GlobalEventCx::route_window_event (cognitive 62) src/event/dispatch.rs:358
- BorderPathIter::next (cognitive 45) src/paint/border_path_iter.rs:95
- EventCx::dispatch_one (cognitive 35) src/event/dispatch.rs:940
- Buffer::compute_undo (cognitive 27) editor-core/src/buffer/mod.rs:509
- TextLayout::selection_geometry_with_line_metrics (cognitive 27) src/text/layout.rs:663
- Resizable::update (cognitive 27) src/views/resizable.rs:405
- WindowState::build_style_traversal (cognitive 27) src/window/state.rs:423
- EditorGutterView::paint (cognitive 26) src/views/editor/gutter.rs:87
- Label::event (cognitive 25) src/views/label.rs:396
- SvgLayoutData::create_taffy_layout_fn (cognitive 24) src/views/svg.rs:60
- InspectorImageView::event (cognitive 22) src/inspector/view.rs:722
- StylePropInfo::new (cognitive 20) src/style/props.rs:205
- TextLayoutState::finalize_for_width (cognitive 19) src/text/layout_state.rs:263
- VgerRenderer::fill (cognitive 19) vger/src/lib.rs:423
- ToggleButton::event (cognitive 18) src/views/toggle_button.rs:325
- TinySkiaRenderer::finish (cognitive 18) tiny_skia/src/lib.rs:1497
- CapturedData::get_children (cognitive 17) src/inspector/data.rs:167
- Dropdown::update (cognitive 17) src/views/dropdown.rs:235
- REDACTED
- Change-coupling hub: scroll.rs → clip.rs, container.rs, tab.rs, virtual_list.rs src/views/scroll.rs
- REDACTED
- REDACTED
- Near-duplicate member family (6 members, 24 shared lines) src/receiver_signal/common/executors.rs:21
- Near-duplicate member family (4 members, 21 shared lines) src/receiver_signal/common/executors.rs:336
- Near-duplicate member pair (33 shared lines) src/receiver_signal/common/executors.rs:668
- Edited copy of a member (33 corresponding lines) src/platform/context_menu.rs:33
- Edited copy of a member (13 corresponding lines) vger/src/lib.rs:605
- Edited copy of a member (12 corresponding lines) src/views/img.rs:157
- Members sharing a duplicated core (6 members, 50+ identical tokens) src/style/mod.rs:3251
- Duplicated block (37–38 lines × 2) src/window/handle.rs:947
- Duplicated block (28 lines × 2) src/views/editor/mod.rs:1045
- Duplicated block (27 lines × 2) vello/src/lib.rs:541
- Duplicated block (23–24 lines × 2) vello/src/lib.rs:84
- Duplicated block (23 lines × 2) vello/src/lib.rs:60
- Duplicated block (21 lines × 4) src/receiver_signal/common/executors.rs:24
- Duplicated block (19–20 lines × 3) src/views/label.rs:361
- Duplicated block (20 lines × 2) editor-core/src/editor.rs:668
- Duplicated block (19 lines × 2) src/views/editor/text.rs:386
- Duplicated block (18–19 lines × 2) src/window/handle.rs:698
- Duplicated block (16 lines × 2) editor-core/src/editor.rs:1281
- Duplicated block (12–16 lines × 2) src/style/cx.rs:871
- Duplicated block (15 lines × 2) src/animate/mod.rs:1018
- Duplicated block (14 lines × 5) src/style/components.rs:236
- Duplicated block (14 lines × 3) src/event/drag_state.rs:675
- Duplicated block (13 lines × 6) src/receiver_signal/common/executors.rs:22
- Duplicated block (13 lines × 4) src/views/editor/gutter.rs:249
- Duplicated block (10–11 lines × 6) src/receiver_signal/common/executors.rs:337
- Duplicated block (11 lines × 4) src/receiver_signal/common/executors.rs:360
- Duplicated block (8–11 lines × 2) src/text/layout.rs:569
- Duplicated block (10 lines × 3) editor-core/src/editor.rs:1291
- Duplicated block (6–10 lines × 3) src/views/label.rs:230
- Duplicated block (8–10 lines × 2) src/views/editor/visual_line.rs:602
- Duplicated block (9 lines × 3) src/style/components.rs:358
- Duplicated block (9 lines × 4) src/views/scroll.rs:973
- Duplicated block (8 lines × 4) src/receiver_signal/common/executors.rs:426
- Duplicated block (7–8 lines × 2) src/views/img.rs:162
- Duplicated block (5 lines × 3) src/views/editor/mod.rs:683
- Duplicated block (3–5 lines × 3) vello/src/lib.rs:245
- Unstable project floem
Minor — 96 finding(s)
- Orphaned file src/event/drag_state.rs:1
- Orphaned file editor-core/src/selection.rs:1
- Orphaned file src/views/editor/movement.rs:1
- Orphaned file src/text/layout.rs:1
- Orphaned file reactive/src/signal.rs:1
- Orphaned file reactive/src/context.rs:1
- Orphaned file editor-core/src/cursor.rs:1
- Orphaned file editor-core/src/buffer/mod.rs:1
- Orphaned file editor-core/src/buffer/rope_text.rs:1
- Orphaned file src/views/editor/text.rs:1
- Orphaned file editor-core/src/word.rs:1
- Orphaned file src/receiver_signal/common/executors.rs:1
- Orphaned file src/views/navigation_stack.rs:1
- Orphaned file src/receiver_signal/resource/builder.rs:1
- Orphaned file editor-core/src/command.rs:1
- Orphaned file src/paint/border_path_iter.rs:1
- Orphaned file skia/src/lib.rs:1
- Orphaned file src/style/custom.rs:1
- Orphaned file editor-core/src/line_ending.rs:1
- Orphaned file src/platform/context_menu.rs:1
- Orphaned file reactive/src/effect.rs:1
- Orphaned file reactive/src/derived.rs:1
- Orphaned file reactive/src/scope.rs:1
- Orphaned file src/views/editor/text_document.rs:1
- Orphaned file src/animate/easing.rs:1
- Most significant orphaned file editor-core/src/editor.rs:1
- Most significant orphaned file src/event/listener.rs:1
- Most significant orphaned file editor-core/src/char_buffer.rs:1
- Duplicated predicate src/style/cx.rs:874
- Duplicated predicate src/style/cx.rs:820
- Off-boarding risk: anonymized user #1
- Projects may be oversized for their cohesion
- Concentrated knowledge decay
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Inverted test pyramid
- Event not named in past tense: UpdatePhase src/event/mod.rs:701
- No ADRs
- Large public API surface
Minor — 27 finding(s)
- Outdated: anyhow
- Outdated: bitflags
- Outdated: console_log
- Outdated: crossbeam
- Outdated: futures
- Outdated: image
- Outdated: imbl
- Outdated: indexmap
- Outdated: kurbo
- Outdated: memchr
- Outdated: objc2
- Outdated: open
- Outdated: palette
- Outdated: peniko
- Outdated: rustc-hash
- Outdated: serde
- Outdated: serde_json
- Outdated: smallvec
- Outdated: swash
- Outdated: thiserror
- Outdated: time
- Outdated: tokio
- Outdated: tokio-stream
- Outdated: unicode-segmentation
- Outdated: wasm-bindgen
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-62ea341205d44198ae44af533859622a/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-62ea341205d44198ae44af533859622a/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 10 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-0b748ebdfaaa45e6b577be6a24d7f720 | 30 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-0b748ebdfaaa45e6b577be6a24d7f720 | 0 | artifacts/raw/osv-scanner.json |