feat: add comment reply functionality (Fixes #161) #412
Conversation
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
PBnicad
force-pushed
the
feature/comment-reply
branch
from
fc02640 to
05e7d49
Compare
- Add two-level nesting comment reply functionality - Add replyToUserId field to track which user is being replied to - Refresh comments immediately after reply submission - Add numbering to comments and sort replies chronologically - Move comment numbering to the left of timestamp - Add type annotations to sort callback parameters - Remove unused replyPrefix parameter from CommentItem - Add database migration for reply functionality - Update translation files for reply feature Co-Authored-By: Claude <noreply@anthropic.com>
PBnicad
force-pushed
the
feature/comment-reply
branch
from
05e7d49 to
3a84800
Compare
OXeu
requested changes
Jan 23, 2026
Collaborator
OXeu
left a comment
OXeu
left a comment
There was a problem hiding this comment.
There are too many "any" type annotations in the code. Are they all necessary?
PBnicad
force-pushed
the
feature/comment-reply
branch
from
d56aed9 to
ec8cb83
Compare
Contributor
Author
fixed |
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.
📋 Summary
Implements nested comment reply functionality as requested in #161.
✨ Features
@usernameto indicate who is being replied toparent_idcolumn with cascade delete🛠️ Technical Changes
Backend
parent_idcolumn to comments table with foreign key and cascade deleteparentIdparameterreplyToUserinfo in comment responseFrontend
ReplyInputcomponent for nested repliesReplyItemcomponent for rendering second-level commentsCommentItemto support reply functionalityDatabase Migration
server/sql/0006.sql: Addsparent_idcolumn with cascade delete📝 Files Changed
server/src/db/schema.ts: Updated comment schemaserver/src/services/comments.ts: Added reply logic and nested structure buildingserver/sql/0006.sql: Database migrationclient/src/page/feed.tsx: Added reply UI componentsclient/public/locales/*.json: Added i18n translationsserver/src/services/feed.ts,rss.ts: Type updates🔗 Related Issue
Fixes #161
🤖 Generated with Claude Code