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

[PR #3597] [MERGED] docs(hono): update RPC client to use init config instead of custom fetch #30504

New Issue
Closed
opened 2026-04-17 21:34:19 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-17 21:34:19 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/better-auth/better-auth/pull/3597
Author: @braden-w
Created: 7/24/2025
Status: ✅ Merged
Merged: 8/10/2025
Merged by: @Kinfe123

Base: main ← Head: fix/hono-rpc-client-init-config

📝 Commits (3)

  • 672c1b9 docs(hono): update RPC client to use init config instead of custom fetch
  • 89569c5 Merge branch 'main' into fix/hono-rpc-client-init-config
  • 659f877 Merge branch 'main' into fix/hono-rpc-client-init-config

📊 Changes

1 file changed (+3 additions, -6 deletions)

View changed files

📝 docs/content/docs/integrations/hono.mdx (+3 -6)

📄 Description

Updated the Hono RPC client configuration in the integration documentation to use the init configuration method instead of a custom fetch function.

This change follows the official Hono RPC documentation: https://hono.dev/docs/guides/rpc#cookies

This is an update to my previous contribution #2209. I didn't realize at the time that there was an even simpler built-in way to send cookies with each request!

🔄 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/3597 **Author:** [@braden-w](https://github.com/braden-w) **Created:** 7/24/2025 **Status:** ✅ Merged **Merged:** 8/10/2025 **Merged by:** [@Kinfe123](https://github.com/Kinfe123) **Base:** `main` ← **Head:** `fix/hono-rpc-client-init-config` --- ### 📝 Commits (3) - [`672c1b9`](https://github.com/better-auth/better-auth/commit/672c1b95e3859fd8f86ac2fe9d908c6c9313d4a2) docs(hono): update RPC client to use init config instead of custom fetch - [`89569c5`](https://github.com/better-auth/better-auth/commit/89569c56f08771ac5f28a98242a39e9c20db0343) Merge branch 'main' into fix/hono-rpc-client-init-config - [`659f877`](https://github.com/better-auth/better-auth/commit/659f877c17fdabb8f3fb9bcf4dff84d576d78163) Merge branch 'main' into fix/hono-rpc-client-init-config ### 📊 Changes **1 file changed** (+3 additions, -6 deletions) <details> <summary>View changed files</summary> 📝 `docs/content/docs/integrations/hono.mdx` (+3 -6) </details> ### 📄 Description Updated the Hono RPC client configuration in the integration documentation to use the `init` configuration method instead of a custom `fetch` function. This change follows the official Hono RPC documentation: https://hono.dev/docs/guides/rpc#cookies This is an update to my previous contribution #2209. I didn't realize at the time that there was an even simpler built-in way to send cookies with each request! --- <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-17 21:34:19 -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#30504
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?