Skip to content

docs: note the renamed-FK diagram notation change in What's New 2.3.2#237

Open
dimitri-yatsenko wants to merge 1 commit into
mainfrom
docs/whats-new-2.3.2-diagram-notation
Open

docs: note the renamed-FK diagram notation change in What's New 2.3.2#237
dimitri-yatsenko wants to merge 1 commit into
mainfrom
docs/whats-new-2.3.2-diagram-notation

Conversation

@dimitri-yatsenko

Copy link
Copy Markdown
Member

Follow-up to #235. The What's New in 2.3.2 section omitted a user-visible change that shipped in the release: the renamed/aliased foreign-key diagram notation changed from an orange alias dot to an orange edge (with a renamed-columns hover tooltip), via the nx.MultiDiGraph migration (datajoint-python#1508).

That change was documented in the diagram how-to and specs (#215) but not surfaced in the release notes — it was mis-classified as a purely internal refactor. This adds a Changes in 2.3.2 bullet describing the notation change and linking Read Diagrams. No other content changes.

The nx.MultiDiGraph migration (#1508) shipped a user-visible rendering
change — renamed/aliased foreign keys now draw as orange edges (with a
renamed-columns tooltip) instead of an orange alias dot — documented in
the diagram how-to/specs (#215) but missing from What's New. Add it to
Changes in 2.3.2.
@dimitri-yatsenko dimitri-yatsenko added the documentation Improvements or additions to documentation label Jul 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants