feat: create supabase lib and actions files

[andostronaut]

This is an automated pull request for branch develop

Summary by CodeRabbit

• New Features

  • Introduced server-side functionality for improved performance and security.
  • Implemented real-time database event handling with Supabase for insertions and deletions.
  • Added listeners for database changes, enhancing application responsiveness.

• Dependencies

  • Integrated new dependencies for Supabase's server-side rendering and JavaScript client library, expanding data handling capabilities.

[coderabbitai]

Walkthrough

The changes introduce server-side functionality through new files and directives, enhancing the application's architecture by separating client and server logic. A Supabase client is established for real-time database interaction, with listeners for insert and delete events. Additionally, dependencies for Supabase's server-side rendering and JavaScript client library are added to the project, facilitating improved data handling and integration with backend services.

Changes

Files	Change Summary
app/(dashboard)/actions.ts	Added 'use server' directive to indicate server-side functionality.
app/(root)/actions.ts	Added 'use server' directive to indicate server-side functionality.
lib/supabase/client.ts	Introduced a Supabase client, exported functions for listening to insert and delete events, and added a mechanism for handling real-time database changes.
lib/supabase/server.ts	Established server-side integration with Supabase, added functions for real-time event handling, and exported the Supabase client instance for broader use.
package.json	Added dependencies: "@supabase/ssr": "^0.5.1" and "@supabase/supabase-js": "^2.45.3" to integrate Supabase's capabilities into the project.

Sequence Diagram(s)

sequenceDiagram
    participant Client
    participant Server
    participant Supabase

    Client->>Server: Request for data
    Server->>Supabase: Fetch data
    Supabase-->>Server: Return data
    Server-->>Client: Send data

Loading

sequenceDiagram
    participant Supabase
    participant Server

    Server->>Supabase: Subscribe to insert events
    Supabase-->>Server: Notify on insert
    Server->>Server: Handle new value
    Server->>Supabase: Subscribe to delete events
    Supabase-->>Server: Notify on delete
    Server->>Server: Handle deleted value

Loading

Poem

🐰 In a world of code, where changes bloom,
New files sprout, dispelling the gloom.
With Supabase magic, events take flight,
Data dances, oh what a sight!
A hop, a skip, to the server we go,
In this tech garden, watch our app grow! 🌼

Tip

Announcements

• The review status is no longer posted as a separate comment when there are no actionable or nitpick comments. In such cases, the review status is included in the walkthrough comment.
• We have updated our review workflow to use the Anthropic's Claude family of models. Please share any feedback in the discussion post on our Discord.
• Possibly related PRs: Walkthrough comment now includes a list of potentially related PRs to help you recall past context. Please share any feedback in the discussion post on our Discord.
• Suggested labels: CodeRabbit can now suggest labels by learning from your past PRs in the walkthrough comment. You can also provide custom labeling instructions in the UI or configuration file.
• Possibly related PRs, automatic label suggestions based on past PRs, learnings, and possibly related issues require data opt-in (enabled by default).

---

Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between a77e13d and 543e81b.

Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

Files selected for processing (5)

• app/(dashboard)/actions.ts (1 hunks)
• app/(root)/actions.ts (1 hunks)
• lib/supabase/client.ts (1 hunks)
• lib/supabase/server.ts (1 hunks)
• package.json (1 hunks)

Files skipped from review due to trivial changes (2)

• app/(dashboard)/actions.ts
• app/(root)/actions.ts

Additional comments not posted (12)

lib/supabase/client.ts (5)

1-8: LGTM!

The code segment is approved.

---

10-12: LGTM!

The code segment is approved.

---

18-31: LGTM!

The code segment is approved.

---

33-46: LGTM!

The code segment is approved.

---

48-50: LGTM!

The code segment is approved.

lib/supabase/server.ts (5)

1-9: LGTM!

The code segment is approved.

---

13-28: LGTM!

The code segment is approved.

---

30-43: LGTM!

The code segment is approved.

---

45-58: LGTM!

The code segment is approved.

---

60-62: LGTM!

The code segment is approved.

package.json (2)

32-32: LGTM!

The code segment is approved.

---

33-33: LGTM!

The code segment is approved.

---

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.