Skip to content

Add comments to preference lists: per-applicant and group-wide - #179

Merged
adescoteaux1 merged 1 commit into
mainfrom
ally/preference-list-comments
Aug 22, 2026
Merged

Add comments to preference lists: per-applicant and group-wide#179
adescoteaux1 merged 1 commit into
mainfrom
ally/preference-list-comments

Conversation

@adescoteaux1

Copy link
Copy Markdown
Contributor

Summary

  • Leads on a preference-list group can now post comments, marked with their name, in two places: a collapsible thread on each applicant in the shared list, and a group-wide thread at the bottom of the page.
  • Mirrors the existing InterviewComment pattern closely: any group member (or chief/admin) may post any number of comments; only the comment's own author can edit it; no delete (same as InterviewComment — not adding a capability the closest precedent in this codebase doesn't have).
  • One table (preference_list_comments) with a nullable application_id: absent means a comment on the group as a whole, set means a comment on that one applicant. Bundled into the existing GetPreferenceListDetail fetch (alongside members/entries/personal_entries) so opening a list costs one request regardless of how many entries or comments it has.
  • Scoped to the shared list only — personal lists don't get comments (they're private scratchpads, not a collaborative surface). Not deadline-gated, matching how personal lists and other discussion-shaped data in this feature already work — a comment thread is meta-discussion, not the ranked decision data itself.

Test plan

  • Backend: make fmt-check, make vet, make lint, make test, make openapi
  • Frontend: npm run generate:api, npx eslint, npx tsc --noEmit, npx prettier --check, npm run test

Mirrors the existing InterviewComment pattern: any group member may
post any number of comments, marked with their name, and edit only
their own (no delete, matching that precedent). One table with a
nullable application_id — absent is a comment on the group as a
whole, set is a comment on that one applicant — bundled into the
existing detail fetch so opening a list costs one request, not one
per entry. Scoped to the shared list only; personal lists don't get
comments. Never deadline-gated, since discussion isn't the ranked
decision data itself.
@netlify

netlify Bot commented Aug 22, 2026

Copy link
Copy Markdown

Deploy Preview for generate-appportal ready!

Name Link
🔨 Latest commit 7d60f63
🔍 Latest deploy log https://app.netlify.com/projects/generate-appportal/deploys/6a8a27518ba41e0008b4e34c
😎 Deploy Preview https://deploy-preview-179--generate-appportal.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@adescoteaux1
adescoteaux1 merged commit 7afdb68 into main Aug 22, 2026
13 checks passed
@adescoteaux1
adescoteaux1 deleted the ally/preference-list-comments branch August 22, 2026 22:56
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