Breaking: Rename "Iterable" to "Collection" #1139
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change is a major renaming of the base class in Immutable.js from
Iterable
toCollection
. In doing so the existingCollection
subclass is completely removed from the hierarchy.In my experience the difference between the two has been a constant point of confusion for newcomers to the library, and with ES2015 becoming a standard part of the development environment, the name
Iterable
has become ambiguous at best and required awkward workarounds in type definitions before this change.To ease conversion, the
Collection
class is still also exported asIterable
and the newisCollection
function is aliased asisIterable
- existing code will not break.