Skip to content

Commit f925dfd

Browse files
authored
Add code markup to Input component reference
1 parent eacd74b commit f925dfd

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

src/markdown/tutorial/part-2/12-provider-components.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -220,7 +220,7 @@ Next, we'll wire up our query state in the component template.
220220
</label>
221221
```
222222

223-
Interesting! There are a few things happening in this one-line template change. First, we're moving from using a plain HTML `<input>` tag to using an `<Input>` tag instead! As it turns out, Ember provides us with a helpful little *[<Input> component][TODO: link to input component]* for this exact use case. The `<Input>` component is actually just a wrapper around the `<input>` element.
223+
Interesting! There are a few things happening in this one-line template change. First, we're moving from using a plain HTML `<input>` tag to using an `<Input>` tag instead! As it turns out, Ember provides us with a helpful little *[`<Input>` component][TODO: link to input component]* for this exact use case. The `<Input>` component is actually just a wrapper around the `<input>` element.
224224

225225
Ember's `<Input>` component is pretty neat; it will wire up things behind the scenes such that, whenever the user types something into the input box, `this.query` changes accordingly. In other words, `this.query` is kept in sync with the value of what is being searched; we finally have the perfect way of storing the state of our search query!
226226

0 commit comments

Comments
 (0)