Skip to content

Conversation

@Oungseik
Copy link

@Oungseik Oungseik commented Sep 13, 2025

Merge the main branch into the target branch. Fix locally reference state which cause some test to fail by wrap the reference of state inside a function in createMutation.svelte.ts

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Sep 13, 2025

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

✨ Finishing touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

  • Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
  • Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@nx-cloud
Copy link

nx-cloud bot commented Sep 17, 2025

View your CI Pipeline Execution ↗ for commit 2f27208

Command Status Duration Result
nx affected --targets=test:sherif,test:knip,tes... ⏳ In Progress ... View ↗
nx run-many --target=build --exclude=examples/*... ✅ Succeeded 2s View ↗

☁️ Nx Cloud last updated this comment at 2025-09-26 11:35:28 UTC

@pkg-pr-new
Copy link

pkg-pr-new bot commented Sep 22, 2025

More templates

@tanstack/angular-query-experimental

npm i https://pkg.pr.new/@tanstack/angular-query-experimental@9650

@tanstack/eslint-plugin-query

npm i https://pkg.pr.new/@tanstack/eslint-plugin-query@9650

@tanstack/query-async-storage-persister

npm i https://pkg.pr.new/@tanstack/query-async-storage-persister@9650

@tanstack/query-broadcast-client-experimental

npm i https://pkg.pr.new/@tanstack/query-broadcast-client-experimental@9650

@tanstack/query-core

npm i https://pkg.pr.new/@tanstack/query-core@9650

@tanstack/query-devtools

npm i https://pkg.pr.new/@tanstack/query-devtools@9650

@tanstack/query-persist-client-core

npm i https://pkg.pr.new/@tanstack/query-persist-client-core@9650

@tanstack/query-sync-storage-persister

npm i https://pkg.pr.new/@tanstack/query-sync-storage-persister@9650

@tanstack/react-query

npm i https://pkg.pr.new/@tanstack/react-query@9650

@tanstack/react-query-devtools

npm i https://pkg.pr.new/@tanstack/react-query-devtools@9650

@tanstack/react-query-next-experimental

npm i https://pkg.pr.new/@tanstack/react-query-next-experimental@9650

@tanstack/react-query-persist-client

npm i https://pkg.pr.new/@tanstack/react-query-persist-client@9650

@tanstack/solid-query

npm i https://pkg.pr.new/@tanstack/solid-query@9650

@tanstack/solid-query-devtools

npm i https://pkg.pr.new/@tanstack/solid-query-devtools@9650

@tanstack/solid-query-persist-client

npm i https://pkg.pr.new/@tanstack/solid-query-persist-client@9650

@tanstack/svelte-query

npm i https://pkg.pr.new/@tanstack/svelte-query@9650

@tanstack/svelte-query-devtools

npm i https://pkg.pr.new/@tanstack/svelte-query-devtools@9650

@tanstack/svelte-query-persist-client

npm i https://pkg.pr.new/@tanstack/svelte-query-persist-client@9650

@tanstack/vue-query

npm i https://pkg.pr.new/@tanstack/vue-query@9650

@tanstack/vue-query-devtools

npm i https://pkg.pr.new/@tanstack/vue-query-devtools@9650

commit: 2f27208

@changeset-bot
Copy link

changeset-bot bot commented Sep 26, 2025

⚠️ No Changeset found

Latest commit: 2f27208

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@lachlancollins lachlancollins merged commit 2f27208 into TanStack:svelte-5-adapter Sep 26, 2025
5 of 6 checks passed
@lachlancollins
Copy link
Member

@Oungseik oops I've made a mistake here and accidentally "merged" this PR. I've synced changes from main to svelte-5-adapter, and it seems like I messed up with the merge conflict resolution with your PR. Would you be able to open a new PR with just the mutation test fixes? Thanks!!

@Oungseik
Copy link
Author

Yes, I can.

@Oungseik
Copy link
Author

I pulled the latest changes, ran the tests and all passed. No fixes need right?

@lachlancollins
Copy link
Member

I pulled the latest changes, ran the tests and all passed. No fixes need right?

Great, I assumed that there was something you were fixing independently of the merge, but if not then I guess we don't need any more changes!

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