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

Unable to update metadata for the organization #301

New Issue
Closed
opened 2026-03-13 07:41:15 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-03-13 07:41:15 -05:00
Owner
Copy Link

Originally created by @Kazizodev on GitHub (Nov 29, 2024).

Describe the bug
In the organization plugin, the organization update should be able to update the metadata. However it only prompts to update the name and the slug.

To Reproduce
Steps to reproduce the behavior:

  1. Add Organization plugin from the better-auth docs
  2. Try updating the metadata from the auth client organization

Expected behavior
The update function in organization should include metadata update as well.
await organization.update({ organizationId: values.organizationId, { name: values.name, metadata: { address: values.address } } })

Desktop:

  • OS: Windows 11
  • Browser: Brave

Additional context
.

Originally created by @Kazizodev on GitHub (Nov 29, 2024). **Describe the bug** In the organization plugin, the organization update should be able to update the metadata. However it only prompts to update the name and the slug. **To Reproduce** Steps to reproduce the behavior: 1. Add Organization plugin from the better-auth docs 2. Try updating the metadata from the auth client organization **Expected behavior** The update function in organization should include metadata update as well. `await organization.update({ organizationId: values.organizationId, { name: values.name, metadata: { address: values.address } } })` **Desktop:** - OS: Windows 11 - Browser: Brave **Additional context** .
GiteaMirror commented 2026-03-13 07:41:16 -05:00
Author
Owner
Copy Link

@Kazizodev commented on GitHub (Nov 30, 2024):

I'm reopening this because when I update with metadata, it is stored in the database as [object object]. in string format not JSON.

It should be the same as create

const { data, error } = await organization.create({
    name: values.name,
    slug,
    metadata: { address: values.address },
})

This is saving in the database as an object { address } correctly

However in update

const { data, error } = await organization.update({
    name: values.name,
    slug,
    metadata: { address: values.address },
})

It is saving the metadata as [Object Object]

Want me to create a new issue in GitHub?

@Kazizodev commented on GitHub (Nov 30, 2024): I'm reopening this because when I update with metadata, it is stored in the database as [object object]. in string format not JSON. It should be the same as create ``` const { data, error } = await organization.create({ name: values.name, slug, metadata: { address: values.address }, }) ``` This is saving in the database as an object { address } correctly However in update ``` const { data, error } = await organization.update({ name: values.name, slug, metadata: { address: values.address }, }) ``` It is saving the metadata as [Object Object] Want me to create a new issue in GitHub?
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
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#301
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?