Repository navigation
feat(frontend): add EvidenceLedgerPage with status and category filters - #389
Open
Anshuu2004 wants to merge 1 commit into
Open
Anshuu2004 wants to merge 1 commit into
Anshuu2004 wants to merge 1 commit into
Conversation
New /readiness/evidence page that lists the claims from GET /api/v1/evidence/claims in a semantic table: claim text, category, source (http/https links only), verification badge, confidence and last checked date. Status and category chips are sent to the API as subjectType/verificationStatus, search runs client side over claim text, key, source and category label. VerificationBadge always prints the status as text (Verified, Partially verified, Unverified, Flagged) so colour is never the only signal. The readiness overview gets an Evidence Ledger card that links to the page. Re-verify, GapToMilestoneDialog and TopGapsPanel are left out because the endpoints they need do not exist yet. Closes VarshithReddy2006#336 Signed-off-by: Abhishek <abhishekcse2004@gmail.com>
Owner
|
@Anshuu2004 CI/CD checks are currently failing on
This failure occurs because public profiles are now private by default with opt-in publication (from PR #381).
Please rebase/merge the latest |
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
Adds the Evidence Ledger page at
/readiness/evidence. It lists the signed-in user's claims fromGET /api/v1/evidence/claimswith filters, a search box and a verification badge that always carries a text label.Closes #336
What changed
frontend/src/services/evidenceService.ts:fetchEvidenceClaims(filters), types mirroring the backend model (4 statuses: verified, partial, unverified, flagged; 5 subject types).frontend/src/pages/readiness/EvidenceLedgerPage.tsx: status chips and category chips (sent to the API asverificationStatus/subjectType), client side search over claim text, key, source and category label, loading / error (with retry) / empty / no-match states, semantic<table>with caption andscopeheaders.VerificationBadge: prints "Verified", "Partially verified", "Unverified" or "Flagged" next to the icon, so colour is not the only signal.EvidenceClaimRow: source link (only http/https urls become anchors,rel="noopener noreferrer"), confidence, last checked date, stale hint whenstaleAfterhas passed, flag reason when present. Legacy claims with no subject type are shown as resume claims, same as the backend does.useEvidenceClaimshook (react-query, filters in the query key)./readiness/evidenceinrouter/index.tsxand an "Evidence Ledger" card on the readiness overview.How I tested
Run from
frontend/, one file at a time:The route test fails with the
router/index.tsxchange stashed (heading not found) and passes with it.tsc -p tsconfig.app.json --noEmitreports no errors in the files touched here (the checkout I tested in has a few unrelated missing-module errors from its node_modules).Notes
GapToMilestoneDialog,TopGapsPanel/ReadinessInputsPaneland the SSE refresh, because the endpoints they need (re-verify,POST /job-targets/:id/gaps/:gapId/milestone) do not exist on main.docs/v2/*.mdnamed in the issue are not in the repo, so no docs change.