Discussion reply notifications show the real name of an anonymous replier
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- typescript
- Domain
- frontend
Research direction
Start in discussion-student.component.ts at sendPostToStudentsInThread lines 259-266, where the notification text is built from getUsernamesByWorkgroupId. Find the component's anonymization flag and compare how the discussion view chooses the anonymous name, then make the notification omit the replier's name when anonymized. Done means an anonymized thread notification reads generically while non-anonymized notifications still name the replier.
Written by the indexing model from the issue text.
Description
With "Anonymize responses" enabled, a student who replies in a thread is shown under an anonymous name in the discussion, but the notification sent to the thread's other participants names them.
How to reproduce
- Author a Discussion with "Anonymize responses" enabled.
- Student A posts; student B replies to A's post.
- As student A, open the notifications menu.
The notification reads "<B's real name> replied to a discussion you were in!".
Cause
DiscussionStudentComponent.sendPostToStudentsInThread (discussion-student.component.ts lines 259 to 266) builds the message from getUsernamesByWorkgroupId without checking whether the component is anonymized. The real name is also stored in the notification's message on the server.
Possible fix
When the component is anonymized, leave the name out ("Someone replied to a discussion you were in!") or use the anonymous name. Leaving it out avoids depending on the anonymous name being the same for every viewer, which it currently is not (#2393).
- Dominant language
- TypeScript
- Stars
- 4
- Forks
- 8
- Avg merge
- 3d 8h
- Merged PRs (30d)
- 12
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from WISE-Community/WISE-Client
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
WISE-Community/WISE-Client#2404 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
WISE-Community/WISE-Client#2401 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
WISE-Community/WISE-Client#2376 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
WISE-Community/WISE-Client#2354 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
WISE-Community/WISE-Client#2350 ·
Maintainers usually reply within 1 day
All issues in WISE-Community/WISE-Client
Similar issues
-
clawsweeper:needs-maintainer-review clawsweeper:needs-product-decision clawsweeper:no-new-fix-pr clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster P3
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
openclaw/openclaw#203385 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
nwverse/persona#12800 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
Maintainers usually reply within 1 day
-
[MCP]: page snapshots in .playwright-mcp/ are not git-ignored (.playwright-cli/ is, since #42318)Open
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
microsoft/playwright#44289 ·
Maintainers usually reply within 1 day
-
good first issue
Difficulty 2/5 Half a day Newbie friendliness 65/100
Maintainers usually reply within 1 day