feat(backend): project relationship

[Sma1lboy]

Summary by CodeRabbit

• New Features

  • Enhanced project forms with stricter validations, ensuring required fields are provided.
  • Improved data management that automatically cleans up related chats when projects or accounts are removed.

• Refactor

  • Streamlined the main interface: the chat and code editing panels have been removed, so the home view now focuses solely on settings.
  • Removed the unsaved changes notification to simplify the code editor experience.

• Chores

  • Updated dependency management for improved consistency.

[coderabbitai]

Warning

There were issues while running some tools. Please review the errors and either fix the tool’s configuration or disable the tool if it’s a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

backend/src/project/project.model.ts

Oops! Something went wrong! :(

ESLint: 8.57.1

ESLint couldn't find the plugin "eslint-plugin-prettier".

(The package "eslint-plugin-prettier" was not found when loaded as a Node module from the directory "/backend".)

It's likely that the plugin isn't installed correctly. Try reinstalling by running the following:

npm install eslint-plugin-prettier@latest --save-dev

The plugin "eslint-plugin-prettier" was referenced from the config file in "backend/.eslintrc.js".

If you still can't figure out the problem, please stop by https://eslint.org/chat/help to chat with the team.

backend/src/build-system/context.ts

Oops! Something went wrong! :(

ESLint: 8.57.1

ESLint couldn't find the plugin "eslint-plugin-prettier".

(The package "eslint-plugin-prettier" was not found when loaded as a Node module from the directory "/backend".)

It's likely that the plugin isn't installed correctly. Try reinstalling by running the following:

npm install eslint-plugin-prettier@latest --save-dev

The plugin "eslint-plugin-prettier" was referenced from the config file in "backend/.eslintrc.js".

If you still can't figure out the problem, please stop by https://eslint.org/chat/help to chat with the team.

backend/src/chat/chat.model.ts

Oops! Something went wrong! :(

ESLint: 8.57.1

ESLint couldn't find the plugin "eslint-plugin-prettier".

(The package "eslint-plugin-prettier" was not found when loaded as a Node module from the directory "/backend".)

It's likely that the plugin isn't installed correctly. Try reinstalling by running the following:

npm install eslint-plugin-prettier@latest --save-dev

The plugin "eslint-plugin-prettier" was referenced from the config file in "backend/.eslintrc.js".

If you still can't figure out the problem, please stop by https://eslint.org/chat/help to chat with the team.

• 4 others

Walkthrough

This pull request introduces several formatting adjustments and enhancements across the backend and frontend codebases. On the backend, minor indentation fixes are applied, and the data models for chats, projects, and users are updated to use UUIDs and to enforce stricter relational constraints with cascading deletes. In addition, input validation and resolver methods are refined with renamed methods and new fields for retrieving related user and chat data. Meanwhile, the frontend sees dependency updates and removal of certain UI layout elements, notably in the main layout and code-saving notification component.

Changes

File(s)	Change Summary
backend/src/build-system/context.ts	Adjusted formatting and indentation for the constructor in the BuilderContext class.
backend/src/chat/chat.model.ts	Added new projectId property and a many-to-one relationship with the Project entity. Modified the existing User relationship to include onDelete: 'CASCADE' and nullable: false.
backend/src/project/dto/project.input.ts	Added validation decorators to enforce constraints on projectName and path; updated projectId and projectPackages to be optional with appropriate validation.
backend/src/project/project.model.ts	Changed primary key generation to UUID; updated userId to type string; modified the User relationship to enforce CASCADE deletion; added a one-to-many relationship with the Chat entity.
backend/src/project/project.resolver.ts	Renamed methods (getUserProjects to getProjects and getProjectDetails to getProject), updated parameter types, and added new resolver methods (getUser and getChats) to resolve related entities.
backend/src/project/project.service.ts	Updated parameter types in methods (getProjectsByUser, getProjectById, deleteProject), refined query relations to include chats and project packages, and improved filtering logic for deleted entries.
backend/src/user/user.model.ts	Switched the primary key to UUID and added a new one-to-many relationship with the Project model through a new projects field.
frontend/package.json	Added a dependency entry for "codefox-common": "workspace:*".
frontend/src/app/(main)/Home.tsx	Removed the rendering logic for the main layout including the chat interface and project code engine; now only renders the settings view.
frontend/src/app/api/project/route.ts	Removed the conditional check for an empty file structure response, altering the fallback behavior for projects with no files.
frontend/src/components/code-engine/code-engine.tsx	Removed the SaveChangesBar component and its associated logic, which previously handled unsaved changes notifications.

Sequence Diagram(s)

sequenceDiagram
    participant Client
    participant Resolver as ProjectsResolver
    participant Service as ProjectService
    participant DB as Database

    Client->>Resolver: Query getProjects(userId)
    Resolver->>Service: getProjectsByUser(userId)
    Service->>DB: Fetch projects with relations (user, chats)
    DB-->>Service: Return project data
    Service-->>Resolver: Project list
    Resolver->>Resolver: Resolve 'user' via getUser(@Parent())
    Resolver->>Resolver: Resolve 'chats' via getChats(@Parent())
    Resolver-->>Client: Return complete project details

Loading

Suggested labels

enhancement

Suggested reviewers

• ZHallen122

Poem

In a burrow deep within our code,
I hop with joy, a rabbit in mode.
Changes sprout like carrots in the ground,
Enhanced models and features all around.
With UUIDs and cascades, our data's secure,
Hop along—our progress is pure!
🐇🌟 Happy coding in our rabbit trail!

Tip

🌐 Web search-backed reviews and chat

• We have enabled web search-based reviews and chat for all users. This feature allows CodeRabbit to access the latest documentation and information on the web.
• You can disable this feature by setting web_search: false in the knowledge_base settings.
• Please share any feedback in the Discord discussion.

---

📜 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 00f2df6 and 4714dd5.

📒 Files selected for processing (11)

• backend/src/build-system/context.ts (1 hunks)
• backend/src/chat/chat.model.ts (2 hunks)
• backend/src/project/dto/project.input.ts (1 hunks)
• backend/src/project/project.model.ts (3 hunks)
• backend/src/project/project.resolver.ts (2 hunks)
• backend/src/project/project.service.ts (2 hunks)
• backend/src/user/user.model.ts (3 hunks)
• frontend/package.json (1 hunks)
• frontend/src/app/(main)/Home.tsx (0 hunks)
• frontend/src/app/api/project/route.ts (0 hunks)
• frontend/src/components/code-engine/code-engine.tsx (0 hunks)

💤 Files with no reviewable changes (3)

• frontend/src/app/api/project/route.ts
• frontend/src/components/code-engine/code-engine.tsx
• frontend/src/app/(main)/Home.tsx

✅ Files skipped from review due to trivial changes (1)

• backend/src/build-system/context.ts

🧰 Additional context used

🪛 Biome (1.9.4)

frontend/package.json

[error] 18-18: The key codefox-common was already declared.

This where a duplicated key was declared again.

If a key is defined multiple times, only the last definition takes effect. Previous definitions are ignored.

(lint/suspicious/noDuplicateObjectKeys)

🪛 GitHub Actions: Run tests and upload coverage

backend/src/project/project.model.ts

[error] 62-62: Cannot find name 'OneToMany'.

---

[error] 62-62: Cannot find name 'OneToMany'.

backend/src/project/project.service.ts

[error] 119-119: Type 'number' is not assignable to type 'string'.

---

[error] 235-235: This comparison appears to be unintentional because the types 'string' and 'number' have no overlap.

🔇 Additional comments (9)

backend/src/project/dto/project.input.ts (2)

11-13: LGTM! Well-structured input validation.

The validation decorators are properly implemented, ensuring:

• Required fields are non-empty strings
• UUID validation for projectId
• Array validation for projectPackages

Also applies to: 16-18, 21-23, 26-28

---

5-7: Add migration path for deprecated class.

The deprecation notice should include information about the alternative approach or replacement class to use.

Consider adding a comment like:

/**
- * @deprecated We don't need project upsert
+ * @deprecated Use CreateProjectInput instead. This class will be removed in the next major version.
 */

backend/src/user/user.model.ts (1)

19-20: LGTM! Well-structured relationship configuration.

The changes appropriately:

• Use UUID for ID field
• Configure projects relationship with consistent options
• Enable cascade delete for proper cleanup

Also applies to: 42-48

backend/src/project/project.model.ts (1)

20-21: LGTM! Well-structured entity relationships.

The changes appropriately:

• Use UUID for ID fields
• Configure bidirectional relationships
• Set up proper cascade behaviors

Also applies to: 31-41, 61-66

backend/src/project/project.resolver.ts (1)

56-66: LGTM! Well-implemented field resolvers.

The new resolvers for user and chats fields are properly implemented with:

• Correct return types
• Proper parent field resolution
• Appropriate filtering of deleted chats

backend/src/chat/chat.model.ts (2)

51-62: LGTM! Well-structured project relationship.

The project relationship is properly defined with:

• GraphQL and TypeORM decorators
• Cascade delete for maintaining referential integrity
• Non-nullable constraint for ensuring data consistency
• Correct foreign key column naming

---

63-69: LGTM! Enhanced user relationship constraints.

The user relationship is properly updated with cascade delete and non-nullable constraints, ensuring data integrity.

backend/src/project/project.service.ts (2)

37-60: LGTM! Enhanced project retrieval with chat filtering.

The changes properly handle chat relationships and filtering of deleted entities.

---

182-213: LGTM! Proper handling of project deletion.

The changes correctly:

• Include chat relations
• Document the automatic handling of related chats through CASCADE
• Maintain soft delete functionality

✨ Finishing Touches

• 📝 Generate Docstrings (Beta)

---

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