fix: missing editor package

[Palanikannan1437]

Summary by CodeRabbit

• Chores
  • Updated dependencies in the editor module, including the addition of a new uuid dependency.
  • Reorganized the devDependencies for improved clarity.

[coderabbitai]

Walkthrough

The pull request introduces updates to the package.json file within the packages/editor module. A new dependency, uuid, has been added with a specified version, while two existing development dependencies, @plane/eslint-config and @plane/typescript-config, have been repositioned within the file. The versions for other type definitions remain unchanged, and the overall structure of the dependencies has been clarified.

Changes

File	Change Summary
packages/editor/package.json	- Added new dependency: "uuid": "^10.0.0" - Moved @plane/eslint-config in devDependencies - Moved @plane/typescript-config in devDependencies

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Editor
    participant PackageManager

    User->>Editor: Request to add new dependency
    Editor->>PackageManager: Update package.json with "uuid"
    PackageManager-->>Editor: Confirm dependency added
    Editor->>PackageManager: Reorganize devDependencies
    PackageManager-->>Editor: Confirm dependencies moved
    Editor-->>User: Notify changes completed

Loading

Poem

🐰 In the editor's cozy den,
A new friend, uuid, joins in!
With configs shuffled, neat and bright,
Our code now dances, pure delight!
Hopping through dependencies,
We celebrate with joyful ease! 🎉

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between d253933 and dc6a432.

⛔ Files ignored due to path filters (1)

• yarn.lock is excluded by !**/yarn.lock, !**/*.lock

📒 Files selected for processing (1)

• packages/editor/package.json (1 hunks)

🔇 Additional comments (2)

packages/editor/package.json (2)

76-77: Verify consistency of moved dev dependencies.

The dev dependencies @plane/eslint-config and @plane/typescript-config have been moved within the devDependencies section. While this reorganization doesn't affect functionality, we should ensure these dependencies are used and their versions are consistent with other packages in the project.

Let's verify the consistency and usage of these packages:

#!/bin/bash
# Description: Check for consistency and usage of @plane/eslint-config and @plane/typescript-config

# Test: Check if these configs are referenced in relevant config files
echo "Checking for usage of @plane/eslint-config"
rg --type yaml --type json '@plane/eslint-config' packages/editor

echo "Checking for usage of @plane/typescript-config"
rg --type yaml --type json '@plane/typescript-config' packages/editor

# Test: Check for consistency of versions across the monorepo
echo "Checking version consistency of @plane/eslint-config"
rg --type json '"@plane/eslint-config":\s*"\*"' packages/*/package.json

echo "Checking version consistency of @plane/typescript-config"
rg --type json '"@plane/typescript-config":\s*"\*"' packages/*/package.json

If inconsistencies are found or these configs are not used, consider addressing these issues.

---

69-69: Verify the usage of the newly added "uuid" package.

The addition of the "uuid" package (version ^10.0.0) is noted. While this is a commonly used package for generating unique identifiers, we should ensure it's actually being used in the codebase.

Let's verify the usage of this package:

If no usage is found, consider removing this dependency to keep the package lean.

---

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.