You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Question: Feel free to just state your question. For a quick answer, there are usually people online at our Gitter channel
MobX currently defines a custom Iterator interface that is used for stuff like ObservableMap.keys(), etc. This conflicts with the built-in Flow Iterator interface, and, in particular, is missing Flow's current @@iterator hack to recognize iterators. This essentially means that you can't use Array.from or similar methods with MobX types, since Flow doesn't recognize them as iterators.
I've tested just removing the Iterator interface from the Flow definitions in MobX, and everything seems to work fine, but I'd like to gauge others' interest before submitting a PR that does this.
The text was updated successfully, but these errors were encountered:
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs or questions.
lockbot
locked as resolved and limited conversation to collaborators
Jul 21, 2019
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I have a:
MobX currently defines a custom Iterator interface that is used for stuff like
ObservableMap.keys()
, etc. This conflicts with the built-in FlowIterator
interface, and, in particular, is missing Flow's current@@iterator
hack to recognize iterators. This essentially means that you can't useArray.from
or similar methods with MobX types, since Flow doesn't recognize them as iterators.I've tested just removing the
Iterator
interface from the Flow definitions in MobX, and everything seems to work fine, but I'd like to gauge others' interest before submitting a PR that does this.The text was updated successfully, but these errors were encountered: