Skip to content

Conversation

@DipakHalkude
Copy link

@DipakHalkude DipakHalkude commented Oct 15, 2025

Closes #14675


Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

  • It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
  • This message body should clearly illustrate what problems it solves.
  • Ideally, include a test that fails without this PR but passes with it.

Tests

  • Run the tests with pnpm test and lint the project with pnpm lint and pnpm check

Changesets

  • If your PR makes a change that should be noted in one or more packages' changelogs, generate a changeset by running pnpm changeset and following the prompts. Changesets that add features should be minor and those that fix bugs should be patch. Please prefix changeset messages with feat:, fix:, or chore:.

Edits

  • Please ensure that 'Allow edits from maintainers' is checked. PRs without this option may be closed.

@changeset-bot
Copy link

changeset-bot bot commented Oct 15, 2025

⚠️ No Changeset found

Latest commit: 8ada398

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

@svelte-docs-bot
Copy link

@DipakHalkude
Copy link
Author

@dummdidumm Could you please review this docs update?

Fixes #14675 - unifies query update terminology and improves navigation.

@ghostdevv ghostdevv added the documentation Improvements or additions to documentation label Oct 15, 2025
@benmccann
Copy link
Member

@DipakHalkude could you run pnpm format? thanks!

@DipakHalkude
Copy link
Author

@benmccann Please have a look :)

@DipakHalkude
Copy link
Author

I guess we can ignore cases. As it is a part of document. I just changed the README.md file.

@DipakHalkude
Copy link
Author

@benmccann @dummdidumm The branch is up to date with main, but the test failures appear to be related to #14732 and are unrelated to these documentation changes.

The lint check is passing and the documentation improvements are complete. This PR fixes #14675 by unifying query update terminology and improving navigation between sections.

Could you please review and merge when possible? Thanks!

@benmccann
Copy link
Member

I updated with the latest code. The remaining error is caused by the docs changes:

Error: The following pages contain links to /docs/kit/remote-functions#form-Single-flight-mutations, but no element with id="form-Single-flight-mutations" exists on /docs/kit/remote-functions - see the handleMissingId option in https://svelte.dev/docs/kit/configuration#prerender for more info:

  • /docs/kit/remote-functions

DipakHalkude and others added 3 commits October 16, 2025 21:25
- Fix broken anchor link from #form-Single-flight-mutations to #single-flight-mutations
- Improve documentation consistency and navigation
@DipakHalkude
Copy link
Author

DipakHalkude commented Oct 16, 2025

@benmccann The preview deployment shows conflicting status:

  • Text says: "svelte.dev previews deployed successfully"
  • But shows red X icon

All other checks are green and the broken anchor link has been fixed in commit 389ce47 (line 769). The link now correctly points to #single-flight-mutations instead of #form-Single-flight-mutations.

Could you please:

  1. Check if this is just a GitHub status display issue
  2. Re-run the deployment check if needed
  3. Merge if everything is actually working

Thanks!

@DipakHalkude
Copy link
Author

Could you please re-run the deployment check from your side? This often resolves these status display issues.

@benmccann
Copy link
Member

I still see a line referencing #single-flight-mutations:

To enable client-driven [query updates after form submissions](#single-flight-mutations), use `submit().updates(...)`. For example, if the `getPosts()` query was used on this page, we could refresh it like so:

You don't need to comment so often. There was only 12 minutes between your comments, which isn't nearly enough time to check them 😄 Sometimes it will be days before we can take another look

@DipakHalkude
Copy link
Author

DipakHalkude commented Oct 16, 2025

Ok got it. Sorry for this 🙏.

@DipakHalkude
Copy link
Author

Just a gentle follow-up on my PR. With Hacktoberfest ending soon, I'd be so grateful if you could take a quick look. I'm ready to make any immediate changes needed. Thank you so much for your time :)

@DipakHalkude
Copy link
Author

Output:

Screenshot 2025-10-20 111055

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

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

docs: update query refresh/update sections

3 participants