如何在最新的 Parse js sdk (1.6.2) 中实现 Backbone 模型？
How do I implement the Backbone model in latest Parse js sdk (1.6.2)?
Backbone.Collection 对应的 Parse Collection class 不再存在于 SDK 中。它曾经在 1.2.13 中存在。
自 2015 年 9 月 9 日起，Parse Javascript SDK 不再包含 backbone 特定行为。您可以参考以前版本的 JS SDK (http://www.parsecdn.com/js/parse-1.5.0.min.js) 来访问 backbone 特定行为，但要了解该分支已不再维护。
V1.6.0 — SEPTEMBER 9, 2015
New Features
Designed to work with ES6. Parse.Object can be treated as a class, and
can be subclassed with the extend keyword
When subclassing Parse.Object, you will need to call
Parse.Object.registerSubclass()
Better support for different platforms, with custom builds for React
Native and Node
All platforms still use the “parse” npm module, but node.js
applications should use “require(‘parse/node’)” and React Native
applications should use “require(‘parse/react-native’)”
Objects can be created from JSON with Parse.Object.fromJSON()
Pointers can be generated with Parse.Object.prototype.toPointer()
All SDK configuration is now stored in Parse.CoreManager
Controllers for concepts like local storage can be hot-swapped via
CoreManager
Changes
SDK no longer contains Backbone-specific behavior. Moving forward, the
core SDK will not be tied to any single framework, but we will work
with the community to produce up-to-date bindings like Parse+React.
The major changes are the removal of Parse.Collection, and allowing
Parse.Objects to act as event channels.
SDK no longer ships with Underscore.js included.
Field type mismatches (trying to increment a string field) will now
throw exceptions on the client side.
In server environments where the current user has not been explicitly
enabled, fetching the current user will now return null instead of
throwing. Attempts to change the current user through logIn or become
will still throw.
Parse.Ops no longer publicly expose their values
Backbone.Collection 对应的 Parse Collection class 不再存在于 SDK 中。它曾经在 1.2.13 中存在。
自 2015 年 9 月 9 日起，Parse Javascript SDK 不再包含 backbone 特定行为。您可以参考以前版本的 JS SDK (http://www.parsecdn.com/js/parse-1.5.0.min.js) 来访问 backbone 特定行为，但要了解该分支已不再维护。
V1.6.0 — SEPTEMBER 9, 2015
New Features
Designed to work with ES6. Parse.Object can be treated as a class, and can be subclassed with the extend keyword
When subclassing Parse.Object, you will need to call Parse.Object.registerSubclass()
Better support for different platforms, with custom builds for React Native and Node
All platforms still use the “parse” npm module, but node.js applications should use “require(‘parse/node’)” and React Native applications should use “require(‘parse/react-native’)”
Objects can be created from JSON with Parse.Object.fromJSON()
Pointers can be generated with Parse.Object.prototype.toPointer()
All SDK configuration is now stored in Parse.CoreManager
Controllers for concepts like local storage can be hot-swapped via CoreManager
Changes
SDK no longer contains Backbone-specific behavior. Moving forward, the core SDK will not be tied to any single framework, but we will work with the community to produce up-to-date bindings like Parse+React. The major changes are the removal of Parse.Collection, and allowing Parse.Objects to act as event channels.
SDK no longer ships with Underscore.js included.
Field type mismatches (trying to increment a string field) will now throw exceptions on the client side.
In server environments where the current user has not been explicitly enabled, fetching the current user will now return null instead of throwing. Attempts to change the current user through logIn or become will still throw.
Parse.Ops no longer publicly expose their values