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

Add query parameter support to useSession().refetch() for cache control consistency #1671

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

Originally created by @adriandlam on GitHub (Aug 8, 2025).

Is this suited for github?

  • Yes, this is suited for github

Is your feature request related to a problem? Please describe.

Currently, getSession() supports query parameters like { disableCookieCache: true }, but useSession().refetch() doesn't. This creates an inconsistent API where I have to import and use both methods just to bypass cookie cache after updating user data. When using optimistic updates with cookie caching enabled, the session remains stale even after calling refetch(), requiring a workaround with getSession({ query: { disableCookieCache: true }}).

Describe the solution you'd like

I'd like useSession().refetch() to accept the same query parameters as getSession():

const { refetch } = useSession();
await refetch({ query: { disableCookieCache: true }});

This would provide API consistency and eliminate the need to import both useSession() and getSession() for cache invalidation.

Describe alternatives you've considered

Current workaround:

import { useSession, getSession } from '@/lib/auth-client';

const { data: session, refetch } = useSession();
// After mutation...
const newSession = await getSession({ query: { disableCookieCache: true }});

Other alternatives considered:

  • Disabling cookie cache entirely (loses performance benefits)
  • Using shorter cache duration (still has timing issues)
  • Manual state management (defeats the purpose of the session hook)
Originally created by @adriandlam on GitHub (Aug 8, 2025). ### Is this suited for github? - [x] Yes, this is suited for github ### Is your feature request related to a problem? Please describe. Currently, `getSession()` supports query parameters like `{ disableCookieCache: true }`, but `useSession().refetch()` doesn't. This creates an inconsistent API where I have to import and use both methods just to bypass cookie cache after updating user data. When using optimistic updates with cookie caching enabled, the session remains stale even after calling `refetch()`, requiring a workaround with `getSession({ query: { disableCookieCache: true }})`. ### Describe the solution you'd like I'd like `useSession().refetch()` to accept the same query parameters as `getSession()`: ```ts const { refetch } = useSession(); await refetch({ query: { disableCookieCache: true }}); ``` This would provide API consistency and eliminate the need to import both `useSession()` and `getSession()` for cache invalidation. ### Describe alternatives you've considered Current workaround: ```ts import { useSession, getSession } from '@/lib/auth-client'; const { data: session, refetch } = useSession(); // After mutation... const newSession = await getSession({ query: { disableCookieCache: true }}); ``` Other alternatives considered: - Disabling cookie cache entirely (loses performance benefits) - Using shorter cache duration (still has timing issues) - Manual state management (defeats the purpose of the session hook)
GiteaMirror added the enhancement label 2026-03-13 08:55:00 -05:00
GiteaMirror commented 2026-03-13 08:55:01 -05:00
Author
Owner
Copy Link

@adriandlam commented on GitHub (Aug 8, 2025):

Working on this now, will submit a PR soon

@adriandlam commented on GitHub (Aug 8, 2025): Working on this now, will submit a PR soon
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 enhancement
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#1671
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?