Add thread schema

[Behzad-rabiei]

Summary by CodeRabbit

• Refactor

  • Updated certain thread properties to be optional, improving flexibility when handling thread data.

• Tests

  • Adjusted unit tests to align with updated thread property requirements.

[coderabbitai]

Walkthrough

The changes update the BaseThread interface to make several properties optional and adjust test cases to use non-null assertion operators when accessing thread_metadata. No new features or logic were introduced; the updates focus on TypeScript type safety and interface flexibility.

Changes

File(s)	Change Summary
src/interfaces/Thread.interface.ts	Made parent_id, owner_id, name, and thread_metadata optional in the BaseThread interface.
tests/unit/models/thread.model.test.ts	Added non-null assertion operators when accessing thread_metadata properties in test cases.

Poem

In fields of code where threads may roam,
Some fields now may stay at home—
Optional tags, a lighter load,
With exclamation marks bestowed.
TypeScript sighs with less constraint,
The rabbit hops—no need to faint!
🐇✨

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

npm error Exit handler never called!
npm error This is an error with npm itself. Please report this error at:
npm error https://github.com/npm/cli/issues
npm error A complete log of this run can be found in: /.npm/_logs/2025-06-11T08_28_18_454Z-debug-0.log

✨ Finishing Touches

• 📝 Generate Docstrings

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (2)

__tests__/unit/models/thread.model.test.ts (2)

43-45: Prefer explicit undefined checks over non-null assertion in tests

Using thread.thread_metadata!.auto_archive_duration = 999 compiles, but it sidesteps the very runtime uncertainty that made the field optional.
A clearer pattern is:

if (thread.thread_metadata) {
  thread.thread_metadata.auto_archive_duration = 999;
}

The test will still fail as intended if thread_metadata is unexpectedly undefined, giving you a signal instead of silently passing compilation.

---

74-76: Same comment as above applies to invitable mutation

Consider guarding with an explicit check rather than using !.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 50ead4d and a62a3d9.

📒 Files selected for processing (2)

• __tests__/unit/models/thread.model.test.ts (2 hunks)
• src/interfaces/Thread.interface.ts (1 hunks)

🔇 Additional comments (1)

src/interfaces/Thread.interface.ts (1)

38-41: Check downstream expectations before loosening these fields

parent_id, owner_id, name, and thread_metadata are now optional. All validation, persistence, and serialization layers that previously assumed these keys were always present must tolerate undefined or supply sensible fall-backs.
In particular, the Mongoose schema (and any DB indexes) may still declare them as required, which would make the typings lie to the rest of the codebase.

Please audit:

1. The Thread model schema (src/models/thread.model.ts?) – ensure .required() flags are removed or kept in sync.
2. All code that does thread.parent_id!, thread.thread_metadata!.… etc. outside of tests.
3. Business rules that rely on name always existing (e.g. duplicate-name checks).

If any of these assumptions remain, keep the properties required or add explicit runtime guards.

Also applies to: 45-45