fix: ensure policy content is always an array in PolicyPageEditor

[carhartlewis]

• Updated PolicyDetails page to handle cases where policy content may be null, ensuring that an empty array is passed to PolicyPageEditor instead of undefined.

Summary by CodeRabbit

• Bug Fixes
  • Improved handling of missing policy details on the dashboard, ensuring a more stable and reliable display of content.

[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	Apr 4, 2025 0:22am

1 Skipped Deployment

Name	Status	Preview	Comments	Updated (UTC)
comp-portal	⬜️ Skipped (Inspect)			Apr 4, 2025 0:22am

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

This change updates the assignment of policyContent in the PolicyPageEditor component. A conditional check now verifies if policy?.content exists. If it does, the content is cast to a JSONContent[]; otherwise, an empty array is assigned. This adjustment ensures that policyContent is always an array, helping to prevent runtime errors when the policy or its content is missing.

Changes

File	Change Summary
apps/.../policies/[policyId]/page.tsx	Modified assignment of policyContent to conditionally check for policy?.content and fallback to an empty array if not present.

Sequence Diagram(s)

sequenceDiagram
    participant Editor as PolicyPageEditor
    participant Policy as policy
    Editor->>Policy: Check if policy?.content exists
    alt Content exists
        Editor->>Editor: Assign policy.content as JSONContent[]
    else No content found
        Editor->>Editor: Assign empty array []
    end

Loading

Possibly related PRs

• Enhance API responses in organization, policies, and risks tools #227: Addresses similar handling in the getPolicyContent function, ensuring robustness when dealing with null or undefined policy objects.
• feat: add policy layout components and enhance policy details page #273: Involves modifications to the PolicyDetails page which similarly enforce safer data handling with the PolicyPageEditor component.

Poem

I'm a hopping rabbit in the codey glade,
Tweaking policyContent so errors will fade.
Whether it's a full array or simply empty space,
My tweaks keep runtime issues off the chase.
Happy hops in code, a safe and smooth trace! 🐰✨

---

📜 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 3ab6803 and ebe6b29.

📒 Files selected for processing (1)

• apps/app/src/app/[locale]/(app)/(dashboard)/[orgId]/policies/[policyId]/page.tsx (1 hunks)

✨ 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.
  • 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.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @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.