Repository navigation
fix(frontend): add explicit canvas relationship filtering - #558
Draft
SHAURYAKSHARMA24 wants to merge 1 commit into
Draft
SHAURYAKSHARMA24 wants to merge 1 commit into
SHAURYAKSHARMA24 wants to merge 1 commit into
Conversation
|
@SHAURYAKSHARMA24 is attempting to deploy a commit to the parthrohit60-3117's projects Team on Vercel. A member of the Team first needs to authorize it. |
This was referenced Oct 8, 2026
This branch has not been deployed
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
Offer explicit canvas relationship-type selection, retain the full model for list and relationship views, and keep focus limiting for large graphs. Preserve all types by default.
Linked issue
Related to #507.
Scope
Audit F11; baseline dev
df0e82be3d7b2b7d846eefc1bcf82bde834936f2. This corrects independently verified existing behavior and advances the linked issue without adding product scope.What changed
Offer explicit canvas relationship-type selection, retain the full model for list and relationship views, and keep focus limiting for large graphs. Preserve all types by default.
Acceptance criteria completed
Implementation and targeted regression coverage below. See remaining work for conditions not verified.
Testing performed
10 graph layout/filter tests, frontend lint/build passed. Actual Chromium graph selector exercised on 88-node/640-edge fixture; screenshot inspected. Explicit filtering completed; default aggregation remains open.
Current head:
4375357b20d78ffc6dd9908ce2a32c1b54d37430; check snapshot appears below.Screenshots
Local screenshots and browser measurements are recorded in the remediation delivery report where applicable. Backend-only changes use contract/regression evidence.
Security and data considerations
Preserves owner scoping, source provenance, sealed graph contracts and historical data. No security gate weakened. Rollback: revert this scoped commit; see issue for migration/deployment implications.
Dependencies and blocked work
Independent dev-based PR unless explicitly stated in the issue. No unmerged changes included.
Scope changes or remaining work
Browser fixture currently has import edges only; mixed types are verified in unit regression. No evidence truncation, aggregation or schema change. Current-head CI and visual review required.
Please review @parthrohit22.
Contributor checklist
Targets dev; dedicated fork branch from latest dev; issue claimed.
Scope/evidence recorded; unrelated changes and secrets excluded.
Targeted validation results reported accurately.
Required current-head CI and maintainer review complete.
Current-head remediation validation
Head:
4375357b20d78ffc6dd9908ce2a32c1b54d37430.10 graph layout/filter tests, frontend lint/build passed. Actual Chromium graph selector exercised on 88-node/640-edge fixture; screenshot inspected. Explicit filtering completed; default aggregation remains open.
Browser fixture currently has import edges only; mixed types are verified in unit regression. No evidence truncation, aggregation or schema change. Current-head CI and visual review required.
Checks at delivery: Repository Hygiene: SUCCESS; Analyze (javascript-typescript): SUCCESS; Analyze (python): SUCCESS; API Contract Drift: SUCCESS; Frontend: FAILURE; Backend: SUCCESS; Docker Build: SUCCESS; Marketing Site: SUCCESS; Prototype Browser Acceptance: SKIPPED; Vercel: FAILURE; CodeQL: SUCCESS. Required checks/reviews must pass before merge; deployment authorization was not granted.