Make session entities readable in a default List - #8
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.
People reviewing a conversation could not reliably read overlapping or clipped graph labels, especially on a phone. The session rail now opens with a native List of complete entity names, kinds, measured counts and typed relationships. Expandable rows distinguish unknown measurements and zero from traversal/visit activity. The optional Map uses the same live session; its label limitations remain. The mobile header scrolls with the content so enlarged names stay unobscured.
The existing browser journey now recognizes the populated List and drives details, Map/List switching, filters and two-turn draft continuity through native controls. Six scenario tests cover empty state, same-name entities, zero/unknown values, escaping, curated receipts and repeated updates. Three tour/walkthrough files are synchronized. Vendor, session data, provider/runtime adapters and dependency declarations are unchanged.
Validation: final ordinary
npm run checkpassed 63 tests in ten files, types, library/UI builds, tours and existing local source/scaffold checks; production audit reported zero findings. Seven viewport pairs, keyboard/two-turn continuity, touch emulation, computed doubled text and reduced motion were observed. After the mobile header correction, all six affected mobile/tablet conditions passed again; prior desktop observations retain their exact source/build continuity. Failed attempts were preserved, including the enlarged-header defect and corrected recorder boundaries. Convex/live-provider and physical-device checks remain unproven; this does not certify the optional Map, broader composer usability or full-product readiness.