Skip to content

feat: Add discover to tanstack start - #763

Open
aXenDeveloper wants to merge 3 commits into
feat/tanstack_start_3from
feat/tanstack_start_4
Open

feat: Add discover to tanstack start#763
aXenDeveloper wants to merge 3 commits into
feat/tanstack_start_3from
feat/tanstack_start_4

Conversation

@aXenDeveloper

Copy link
Copy Markdown
Owner

Improving Documentation

Description

What?

Why?

@vercel

vercel Bot commented Aug 27, 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 27, 2026 6:14pm

@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: 8c70ecbf55

ℹ️ 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".

Comment thread apps/web/src/routes/discover.tsx Outdated
Comment on lines +165 to +168
<SearchFeedContent
LinkComponent={DiscoverFeedLink}
locale={locale}
params={DISCOVER_FEED_PARAMS}

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Route pagination through the validated Discover fetcher

When a visitor loads another page, SearchFeedContent supplies its own query function for the shared cache key, so the request no longer passes through assertDiscoverFeedResponse. A 400 or 429 is therefore parsed and cached as a SearchFeedPage; the subsequent pageInfo access can break the feed instead of leaving the previous pages intact and reporting a query error. Keep pagination on discoverFeedQueryOptions' validated fetcher or add equivalent status validation to the shared component.

Useful? React with 👍 / 👎.

}),
})

function DiscoverRoute() {

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 Define DiscoverRoute as an arrow component

Convert this newly added component to an arrow function; the repository explicitly requires arrow functions for components.

AGENTS.md reference: AGENTS.md:L11-L11

Useful? React with 👍 / 👎.


return (
<RouteMessages namespaces={DISCOVER_NAMESPACES}>
<main className="container mx-auto flex max-w-3xl flex-col gap-6 p-4">

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 Separate padding from the gap layout

This new container combines gap-6 with p-4 and mx-auto on the same element, contrary to the repository rule prohibiting margin or padding from being mixed with gap. Move the outer spacing to a wrapper while retaining the flex gap on this container.

AGENTS.md reference: AGENTS.md:L51-L51

Useful? React with 👍 / 👎.

@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: 716ba64663

ℹ️ 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".

Comment thread apps/web/vitnode-env.ts
// Temporary, for the length of the migration: the origin serving the routes
// this app does not own yet. `components/migration-link.tsx` reads it in the
// browser, so it has to be inlined like the others. See `src/lib/legacy-app.ts`.
'NEXT_PUBLIC_LEGACY_WEB_URL',

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Keep the legacy origin identical across hydration

When a production artifact is built once and NEXT_PUBLIC_LEGACY_WEB_URL is supplied or changed only at container runtime, this client definition retains the build-time value while legacyWebOrigin() reads the live value during SSR. The same MigrationLink can therefore render an absolute legacy URL on the server but a relative or stale URL after hydration, producing a hydration mismatch and causing subsequent client renders to send unmigrated result links to the TanStack origin and 404. Either inject this value into the browser at runtime or require the server to use the same build-time value.

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