jquense

The 0.13.0 improvements to React Components are often framed as "es6 classes" but being able to use the new class syntax isn't really the big change. The main thing of note in 0.13 is that React Components are no longer special objects that need to be created using a specific method (createClass()). One of the benefits of this change is that you can use the es6 class syntax, but also tons of other patterns work as well!

Below are a few examples creating React components that all work as expected using a bunch of JS object creation patterns (https://github.com/getify/You-Dont-Know-JS/blob/master/this%20&%20object%20prototypes/ch4.md#mixins). All of the examples are of stateful components, and so need to delegate to React.Component for setState(), but if you have stateless components each patterns tends to get even simpler. The one major caveat with react components is that you need to assign props and context to the component instance otherwise the component will be static. The reason is

niraj-shah

// ACL to restrict write to user, and public read access
var custom_acl = new Parse.ACL();
// give write access to the current user
custom_acl.setWriteAccess( Parse.User.current(), true);
// give public read access
custom_acl.setPublicReadAccess(true);
GameObject.setACL(custom_acl);

// ACL to restrict write to user, and no public access
var custom_acl = new Parse.ACL();