github-starred/better-auth
2
0
Fork 0
mirror of https://github.com/better-auth/better-auth.git synced 2026-05-27 09:32:20 -05:00
Code Issues 2.5k Packages Projects Releases 112 Wiki Activity

[PR #1872] [MERGED] fix(docs): Fix prisma column mappings in NextAuth migration guide #12287

New Issue
Closed
opened 2026-04-13 08:17:40 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-13 08:17:40 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/better-auth/better-auth/pull/1872
Author: @joshuanianji
Created: 3/18/2025
Status: ✅ Merged
Merged: 4/11/2025
Merged by: @Bekacru

Base: main ← Head: next-auth-migration-clarification

📝 Commits (1)

📊 Changes

1 file changed (+4 additions, -4 deletions)

View changed files

📝 docs/content/docs/guides/next-auth-migration-guide.mdx (+4 -4)

📄 Description

The "Example with Prisma" section under the NextAuth migration guide has the "expires" and "expiresAt" column switched. This isn't a huge issue but just a little confusing when implementing the changes.

Assuming we want to map expires -> expiresAt, I changed that section and also updated the comments to make it clear that BetterAuth uses expiresAt, while the old column name is expires.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/better-auth/better-auth/pull/1872 **Author:** [@joshuanianji](https://github.com/joshuanianji) **Created:** 3/18/2025 **Status:** ✅ Merged **Merged:** 4/11/2025 **Merged by:** [@Bekacru](https://github.com/Bekacru) **Base:** `main` ← **Head:** `next-auth-migration-clarification` --- ### 📝 Commits (1) - [`1bdeffd`](https://github.com/better-auth/better-auth/commit/1bdeffd9d50dbf30020be9fbab635b72d6b40616) update db mapping docs ### 📊 Changes **1 file changed** (+4 additions, -4 deletions) <details> <summary>View changed files</summary> 📝 `docs/content/docs/guides/next-auth-migration-guide.mdx` (+4 -4) </details> ### 📄 Description The "Example with Prisma" section under the NextAuth migration guide has the "expires" and "expiresAt" column switched. This isn't a huge issue but just a little confusing when implementing the changes. Assuming we want to map `expires -> expiresAt`, I changed that section and also updated the comments to make it clear that BetterAuth uses `expiresAt`, while the old column name is `expires`. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-04-13 08:17:40 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
adapter
astro
awaiting external contributor
blocked
breaking
breaking change
bug
c-devops
core
credentials
database
dependencies
devops
devtools
docs
documentation
duplicate
elysia
enhancement
enterprise
expo
express
fastify
good first issue
help wanted
hono
identity
infra
integration
invalid
javascript
locked
maintenance
need-more-information
needs: info
needs: repro
nextjs
nuxt
oauth
organization
P0
payments
perf
platform
plugin
pull-request
Mirrored from GitHub Pull Request
 question
ready
regression
remix
security
social-provider
solid
stale
svelte
tanstack-start
tracking
version-bump
vue
wontfix
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/better-auth#12287
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?