fix: preserve emptied remote number defaults

[vamshikrishnaramasamy]

Fixes #15937.

Remote form fields previously rendered their default whenever the backing value was null or undefined. Empty number inputs are converted to undefined, so deleting a defaulted number field caused the rendered value to snap back to the default.

This distinguishes a missing field from a field that exists with an undefined value. Missing fields still render defaults, while emptied number fields render as empty strings.

Tests:

• pnpm --dir packages/kit exec vitest --config kit.vitest.config.js run src/runtime/form-utils.spec.js
• pnpm --dir packages/kit exec prettier --config ../../.prettierrc --check src/runtime/form-utils.js src/runtime/form-utils.spec.js
• pnpm --dir packages/kit exec tsc --noEmit --pretty false

[pkg-svelte-dev]

Install the latest version of @sveltejs/kit from 5e1f2d4:

pnpm add https://pkg.svelte.dev/@sveltejs/kit/c/5e1f2d46e77f47fb2316a57e11d3b8de00e41dc3

Open in pkg.svelte.dev: https://pkg.svelte.dev/repos/kit/pr/16237

Note

This PR is from a fork. A maintainer must approve approve each commit before it can be built and installed.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 5e1f2d4

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