fix: store directions in infinite query result structure

[TkDodo]

so that we can re-use the first one when a refetch happens and properly pass "backward" to it if necessary

fixes #7203

[vercel[bot]]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Ignored Deployment

Name	Status	Preview	Comments	Updated (UTC)
query	⬜️ Ignored (Inspect)	Visit Preview		May 10, 2024 0:46am

[nx-cloud[bot]]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit 864fd247011dcd85827bdbdd474580e465efe676. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this CI Pipeline Execution

---

✅ Successfully ran 1 target

• nx affected --targets=test:format,test:sherif,test:knip,test:eslint,test:lib,test:types,test:build,build,test:attw --parallel=3

---

Sent with 💌 from NxCloud.

[codesandbox-ci[bot]]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit 864fd247011dcd85827bdbdd474580e465efe676:

Sandbox	Source
@tanstack/query-example-angular-basic	Configuration
@tanstack/query-example-react-basic-typescript	Configuration
@tanstack/query-example-solid-basic-typescript	Configuration
@tanstack/query-example-svelte-basic	Configuration
@tanstack/query-example-vue-basic	Configuration

[TkDodo]

not going ahead with this because the better fix is to not rely on direction being passed to the QueryFunctionContext, but to pass it yourself via pageParams.

I'll deprecate direction.