Skip to content

feat: Add settings in tanstack start - #768

Open
aXenDeveloper wants to merge 2 commits into
feat/tanstack_start_8from
feat/tanstack_start_9
Open

feat: Add settings in tanstack start#768
aXenDeveloper wants to merge 2 commits into
feat/tanstack_start_8from
feat/tanstack_start_9

Conversation

@aXenDeveloper

Copy link
Copy Markdown
Owner

Improving Documentation

Description

What?

Why?

@vercel

vercel Bot commented Aug 28, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
vitnode-docs Ready Ready Preview Aug 28, 2026 4:19pm

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 3f37ce58bc

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

* Exported as the invalidation target too - there is exactly one entry, so the
* key and the family are the same value.
*/
export const DEVICES_QUERY_KEY = ["devices", "me"] as const;

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Invalidate device data when the session changes

When two users sign in sequentially in the same browser tab, this user-independent key retains the first user's device list after sign-out because useSignOutAction only invalidates the session query. On the second user's visit, the route loader uses ensureQueryData, which accepts the existing entry, while the configured refetchOnMount: false prevents the component from correcting it; the page therefore exposes the previous user's device names, IP addresses, and timestamps. Remove this identity-scoped entry on sign-out/authentication changes or include the authenticated user identity in its key.

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

💡 Feature A new feature

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant