github-starred/better-auth
2
0
Fork 0
mirror of https://github.com/better-auth/better-auth.git synced 2026-05-22 14:21:55 -05:00
Code Issues 2.5k Packages Projects Releases 112 Wiki Activity

[PR #430] [CLOSED] Add object type support for database field #3284

New Issue
Closed
opened 2026-03-13 10:47:00 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-03-13 10:47:00 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/better-auth/better-auth/pull/430
Author: @mmikhan
Created: 11/5/2024
Status: ❌ Closed

Base: next ← Head: main

📝 Commits (2)

  • 413ea60 Add object type support for database field
  • 2e370cf lint fixes

📊 Changes

3 files changed (+30 additions, -9 deletions)

View changed files

📝 packages/better-auth/src/db/field.ts (+8 -5)
📝 packages/better-auth/src/db/get-migration.ts (+18 -3)
📝 packages/better-auth/src/db/to-zod.ts (+4 -1)

📄 Description

Overview

This PR adds support for storing object type fields in the database across different database engines. It is useful for extending core schema to add a JSON object or even gives the opportunity to add a relationship between the user and other table while still using the user inferring types.

Example Usage

import { betterAuth } from "better-auth";
 
export const auth = betterAuth({
   user: {
      additionalFields: { 
          role: {
             type: "object",
             required: false,
             defaultValue: "{}",
             input: false // don't allow user to set role
          },
      }
   }
})

🔄 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/430 **Author:** [@mmikhan](https://github.com/mmikhan) **Created:** 11/5/2024 **Status:** ❌ Closed **Base:** `next` ← **Head:** `main` --- ### 📝 Commits (2) - [`413ea60`](https://github.com/better-auth/better-auth/commit/413ea60348cb2eb6fc2c32b7be401bc1b6291ad7) Add object type support for database field - [`2e370cf`](https://github.com/better-auth/better-auth/commit/2e370cfc56d9bf5e79a6872ed42230e573f51f40) lint fixes ### 📊 Changes **3 files changed** (+30 additions, -9 deletions) <details> <summary>View changed files</summary> 📝 `packages/better-auth/src/db/field.ts` (+8 -5) 📝 `packages/better-auth/src/db/get-migration.ts` (+18 -3) 📝 `packages/better-auth/src/db/to-zod.ts` (+4 -1) </details> ### 📄 Description ## Overview This PR adds support for storing object type fields in the database across different database engines. It is useful for [extending core schema](https://www.better-auth.com/docs/concepts/database#extending-core-schema) to add a JSON object or even gives the opportunity to add a relationship between the user and other table while still using the user [inferring types](https://www.better-auth.com/docs/concepts/typescript#infering-types). ## Example Usage ```typescript import { betterAuth } from "better-auth"; export const auth = betterAuth({ user: { additionalFields: { role: { type: "object", required: false, defaultValue: "{}", input: false // don't allow user to set role }, } } }) ``` --- <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-03-13 10:47:00 -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#3284
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?