You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/BackboneViews.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ first (it's mostly backward compatible with Backbone 1.2 API, so transition is n
9
9
Which by itself will be a big step forward, because:
10
10
11
11
- It's order of magnitude faster, so your application becomes more responsive and you can handle collection which are 10 times larger than you have now. [No kidding](http://slides.com/vladbalin/performance#/).
12
-
- It implements nested models and collections handling in the right way. During `fetch`, nested objects are updated in place, so it's safe to pass them by reference.
12
+
- It implements nested models and collections in the right way. During `fetch`, nested objects are updated in place, so it's safe to pass them by reference.
13
13
- It can handle model references by `id` in attributes for you too, operating on a set of independently fetched collections.
14
14
- It's type-safe, providing the same contract for model attributes as in statically typed language. Thus,
15
15
attributes are guaranteed to hold values of declared types whatever you do, making it impossible to break client-server protocol.
0 commit comments