Skip to content

Fix the Relationships description in the v2.1.0 notes #93

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Mx-Iris merged 1 commit into from
Aug 12, 2026
+16 −4
Merged

Fix the Relationships description in the v2.1.0 notes #93

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 16 additions & 4 deletions Changelogs/v2.1.0.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,7 @@ release-candidate users too, not only to those coming from 2.0.x.
- **Multi-tab content navigation** with a window tab bar and per-tab history
- **Generic type specialization** — inspect Swift generics with concrete arguments filled in
- **Background indexing** — the sidebar is ready when you click into it, not seconds later
- **Inspector → Relationships** — see who references a type, and what a type depends on
- **Inspector → Relationships** — a class's subclasses and a protocol's conforming types, gathered across every indexed binary
- **Batch export** interfaces for multiple images in one pass
- **Theme settings** with a data-driven color model and a built-in Xcode preset
- **Jump to Definition** for Swift type references
Expand Down Expand Up @@ -48,9 +48,21 @@ interface alongside the original unspecialized form.
silently producing garbage.

#### Inspector → Relationships
A new **Relationships** tab sits between *Hierarchy* and *Specialization*. It
lists inbound references (who uses this type) and outbound references (what
this type depends on), drawn across every binary the document has loaded.
A new **Relationships** tab sits between *Hierarchy* and *Specialization*,
answering the question a single interface listing cannot: what else in the
loaded binaries builds on this type.

- Select a **class** and it lists that class's direct subclasses.
- Select a **protocol** and it lists the types that conform to it.

Both are unioned across every indexed image rather than looked up in the image
that defines the target, so a subclass or conformer living in a different
binary still shows up. Images that are loaded but not yet indexed contribute
nothing, so the list fills in as background indexing catches up.

Objective-C and Swift classes and protocols are covered, including classes
bridged between the two. Other kinds — structs, enums, categories — have no
relationships to show.

#### Jump to Definition for Swift types
Command-click a Swift type reference in the content view to navigate to its
Expand Down