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 #3963] docs: add better-auth-speckle plugin to community plugins list #5110

New Issue
Open
opened 2026-03-13 12:11:05 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-03-13 12:11:05 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/better-auth/better-auth/pull/3963
Author: @XingxinHE
Created: 8/13/2025
Status: 🔄 Open

Base: canary ← Head: docs/add-speckle-community-plugin-to-doc

📝 Commits (3)

  • 4bea9f0 docs: add better-auth-speckle plugin to community plugins list
  • c3361c0 Apply suggestions from code review
  • a3e80db Apply suggestions

📊 Changes

1 file changed (+11 additions, -0 deletions)

View changed files

📝 docs/components/community-plugins-table.tsx (+11 -0)

📄 Description

Hi team,

I've built a plugin for Speckle System. Since it doesn't fulfill a standard oauth flow, I can't use the generic oauth plugin to handle it. Therefore, I take the reference of generic-oauth-plugin to create a community plugin to handle its vanilla REST oauth flow into a clean, easy-to-use API.

high level of this plugin:

  • code implements the interface of BetterAuthPlugin, OAuthProvider, and ProviderOptions.
  • test covers 3 auth endpoint, sign in, link account, callback.

In this PR, there is only documentation change.

Summary by cubic

Added the better-auth-speckle plugin to the Community Plugins list in docs/components/community-plugins-table.tsx. Supports Speckle System’s non-standard OAuth flow with sign-in and link account.

Written for commit a3e80dbcac471b1a8d8dcaabf57b6f1a0af90c59. Summary will update on new commits.

🔄 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/3963 **Author:** [@XingxinHE](https://github.com/XingxinHE) **Created:** 8/13/2025 **Status:** 🔄 Open **Base:** `canary` ← **Head:** `docs/add-speckle-community-plugin-to-doc` --- ### 📝 Commits (3) - [`4bea9f0`](https://github.com/better-auth/better-auth/commit/4bea9f00ef5da8114df0fa070ce6ba32d34a259b) docs: add better-auth-speckle plugin to community plugins list - [`c3361c0`](https://github.com/better-auth/better-auth/commit/c3361c04be08765263dbcd89d51a38946f991b81) Apply suggestions from code review - [`a3e80db`](https://github.com/better-auth/better-auth/commit/a3e80dbcac471b1a8d8dcaabf57b6f1a0af90c59) Apply suggestions ### 📊 Changes **1 file changed** (+11 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `docs/components/community-plugins-table.tsx` (+11 -0) </details> ### 📄 Description Hi team, I've built a plugin for [Speckle System](https://github.com/specklesystems/speckle-server). Since it doesn't fulfill a standard oauth flow, I can't use the generic oauth plugin to handle it. Therefore, I take the reference of generic-oauth-plugin to create a community plugin to handle its vanilla REST oauth flow into a clean, easy-to-use API. high level of this plugin: - [code](https://github.com/XingxinHE/better-auth-speckle/blob/main/src/server.ts) implements the interface of `BetterAuthPlugin`, `OAuthProvider`, and `ProviderOptions`. - [test](https://github.com/XingxinHE/better-auth-speckle/blob/main/test/speckle.browser.test.ts) covers 3 auth endpoint, sign in, link account, callback. In this PR, there is only documentation change. <!-- This is an auto-generated description by cubic. --> --- ## Summary by cubic Added the better-auth-speckle plugin to the Community Plugins list in docs/components/community-plugins-table.tsx. Supports Speckle System’s non-standard OAuth flow with sign-in and link account. <sup>Written for commit a3e80dbcac471b1a8d8dcaabf57b6f1a0af90c59. Summary will update on new commits.</sup> <!-- 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-03-13 12:11:05 -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#5110
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?