Skip to content

chore: fix reuse wording in client comment#15679

Merged
Rich-Harris merged 2 commits intosveltejs:mainfrom
Rohan5commit:pr-20260409-kit-reuse-comment
Apr 9, 2026
Merged

chore: fix reuse wording in client comment#15679
Rich-Harris merged 2 commits intosveltejs:mainfrom
Rohan5commit:pr-20260409-kit-reuse-comment

Conversation

@Rohan5commit
Copy link
Copy Markdown
Contributor

@Rohan5commit Rohan5commit commented Apr 9, 2026

Fix a wording typo in a runtime client comment: re-use -> reuse.

This is a single-file, comment-only change with no user-facing behavior change.


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 clearly illustrates 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.

Notes

  • Local tests were not run for this comment-only change.
  • No changeset needed for this non-user-facing wording correction.

Signed-off-by: Codex <codex@openai.com>
Copilot AI review requested due to automatic review settings April 9, 2026 02:19
@changeset-bot
Copy link
Copy Markdown

changeset-bot bot commented Apr 9, 2026

⚠️ No Changeset found

Latest commit: ac0a503

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
Copy Markdown

Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

Updates a runtime client comment to use consistent wording (“re-use” → “reuse”).

Changes:

  • Adjust comment wording in the client runtime load path

Comment on lines 1189 to 1192
const server_data_node = server_data_nodes?.[i];

// re-use data from previous load if it's still valid
// reuse data from previous load if it's still valid
const valid =
Copy link

Copilot AI Apr 9, 2026

Choose a reason for hiding this comment

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

This comment line is indented one level deeper than the surrounding statements (it has an extra tab). Align it with const server_data_node / const valid to keep consistent formatting and avoid noisy diffs.

Copilot uses AI. Check for mistakes.
@teemingc teemingc changed the title docs: fix reuse wording in client comment chore: fix reuse wording in client comment Apr 9, 2026
@Rich-Harris
Copy link
Copy Markdown
Member

my man how do you manage to mess up a PR that changes a single character

Co-authored-by: vercel[bot] <35613825+vercel[bot]@users.noreply.github.com>
@Rich-Harris Rich-Harris merged commit 24d7e76 into sveltejs:main Apr 9, 2026
26 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants