docs: Fixes swapped logic for readonly function bindings #15162
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Read-only bindings should have the SET value assigned to null, not the GET.
e.g. this:
<input type="checkbox" bind:indeterminate={null, () => true} />
...fails, while this:
<input type="checkbox" bind:indeterminate={() => true, null} />
...works as expected.
(note: ts doesn't love this, prefers:
<input type="checkbox" bind:indeterminate={() => true, () => null} />
)Question: should I also add explicit wording for bind:indeterminate since it no longer works without explicitly defining a getter/setter:
<input type="checkbox" bind:indeterminate={true} />
Fails.
<input type="checkbox" bind:indeterminate={() => true, null} />
is the only way this binding currently works in Svelte5.
Alternatively, should support for indeterminate={true} be a feat: ticket?
Before submitting the PR, please make sure you do the following
feat:
,fix:
,chore:
, ordocs:
.packages/svelte/src
, add a changeset (npx changeset
).Tests and linting
pnpm test
and lint the project withpnpm lint