Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings
This repository was archived by the owner on Aug 5, 2025. It is now read-only.

Commit164d484

Browse files
committed
add missing $
1 parent56da210 commit164d484

File tree

1 file changed

+1
-1
lines changed
  • content/tutorial/01-svelte/06-bindings/01-text-inputs

1 file changed

+1
-1
lines changed

‎content/tutorial/01-svelte/06-bindings/01-text-inputs/README.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ As a general rule, data flow in Svelte is _top down_ — a parent component can
66

77
Sometimes it's useful to break that rule. Take the case of the`<input>` element in this component — we_could_ add an`on:input` event handler that sets the value of`name` to`event.target.value`, but it's a bit... boilerplatey. It gets even worse with other form elements, as we'll see.
88

9-
Instead, we can use the[`bind:value` directive](docs#template-syntax-element-directives-bind-property):
9+
Instead, we can use the[`bind:value` directive]($docs#template-syntax-element-directives-bind-property):
1010

1111
```svelte
1212
<input bind:value={name}>

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp