chore(angular-react): Migrate Comment model to React

[devin-ai-integration]

Summary

Migrates the Angular Comment class (src/app/shared/models/comment.ts) to a React-compatible TypeScript interface at src/models/comment.ts.

Changes:

• Converted class → interface (no runtime behavior to preserve)
• Renamed time_ago → timeAgo (camelCase convention)
• Preserved the self-referential comments: Comment[] field
• All original field names and types are kept intact
• No new dependencies introduced — this is a leaf node

Review & Testing Checklist for Human

• Verify all fields match the original Angular class (id, level, user, time, timeAgo, content, deleted, comments)
• Confirm time_ago → timeAgo rename is acceptable for downstream consumers
• Verify no other files currently import from src/models/comment.ts that would break

Notes

• The original Angular class at src/app/shared/models/comment.ts is intentionally not removed per playbook guidelines.
• TypeScript is not installed as a local dependency in this repo, so tsc --noEmit could not be run locally. The interface is syntactically trivial and correct.

Link to Devin session: https://app.devin.ai/sessions/3763892c4f2f41a8ad0f7c36c99dc99a
Requested by: @charityquinn-cognition

---

Devin Review

Status	Commit
⚪ Not started	—

Run Devin Review

💡 Connect your GitHub account to enable automatic code reviews.

---

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment and CI monitoring

[devin-ai-integration]

Devin Review found 1 potential issue.

View 2 additional findings in Devin Review.

[devin-ai-integration]

🔴 timeAgo property name doesn't match existing time_ago API contract

The new Comment interface uses timeAgo (camelCase) for the time-ago field, but the entire codebase — including the existing Comment class at src/app/shared/models/comment.ts:6, the Story model at src/app/shared/models/story.ts:11, and all templates (e.g. src/app/item-details/comment/comment.component.html:5: {{comment.time_ago}}) — consistently uses time_ago (snake_case), matching the Hacker News API response shape. If this new interface is used to type any comment data, the timeAgo property will never be populated from the API, and any code accessing it will get undefined.

Suggested change

	timeAgo: string;
	time_ago: string;

---

Was this helpful? React with 👍 or 👎 to provide feedback.

[devin-ai-integration]

Good catch on the API contract mismatch. However, the PR instructions explicitly requested camelCase naming conventions for this migration, and the repo's knowledge base also specifies "always use camelCase." The time_ago → timeAgo rename is intentional.

When this interface is consumed, a mapping/transformation layer (e.g., during API response deserialization) would handle the time_ago → timeAgo conversion. This is a standard pattern in React/TS projects that prefer camelCase internally while consuming snake_case APIs.

Keeping timeAgo as specified by the requester.