Andrew Imm

Ah -- I overlooked that bit. Let me think about this for a bit, and see if there's a reasonable way to implement this without having a subscription that watches...

We try to print out a warning if you subscribe to something that doesn't support the subscribe() interface: https://github.com/ParsePlatform/ParseReact/blob/master/lib/Mixin.js#L125 Warnings only print when you're using a development-mode (read: non-minified) version...

Glad to hear it's making a difference in your development cycle! Hmm, seems like I need to rethink the code behind `warning()`. Originally when we released the library, the npm...

We can definitely produce standalone declarations for third party apps to use. It never occurred to me that the babel compilation wouldn't remove those flow annotations. You can track this...

@TristanBBQ are you using ES6 and Babel to write/transpile your code? Do you have a small piece of code that can reproduce this bug?

Just encountered this myself. Not sure what's happening, but I'm guessing it's related to the initial render loop of a component. Digging in further...

Thank you. We've been actively working on getting an update to Parse+React today to follow up on these changes.

1.6 is supported in version 0.5.0 of Parse+React. Let me know if you encounter any issues!

@ecesena Can you be more specific about the issue in 4? I've run it against our FB Login integration tests and it seems to be fine, but because using fb...

@ecesena I think it may happen when you have Parse Users with FB auth data, but the application isn't registered to use the FB Auth Provider. I have a fix...