add owner to Space, fix "create" policy for SpaceUser

[ymc9]

Summary by CodeRabbit

• New Features

  • Introduced ownership functionality for spaces, allowing users to own spaces and manage memberships.
  • Enhanced filtering capabilities in space checks by adding ownerId.

• Bug Fixes

  • Updated delete cascade behavior to ensure spaces are deleted when a user is removed.

• Documentation

  • Clarified relationships and permissions in data models.

• Chores

  • Updated dependency versions for Prisma packages.
  • Modified image handling configuration for better pattern matching.

• Style

  • Removed unused Tailwind CSS plugin to streamline configuration.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Skipped Deployment

Name	Status	Preview	Comments	Updated (UTC)
todo-demo	⬜️ Ignored (Inspect)			Dec 22, 2024 1:27pm

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

This pull request introduces significant changes to the project's data model and authentication flow, focusing on enhancing space ownership and user membership relationships. The modifications span multiple files, including the Prisma schema, model metadata, authentication configuration, and database migrations. The primary goal is to establish a clear ownership structure for spaces, allowing each space to have a designated owner and improving user-space interactions.

Changes

File	Change Summary
lib/hooks/__model_meta.ts	- Added owner and ownerId fields to space model - Renamed spaces to ownedSpaces in user model - Added memberships field to user model - Updated delete cascade configuration
lib/hooks/space.ts	- Updated useCheckSpace function to include ownerId in filtering options
next.config.js	- Replaced domains with remotePatterns for image handling
package.json	- Updated Prisma package versions to ^6.1.0
pages/api/auth/[...nextauth].ts	- Added owner connection when creating a new space during sign-in
prisma/schema.prisma	- Added owner and ownerId to Space model - Renamed spaces to ownedSpaces - Added memberships to User model
schema.zmodel	- Enhanced space and user model relationships - Updated permission rules for space and space user models
tailwind.config.js	- Removed @tailwindcss/line-clamp plugin

Sequence Diagram

sequenceDiagram
    participant User
    participant AuthSystem
    participant SpaceModel
    
    User->>AuthSystem: Sign In
    AuthSystem->>SpaceModel: Create Space
    SpaceModel-->>AuthSystem: Set User as Owner
    AuthSystem-->>User: Authenticate and Assign Space

Loading

Poem

🐰 A Rabbit's Ode to Space Ownership 🏠

In realms of code, a change takes flight,
Spaces now have an owner's might!
With metadata crisp and relations clear,
User and space, now drawing near.
A digital home, with boundaries bright! 🌟

Tip

CodeRabbit's docstrings feature is now available as part of our Early Access Program! Simply use the command @coderabbitai generate docstrings to have CodeRabbit automatically generate docstrings for your pull request. We would love to hear your feedback on Discord.

---

📜 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 8cd77cf and 83aca6e.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (10)

• lib/hooks/__model_meta.ts (4 hunks)
• lib/hooks/space.ts (1 hunks)
• next.config.js (1 hunks)
• package.json (2 hunks)
• pages/api/auth/[...nextauth].ts (1 hunks)
• prisma/migrations/20241222114017_add_space_owner/migration.sql (1 hunks)
• prisma/migrations/migration_lock.toml (1 hunks)
• prisma/schema.prisma (2 hunks)
• schema.zmodel (4 hunks)
• tailwind.config.js (1 hunks)

---

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.