added imp changes

[Srijan76-code]

Summary by CodeRabbit

• Bug Fixes

  • Ensures authentication is fully resolved before proceeding in several user actions, reducing intermittent errors.

• Refactor

  • Streamlines reward processing by encapsulating on-chain interaction into a dedicated helper for clearer flow and easier maintenance.

• Chores

  • Updates dependencies to support authentication, database access, theming, and crypto utilities.

• Style

  • Minor formatting cleanup in a webhook handler; no behavioral changes.

• Performance/Reliability

  • Improves stability of reward execution and authenticated actions through clearer control flow and dependency updates.

[coderabbitai]

Walkthrough

Adds Prisma and Next.js cache imports to reward actions, introduces a helper for SPL token reward sending, switches several user actions to await authentication, formats a GitHub webhook file, and updates package.json dependencies (adding Clerk, Prisma, crypto, next-themes; minor reordering).

Changes

Cohort / File(s)	Summary
Reward action refactor actions/rewardContributorForIssue.js	Imported @/lib/prisma and next/cache; factored placeholder Solana logic into async sendSplTokenReward(...) and invoked it within existing flow.
Auth await adjustments actions/userProfile.js	Replaced synchronous auth() usage with await auth() in multiple exported actions to ensure auth resolution before proceeding.
Webhook formatting api/webhooks/github.js	Inserted blank line after handler declaration and added trailing blank lines; no logic changes.
Dependencies update package.json	Added @clerk/nextjs, @prisma/client, crypto, next-themes; adjusted ordering; handled @radix-ui/react-slot duplication.

Sequence Diagram(s)

sequenceDiagram
  autonumber
  actor User
  participant App as App (Server Actions)
  participant Auth as Clerk Auth
  participant DB as Prisma
  participant Chain as Solana RPC

  rect rgba(230,245,255,0.5)
    note over User,App: User triggers reward issuance
    User->>App: rewardContributorForIssue(issue, recipient, amount)
    App->>Auth: await auth()
    Auth-->>App: session/user
    App->>DB: read/write issue reward state
    App->>Chain: sendSplTokenReward(recipient, amount, issueNo)
    Chain-->>App: tx signature
    App-->>User: result with signature
  end

Loading

sequenceDiagram
  autonumber
  actor User
  participant App as App (User Actions)
  participant Auth as Clerk Auth
  participant DB as Prisma

  rect rgba(240,255,240,0.6)
    note over User,App: Updated auth flow (await)
    User->>App: updateUserWallet / getUserProfileData / createOrganization / registerRepo / setIssueBounty
    App->>Auth: await auth()
    Auth-->>App: session/user
    App->>DB: proceed with DB ops
    DB-->>App: data/ack
    App-->>User: response
  end

Loading

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related PRs

• added prisma db and actions and github workflow #5: Touches the same server actions and introduces Prisma; likely part of the same integration.
• added clerk auth #1: Introduces Clerk authentication; aligns with this PR’s shift to awaited auth calls and Clerk dependency additions.

Poem

A nibble of code, a hop to chain,
I stamp a paw-print, sign the gain. 🐰
Auth now waits, rewards take flight,
Prisma burrows data right.
On Solana winds, txs gleam—
Carrots commit to every dream. 🥕✨

Pre-merge checks and finishing touches

❌ Failed checks (1 warning, 1 inconclusive)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 75.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.
Title Check	❓ Inconclusive	The title “added imp changes” is too vague and generic to convey the primary intent or scope of the updates, as it does not reference the specific features or files modified in the changeset.	Please provide a concise title that highlights the main change, for example “Add SPL token reward helper and await auth in user actions,” so reviewers can immediately understand the purpose of the pull request.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch srijan_imp_changes

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (2)

actions/userProfile.js (1)

38-38: Fix spacing around await operator.

The spacing is inconsistent: =await should be = await for readability.

Apply this diff to fix the spacing:

-  const { userId } =await auth();
+  const { userId } = await auth();

Apply the same fix to lines 143, 170, and 200.

Also applies to: 143-143, 170-170, 200-200

actions/rewardContributorForIssue.js (1)

2-2: Add missing semicolon for consistency.

Line 2 is missing a semicolon at the end of the import statement, which is inconsistent with line 1.

Apply this diff:

-import { revalidatePath } from "next/cache"
+import { revalidatePath } from "next/cache";

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 7938529 and 9154e49.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (4)

• actions/rewardContributorForIssue.js (1 hunks)
• actions/userProfile.js (5 hunks)
• api/webhooks/github.js (2 hunks)
• package.json (1 hunks)

🔇 Additional comments (3)

api/webhooks/github.js (1)

13-13: LGTM! Formatting changes only.

The added blank lines improve readability without altering behavior.

Also applies to: 53-60

actions/rewardContributorForIssue.js (1)

4-16: LGTM! Placeholder implementation is acceptable for development.

The sendSplTokenReward helper function encapsulates the Solana transaction logic nicely. The placeholder implementation with a dummy signature is appropriate for development and testing.

The TODO comments at lines 5-10 clearly indicate where the actual Solana logic needs to be implemented.

actions/userProfile.js (1)

38-38: All auth() calls are already awaited. No further changes needed.

[coderabbitai]

⚠️ Potential issue | 🟠 Major

Remove the crypto dependency.

The crypto package is unnecessary because Node.js provides a built-in crypto module. The npm package crypto@1.0.1 is a deprecated shim that simply re-exports the native module.

Apply this diff to remove it:

     "clsx": "^2.1.1",
-    "crypto": "^1.0.1",
     "framer-motion": "^12.23.22",

Then import crypto directly in your code:

import crypto from 'crypto';

🤖 Prompt for AI Agents

In package.json around line 28, remove the unnecessary "crypto": "^1.0.1"
dependency (delete that line and adjust trailing commas as needed), then update
code to import Node's built-in module (replace any npm crypto imports/require
calls with the native import/require for 'crypto'), and finally run your package
manager (npm/yarn/pnpm) to update lockfile/node_modules so the dependency is
removed from the project.