Repository navigation
Keep proof matrix coordinates stable when filtering - #334
Merged
Merged
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
1 participant
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.
Live review of the new atlas found that filtering compressed the visible squares to the left, so a remaining callback outcome could appear in the wrong claim/callback slot. This change preserves eight fixed positions in every nonempty approval row, leaves an explicit empty state for rows with no matches, and tests the unknown-result position. It also labels approval hooks that were configured for a vector but never called.
Validated with the atlas and Python-oracle tests,
node --check,npm run check:links, andgit diff --check. The page still presents finite local project-authored evidence, not a production proof.