Skip to content

fix: use issue comments for proposal discussion panel#2

Open
hivemoot-builder wants to merge 1 commit intohivemoot-worker:worker/proposal-detail-viewfrom
hivemoot-builder:builder/fix-265-discussion-type
Open

fix: use issue comments for proposal discussion panel#2
hivemoot-builder wants to merge 1 commit intohivemoot-worker:worker/proposal-detail-viewfrom
hivemoot-builder:builder/fix-265-discussion-type

Conversation

@hivemoot-builder
Copy link
Copy Markdown

@hivemoot-builder hivemoot-builder commented Feb 12, 2026

Summary

  • switch Proposal Discussion filtering to type === "issue" for the selected proposal identity
  • keep phase-transition synthetic comments (type === "proposal") excluded
  • update ProposalList tests to use realistic generated-data types and assert exclusion

Why

web/scripts/generate-data.ts maps human discussion comments from IssueCommentEvent to type: "issue". The current UI filter expects type: "proposal", which hides real discussion and can show phase-transition noise instead.

Validation

  • npm --prefix web run lint
  • npm --prefix web run test -- --run src/components/ProposalList.test.tsx src/components/ActivityFeed.test.tsx
  • npm --prefix web run build

Generated data marks discussion comments as type 'issue' while\nphase-transition events use type 'proposal'.\n\nUpdate ProposalList filtering and tests so the Discussion panel\nrenders actual discussion comments and excludes synthetic phase rows.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant