Closed
Conversation
…provements - Add error tracking as signal source with 3 sub-types toggled together - Replace non-functional LLM analytics toggle with evaluations list (polls 5s) - Evaluations link to Cloud for management (region-aware) - Fix re-render cascade: direct API calls, per-source optimistic state - Per-source onToggle API with memoized cards - Rounded toggle cards, GitHub OAuth flow - Add suggested reviewer + artefact types
- Consistent SignalCardHeader: colored dot + "Product · Type" + Weight badge - Source-specific cards: error tracking (fingerprint), GitHub (labels, link), Zendesk (priority/status/tags), LLM analytics (model/provider/trace) - Cloud-exact source line labels and product colors - Type guards dispatch signals to correct card variant
sortafreel
changed the base branch from
twixes/inbox-signal-cards
to
twixes/inbox-source-filter
Twixes
force-pushed
the
twixes/inbox-signal-cards
branch
from
d04184c to
015d5da
Compare
sortafreel
added a commit
that referenced
this pull request
Apr 8, 2026
- Add Priority and Actionability detail rows with collapsible "Why?" explanations from priority_judgment and actionability_judgment artefacts - Add 'already addressed' warning banner driven by report or judgment - Pass per-signal SignalFinding (verified flag, code paths, data queried) to SignalCard so the detail pane can surface research evidence - Add VerificationBadge to SignalCardHeader and CodePaths/DataQueried collapsibles inside each source-specific signal card variant - Add SignalReportActionabilityBadge alongside the existing priority/ status chips on the inbox list card - Restructure the evidence section in ReportDetailPane to surface loading and unavailable states (forbidden, not_found, invalid_payload, request_failed) so the user gets feedback when artefacts can't load - Add typed normalizers for priority_judgment, actionability_judgment and signal_finding artefacts in posthogClient - Drop the legacy JudgmentBadges component, which used an outdated Record<string, unknown> shape that no longer matches the typed artefact schema in shared/types Squashed-from: signals/new-report-data-in-inbox-ui-backup Originally PR #1428
Contributor
Author
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
2 participants
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.
Problem
We get plenty of data from the Signals report to:
But we don't show them in the UI
Changes
How did you test this?