feat: update toJson plugin

[Behzad-rabiei]

Summary by CodeRabbit

• New Features

  • Updated package version to 3.0.79.

• Bug Fixes

  • Adjusted the toJSON method to retain createdAt and updatedAt fields in the serialized output.

[coderabbitai]

Walkthrough

This pull request contains two primary changes: a version bump in the package.json file and a modification to the toJSON plugin in the schema transformation logic. The version has been incremented from "3.0.78" to "3.0.79", and the toJSON function in the plugin has been adjusted by commenting out the deletion of createdAt and updatedAt fields, which will now be preserved in the serialized output.

Changes

File	Change Summary
package.json	Version updated from "3.0.78" to "3.0.79"
src/models/schemas/plugins/toJSON.plugin.ts	Commented out deletion of createdAt and updatedAt fields in toJSON transform function

Poem

🐰 A version hop, a tiny leap,
Fields once hidden, now they keep
Their timely tale in JSON's embrace
A rabbit's code with gentle grace
Version 3.0.79 takes flight! 🚀

Tip

CodeRabbit's docstrings feature is now available as part of our Early Access Program! Simply use the command @coderabbitai generate docstrings to have CodeRabbit automatically generate docstrings for your pull request. We would love to hear your feedback on Discord.

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between aeedd61 and da67cdd.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (2)

• package.json (1 hunks)
• src/models/schemas/plugins/toJSON.plugin.ts (1 hunks)

✅ Files skipped from review due to trivial changes (1)

• package.json

🔇 Additional comments (1)

src/models/schemas/plugins/toJSON.plugin.ts (1)

42-43: Carefully review the decision to retain createdAt and updatedAt fields in JSON output.

Previously, these fields were removed, likely for privacy or data minimization. Restoring them might be intentional for auditing or debugging, but consider the potential impact on client-facing APIs if these timestamps are not meant to be publicly exposed.

Would you like me to run a repository-wide check to see which endpoints or consumers rely on these fields?

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ 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.
  • Generate unit testing code for this file.
  • 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 generate unit testing code for this file.
  • @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 generate unit testing code.
  • @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.

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. (Beta)
• @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.