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

[GH-ISSUE #2772] Organization plugin lacking metadata type-safety and JSON parsing #9343

New Issue
Closed
opened 2026-04-13 04:46:46 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-13 04:46:46 -05:00
Owner
Copy Link

Originally created by @ohkimur on GitHub (May 24, 2025).
Original GitHub issue: https://github.com/better-auth/better-auth/issues/2772

Is this suited for github?

  • Yes, this is suited for github

To Reproduce

  1. Create a new organization.
  2. Add metadata fields.
  3. Try to access this metadata from useActiveOrganization and/or useListOrganizations -> No type-safety and it's raw string instead of parsed JSON.

Current vs. Expected behavior

The current behavior is almost there, but we should be able to define a type schema for the metadata in an intuitive way. Additionally the metadata object although stored as a string in the db should be parsed by default with the right type.

Additionally we should have the ability to customize the organization schema through additionalFields such that we don't just have metadata, but we have the power of actually extending the organization schema properly. There are plenty of usecases where this would be very valuable.

What version of Better Auth are you using?

1.2.8

Provide environment information

MacOS, Arc Browser

Which area(s) are affected? (Select all that apply)

Types

Auth config (if applicable)

import { betterAuth } from "better-auth"
import { organization } from 'better-auth/plugins'

export const auth = betterAuth({
  emailAndPassword: {  
    enabled: true
  },
  plugins: [organization()]
});

Additional context

No response

Originally created by @ohkimur on GitHub (May 24, 2025). Original GitHub issue: https://github.com/better-auth/better-auth/issues/2772 ### Is this suited for github? - [x] Yes, this is suited for github ### To Reproduce 1. Create a new organization. 2. Add metadata fields. 3. Try to access this metadata from `useActiveOrganization` and/or `useListOrganizations` -> No type-safety and it's raw `string` instead of parsed JSON. ### Current vs. Expected behavior The current behavior is almost there, but we should be able to define a type schema for the metadata in an intuitive way. Additionally the metadata object although stored as a string in the db should be parsed by default with the right type. Additionally we should have the ability to customize the organization schema through `additionalFields` such that we don't just have metadata, but we have the power of actually extending the organization schema properly. There are plenty of usecases where this would be very valuable. ### What version of Better Auth are you using? 1.2.8 ### Provide environment information ```bash MacOS, Arc Browser ``` ### Which area(s) are affected? (Select all that apply) Types ### Auth config (if applicable) ```typescript import { betterAuth } from "better-auth" import { organization } from 'better-auth/plugins' export const auth = betterAuth({ emailAndPassword: { enabled: true }, plugins: [organization()] }); ``` ### Additional context _No response_
GiteaMirror added the locked label 2026-04-13 04:46:46 -05:00
GiteaMirror commented 2026-04-13 04:46:47 -05:00
Author
Owner
Copy Link

@Kinfe123 commented on GitHub (May 28, 2025):

Metadata is designed to store a wide range of complex and dynamic data based on various use cases. This gives you greater flexibility when storing information in the metadata field, and you can handle typing in your application code, which feels quite intuitive.

<!-- gh-comment-id:2914657113 --> @Kinfe123 commented on GitHub (May 28, 2025): Metadata is designed to store a wide range of complex and dynamic data based on various use cases. This gives you greater flexibility when storing information in the metadata field, and you can handle typing in your application code, which feels quite intuitive.
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 locked
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#9343
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?