Fix the role not being present on user session

[NiallJoeMaher]

✨ Codu Pull Request 💻

Pull Request details

• The Drizzle adapter doesn't infer the user schema
• Manually add the user schema to the adapter
• Fix date format in ban function

Any Breaking changes

• None 👍

[vercel]

@NiallJoeMaher is attempting to deploy a commit to the Codú Team on Vercel.

A member of the Team first needs to authorize it.

[coderabbitai]

Walkthrough

The recent changes include modifications to the date format in the adminRouter, converting the createdAt property from a Date object to an ISO 8601 string. Additionally, the authOptions in server/auth.ts has been enhanced with a usersTable property to specify the user schema, and a new role property has been added to the session.user object for improved session management.

Changes

Files	Change Summary
server/api/router/admin.ts	Changed createdAt property from a Date object to an ISO 8601 string format.
server/auth.ts	Updated authOptions to include usersTable in DrizzleAdapter and added role to session.user.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant AdminRouter
    participant Auth

    User->>AdminRouter: Create new object
    AdminRouter->>AdminRouter: Set createdAt to ISO 8601 string
    AdminRouter-->>User: Return success response

    User->>Auth: Log in
    Auth->>Auth: Retrieve user data
    Auth-->>User: Return session with user role

Loading

🐇 In fields of code, I hop with glee,
New formats and roles, oh what a spree!
From dates to strings, we dance and play,
Enhancing our paths in a joyful way!
With every change, the world feels bright,
A rabbit's delight in the coding night! 🌙✨

---

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

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

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.

[vercel]

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

Name	Status	Preview	Comments	Updated (UTC)
codu	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Aug 28, 2024 7:46am

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 56d8f27 and 75c8177.

Files selected for processing (2)

• server/api/router/admin.ts (1 hunks)
• server/auth.ts (3 hunks)

Additional comments not posted (3)

server/api/router/admin.ts (1)

31-31: Approved change to date format.

Converting the createdAt date to an ISO 8601 string is a good practice for standardizing date formats across different systems. Ensure that all systems consuming this date are capable of handling the ISO format.

server/auth.ts (2)

39-39: Approved addition of usersTable configuration.

Explicitly specifying the usersTable in the DrizzleAdapter configuration enhances clarity and ensures that the correct table is used for user management.

---

61-61: Approved addition of role to session user object.

Adding the role property to the session.user object is a significant enhancement for role-based access control within the application. Ensure that role checks are implemented consistently throughout the application.