[WEB-2430] fix: issue exports for project

[NarayanBavisetti]

fix:

• issue exports for projects

Issue Link: WEB-2430

Summary by CodeRabbit

• New Features

  • Enhanced logic for adding assignees and labels in data updates, allowing for more flexibility when existing lists are empty.

• Bug Fixes

  • Improved error handling by ensuring that assignees and labels can be added even if there are no existing entries, preventing potential data omissions.

[coderabbitai]

Walkthrough

The changes made in the pull request focus on updating the logic within the update_json_row and update_table_row functions in the export_task.py file. The modifications primarily enhance the conditions for adding assignees and labels, allowing for the addition of these entities even when existing lists are empty. This adjustment aims to improve data handling by preventing errors related to null or empty values.

Changes

File Path	Change Summary
apiserver/plane/bgtasks/export_task.py	Updated logic in update_json_row and update_table_row to allow adding assignees and labels when existing lists are None.

Poem

In the fields where data grows,
A rabbit hops where logic flows.
With labels bright and friends anew,
The tasks are set, the changes true.
Hooray for updates, let’s all cheer,
For brighter rows, we hold so dear! 🐇✨

---

Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 00b7630 and 5ae7954.

Files selected for processing (1)

• apiserver/plane/bgtasks/export_task.py (2 hunks)

Additional comments not posted (4)

apiserver/plane/bgtasks/export_task.py (4)

247-249: LGTM!

The changes to the condition for adding assignees look good. The additional check for existing_assignees being None allows for a more flexible handling of cases where there are no existing assignees, enhancing the robustness of the function.

---

251-253: LGTM!

The changes to the condition for adding labels look good. The additional check for existing_labels being None allows for a more flexible handling of cases where there are no existing labels, enhancing the robustness of the function.

---

273-275: LGTM!

The changes to the condition for adding assignees look good. The additional check for existing_assignees being None allows for a more flexible handling of cases where there are no existing assignees, enhancing the robustness of the function. This is consistent with the changes made in the update_json_row function.

---

277-279: LGTM!

The changes to the condition for adding labels look good. The additional check for existing_labels being None allows for a more flexible handling of cases where there are no existing labels, enhancing the robustness of the function. This is consistent with the changes made in the update_json_row function.

---

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>.
  • 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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 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.