Skip to content

fix(voyager): refetch Related Entities sub-graph when main graph re-renders #100

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
allmonday merged 1 commit into from
Jul 3, 2026
+12 −0
Merged

fix(voyager): refetch Related Entities sub-graph when main graph re-renders #100

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
12 changes: 12 additions & 0 deletions src/nexusx/voyager/web/vue-main.js
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -201,6 +201,18 @@ const app = createApp({
const schemasArr = Array.isArray(data.schemas) ? data.schemas : []
store.state.erDiagramSchemas = Object.fromEntries(schemasArr.map((s) => [s.id, s]))
await graphUI.render(data.dot, resetZoom)
// Spec 007 fix — when the main graph re-renders because a display
// toggle (Hide Reverse Relationships / brief mode / cluster display /
// show methods / etc.) changed, the Related Entities sub-graph must
// refetch too, otherwise it keeps showing the previous config's data.
// fetchRelatedEntities has a dedup guard (spec 005 FR-011) that would
// skip the fetch when the same schemaName is open; clearing
// selectedSchema forces the next call to actually hit the server.
const openSubSchema = store.state.relatedEntities.selectedSchema
if (openSubSchema && store.state.relatedEntities.dot) {
store.state.relatedEntities.selectedSchema = ""
store.actions.fetchRelatedEntities(openSubSchema)
}
} catch (err) {
console.error(err)
} finally {
Expand Down