Open cristian-sima opened 8 years ago
@moroshko Any thought on this?
Following the conversation from here https://github.com/pburtchaell/react-notification/issues/92 it seems there is no simple, free dependent way of creating this.
However, I am thinking of another way of approaching this problem.
We can create a new branch called support-immutablejs
which contains this dependency react-immutable-proptypes
(and implicit the immutable dependecy). Taking into account that those interested in using support-immutablejs
will already use immutable, they will not find it as a problem.
For all others, there will be the master branch which is free dependent. For any updates on master, we can update the support-immutablejs
branch from master.
What do you think?
Using .toArray() on an immutable iterable will still keep the entries as immutable, which is what I've done.
The getSuggestionValue
and renderSuggestion
functions can handle immutable entries fine.
Let's take this code:
This code does not work. I got:
However, if I do
it then works, however there is a big problem.
I will lose the benefits of Immutable if I change the code to
Immutable.List().toArray (or toJS))
as presented hereAlso here.
Other comment about this:
So, in the end, the request is to support Immutable types