fix(wiki): preserve graph and tenant integrity#1660
Open
yangcongcong-coding wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
in_links + out_linkstenant_idRoot cause
Reciprocal Wiki links appear in both
in_linksandout_links. Adding both array lengths double-counts the same neighbor, while missing and self-referential targets are counted even though the graph cannot render them. This can make the sidebar report an unreachable or dead neighbor when every real neighbor is present.The built-in Wiki fixer creates pages without setting
TenantID.CreatePagepreviously persisted that zero value instead of resolving ownership from the parent knowledge base, leaving tenantless Wiki rows.Impact
Validation
gofmtandgit diff --checkalso pass.