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

[PR #3386] [CLOSED] fix: add metadata to invitation #13042

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

📋 Pull Request Information

Original PR: https://github.com/better-auth/better-auth/pull/3386
Author: @Abenezer
Created: 7/15/2025
Status: ❌ Closed

Base: main ← Head: fix/addMetadataToInvitation

📝 Commits (2)

  • a32913d fix: metadata to invitation
  • 971cbec fix : fomrating on add metadata to invitation

📊 Changes

7 files changed (+87 additions, -19 deletions)

View changed files

📝 docs/content/docs/plugins/organization.mdx (+6 -0)
📝 packages/better-auth/src/adapters/kysely-adapter/test/state.txt (+1 -1)
📝 packages/better-auth/src/plugins/organization/adapter.ts (+42 -18)
📝 packages/better-auth/src/plugins/organization/organization.test.ts (+18 -0)
📝 packages/better-auth/src/plugins/organization/organization.ts (+5 -0)
📝 packages/better-auth/src/plugins/organization/routes/crud-invites.ts (+11 -0)
📝 packages/better-auth/src/plugins/organization/schema.ts (+4 -0)

📄 Description

To provide flexibility when inviting users i am adding a metaData field in invitation
Currently, customizing the invitation message or redirect links isn't possible. My pull request introduces a metaData field to the invitation object, allowing for custom fields (like invitationMessage and redirectLinks) to be included.
this PR also update the Docs and add a test

Summary by cubic

Added a metadata field to invitations so custom data like messages or redirect links can be included when inviting users.

  • New Features
    • Invitations now support an optional metadata field for custom information.
    • Updated docs and added a test to cover metadata usage.

🔄 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/3386 **Author:** [@Abenezer](https://github.com/Abenezer) **Created:** 7/15/2025 **Status:** ❌ Closed **Base:** `main` ← **Head:** `fix/addMetadataToInvitation` --- ### 📝 Commits (2) - [`a32913d`](https://github.com/better-auth/better-auth/commit/a32913d98aea50337f4e33d537892bcbab6bfd1c) fix: metadata to invitation - [`971cbec`](https://github.com/better-auth/better-auth/commit/971cbec402328aa5e7fa47a01b705588feeb2e36) fix : fomrating on add metadata to invitation ### 📊 Changes **7 files changed** (+87 additions, -19 deletions) <details> <summary>View changed files</summary> 📝 `docs/content/docs/plugins/organization.mdx` (+6 -0) 📝 `packages/better-auth/src/adapters/kysely-adapter/test/state.txt` (+1 -1) 📝 `packages/better-auth/src/plugins/organization/adapter.ts` (+42 -18) 📝 `packages/better-auth/src/plugins/organization/organization.test.ts` (+18 -0) 📝 `packages/better-auth/src/plugins/organization/organization.ts` (+5 -0) 📝 `packages/better-auth/src/plugins/organization/routes/crud-invites.ts` (+11 -0) 📝 `packages/better-auth/src/plugins/organization/schema.ts` (+4 -0) </details> ### 📄 Description To provide flexibility when inviting users i am adding a metaData field in invitation Currently, customizing the invitation message or redirect links isn't possible. My pull request introduces a metaData field to the invitation object, allowing for custom fields (like invitationMessage and redirectLinks) to be included. this PR also update the Docs and add a test <!-- This is an auto-generated description by cubic. --> --- ## Summary by cubic Added a metadata field to invitations so custom data like messages or redirect links can be included when inviting users. - **New Features** - Invitations now support an optional metadata field for custom information. - Updated docs and added a test to cover metadata usage. <!-- End of auto-generated description by cubic. --> --- <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:42:55 -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#13042
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?