fix: workspace draft build

[rahulramesha]

This PR is a patch to fix the build caused by workspace drafts changes

Summary by CodeRabbit

• New Features

  • Enhanced issue management with new quick action options and improved drag-and-drop functionality.
  • Added flexibility in issue creation and updates to support multiple issue types.
  • Introduced new methods for managing issues within cycles and modules.

• Bug Fixes

  • Improved type safety and clarity in issue creation and update processes.

• Documentation

  • Updated component display names for better clarity.

• Chores

  • Reorganized import statements for improved readability.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The pull request introduces various modifications across multiple components and services related to issue management. Key changes include the addition of new props in the WorkspaceDraftIssueLayoutRoot component, updates to issue handling methods in the CreateUpdateIssueModalBase, enhancements to the ColorDropdown component, and the introduction of new types and methods in various hooks and services. These changes collectively aim to improve the functionality and maintainability of the issue management system.

Changes

File Path	Change Summary
.../workspace-draft-root.tsx	Added QuickActions and canEditPropertiesBasedOnProject props to BaseListRoot.
.../issue-modal/base.tsx	Updated issue creation and updating methods with refined logic and type definitions.
.../header/color-dropdown.tsx	Added display name for ColorDropdown and adjusted import statements for readability.
.../use-group-dragndrop.ts	Added EIssuesStoreType.WORKSPACE_DRAFT to DNDStoreType.
.../use-issues-actions.tsx	Updated fetching and issue management methods to use new pagination type and generalized methods.
.../workspace_draft.service.ts	Updated createIssue and updateIssue methods to accept `Partial<TWorkspaceDraftIssue
.../issue/root.store.ts	Reformatted import statements in IssueRootStore for better readability.
.../workspace-draft/issue.store.ts	Modified IWorkspaceDraftIssues interface and WorkspaceDraftIssues class with new methods and types.

Possibly related PRs

• [WEB-2388] dev: workspace draft issues #5772: The changes in the main PR involve the introduction of new components and services for managing workspace draft issues, which directly relates to the modifications in the WorkspaceDraftIssueLayoutRoot component in the main PR that enhances the functionality of draft issues.
• [WEB-2001] fix: Issue local cache fixes #5703: This PR addresses fixes related to local cache functionality, which may be relevant to the management of draft issues as they often involve caching and state management.
• [WEB-2316] fix: Style Calculation performance issue in virtualization #5647: The performance improvements in style calculations may indirectly affect the rendering of draft issues, especially in components that display lists of issues, including drafts.
• Fix: cycles build issue #5750: The changes to the ActiveCycleRoot component may relate to how draft issues are displayed or managed within cycles, which could be relevant to the overall draft issue management system.
• [WEB 2418] Fix minor UI inconsistencies #5568: Minor UI improvements in the issue modal could enhance the user experience when interacting with draft issues, making this PR relevant to the main PR's focus on draft issues.
• [WEB-2390] fix: Clickable Area for Issue List Layout Item #5536: The clickable area for issue list layout items may improve the interaction with draft issues displayed in lists, making this PR relevant to the main PR's context.
• [WEB-1185] chore: minor UI improvement in issue modal. #5390: Minor UI improvements in the issue modal could also enhance the user experience when managing draft issues, linking it to the main PR's focus.
• chore: create/ update issue modal restructure. #5385: The restructuring of the issue modal may improve how draft issues are created or updated, making this PR relevant to the main PR's objectives.
• [WEB-2001]feat: Cache issues on the client #5327: The caching mechanism for issues could directly impact the performance and user experience when dealing with draft issues, linking it to the main PR's focus on draft management.
• [WEB-2025] chore: profile page enhancements #5209: Enhancements to the profile page may indirectly relate to how users interact with draft issues, especially if user profiles are tied to issue management.
• [WEB-2007] fix: cycles loading optimization #5207: Fixes related to cycles loading optimization may impact how draft issues are displayed within cycles, making this PR relevant to the main PR's context.
• [WEB-1972] fix: persist cycle and module Issue properties on page reload in Inbox #5190: Improvements in the inbox feature may enhance how draft issues are previewed or managed, linking it to the main PR's focus on draft issues.

Suggested labels

🧹chore, 🐛bug

Suggested reviewers

• SatishGandham

🐰 In the code we hop and play,
New props and methods lead the way.
With each change, our bugs take flight,
Drafts and issues shine so bright!
A joyful leap, a coding cheer,
For every fix, we hold so dear! 🐇✨

---

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