counterexample -> antipattern
Ben Alpert committed
Jul 20, 2015 at 08:28 UTC
d13fafa5dd14406153d6cd629ee4efc00cb25397
2 files changed
+3
-3
docs/docs/07-forms.md
+1
-1
@@ -129,7 +129,7 @@ Since this method describes the view at any point in time, the value of the text
129
In HTML, the value of `<textarea>` is usually set using its children:
130
131
```html
132
- <!-- counterexample: DO NOT DO THIS! -->
132
+ <!-- antipattern: DO NOT DO THIS! -->
133
<textarea name="description">This is the description.</textarea>
134
```
135
docs/docs/08.1-more-about-refs.md
+2
-2
@@ -48,7 +48,7 @@ Notice how, in this example, we want to "tell" the input something - something t
48
This means that you should never "hold onto" something that you return from `render()` and then expect it to be anything meaningful.
49
50
```javascript
51
- // counterexample: DO NOT DO THIS!
51
+ // antipattern: This won't work.
52
render: function() {
53
var myInput = <input />; // I'm going to try to call methods on this
54
this.rememberThisInput = myInput; // input at some point in the future! YAY!
@@ -61,7 +61,7 @@ This means that you should never "hold onto" something that you return from `ren
61
}
62
```
63
64
-In this counterexample, the `<input />` is merely a *description* of an `<input />`. This description is used to create a *real* **backing instance** for the `<input />`.
64
+In this example, the `<input />` is merely a *description* of an `<input />`. This description is used to create a *real* **backing instance** for the `<input />`.
65
66
So how do we talk to the *real* backing instance of the input?
67