Iftach Yakar

I actually started writing one and then noticed that there's a [@types/css-tree](https://github.com/DefinitelyTyped/DefinitelyTyped/blob/014c05022b2f2044f92d21a6a0c9b035e67289c1/types/css-tree/index.d.ts) so there you go 💃🏼

As far as I understand at the moment, it seems like we need to make a choice between immutability and the benefits of extending Parse.Objects...

I see that this is probably an RN > 0.29 problem.. A fix is shown here: https://github.com/mholtzberg/react-native-paypal and here: https://github.com/sharafat/react-native-paypal They should probably be integrated to this repo as well..

@RickDT I was thinking the same thing. The only thing which bothers me is that I would want to include my extended subclasses of Parse.Object inside the redux store, but...

@RickDT I see what you mean. Currently I'm using Redux with Parse in the following way: action for queries are dispatched, and a promise-middleware takes care of the async part....

Any updates about this? does this also happen when using parse-react with parse-sdk-js 1.6.14?