fix db seed

[Marfuen]

Summary by CodeRabbit

• Bug Fixes

  • Improved error handling during policy file processing to ensure that issues with individual files don’t interrupt overall operations.

• New Features

  • Enhanced the policy data structure to support more detailed and flexible content representation.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
app	🔄 Building (Inspect)	Visit Preview	💬 Add feedback	Feb 17, 2025 10:16pm

1 Skipped Deployment

Name	Status	Preview	Comments	Updated (UTC)
web	⬜️ Skipped (Inspect)			Feb 17, 2025 10:16pm

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

This pull request enhances the seeding process by adding error handling during the processing of policy files and refines the data structure of the Policy interface. In the seeding script, a try-catch block is introduced to manage errors in file reading and JSON parsing, ensuring that one faulty file does not halt the entire process. In parallel, the Policy interface is updated by adding a new top-level type property, removing the type property from the metadata, and restructuring the content field from a simple JSON array to an array of objects with defined schema.

Changes

File(s)	Change Summary
packages/db/prisma/seed.ts	Added a try-catch block to handle errors during file reading/parsing. Moved the declaration of policyData inside the try block to limit its scope.
packages/db/prisma/seedTypes.ts	Updated the Policy interface by adding a new top-level type property. Removed the type property from the metadata object and restructured content from a JsonArray to an array of objects with a defined structure.

Sequence Diagram(s)

sequenceDiagram
    participant SeedFunction as Seed Function
    participant FileSystem as File System
    participant Logger as Logger
    participant Database as Database

    SeedFunction->>FileSystem: Read & parse policy file
    alt Parsing is successful
        SeedFunction->>Database: Upsert policy data
    else Error occurs
        SeedFunction->>Logger: Log error with file details
    end

Loading

Poem

I'm a bunny hopping through the code,
Dancing with lines where errors erode.
With try-catch leaps, I keep the pace,
Nibbling bugs with a graceful grace.
Data gardens bloom as I happily roam,
CodeRabbit cheers—this seed finds its home!
🐇💻

---

📜 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 5bf12d0 and 433f18d.

📒 Files selected for processing (2)

• packages/db/prisma/seed.ts (1 hunks)
• packages/db/prisma/seedTypes.ts (1 hunks)

✨ Finishing Touches

• 📝 Generate Docstrings (Beta)

---

🪧 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.