Andrew Imm

@ecesena Very odd. In this case, I'd love to know more about this specific error. Version numbers and stack traces will help a lot -- if you can build a...

@ethandt92 I just released 1.6.2 on npm. Among other things, it adds a clause that will skip synchronization of an unknown auth provider, so this error should no longer occur.

Ah crap, you're right. I'll have to figure out how that happened -- our publish script first runs the build script for all 3 releases. Well, onto 1.6.3!

Fantastic to hear. I'll leave this task open for another day or so before closing out.

I'll think of the best way to handle this without patching too much of Parse.Query under the hood. In the meantime, you can actually achieve the same behavior above with...

Sorry all, I haven't had much time to devote to new features lately. Originally, I was opposed to a hook like this, since it's expanding the scope of the originally-proposed...

`toPlainObject` is a utility function for converting the JS SDK's current representation of a Parse Object into a flattened version ideal for Parse+React mutations. This is typically used for the...

Rather than handle it at the component level, I think we should handle it at the internal storage layer. As an initial fix, I'd say a failed subscription should not...

Sorry, I haven't had much time to devote to new Parse+React features lately. I'll open up a discussion task on the matter of disk caching, though.

@mikemintz We've been trying to work out a decent way to expose this expanded functionality on ParseQuery. Most of the trouble is a matter of working out an ideal API....