Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

(REBASE) Remove collections dependency and es6-set instead #168

Merged
merged 3 commits into from
Jul 11, 2018

Conversation

hthetiot
Copy link
Collaborator

@hthetiot hthetiot commented Jul 11, 2018

via @alFReD-NSH rebase on v1

1.2 ?

faridnsh and others added 3 commits February 11, 2015 14:28
Since [collections module][1] modifies native objects, it's only good
to be used as a top dependency of an application and not modules that
it's using.

The problem is that this will conflict if native objects has been
modified by another module, let's say something like [sugar][2] or just
another version of collections. When you have two of these being used in
your app, you might be in trouble, where some code depends on a
behaviour of a method implemented by one module but actually the method
had been silently overriden by another module having a different
behaviour.

[1]: http://collectionsjs.com
[2]: http://sugarjs.com
@kriskowal
Copy link
Owner

I think it’s very reasonable to land this in a minor or patch. The dependency on collections is not part of the interface contract.

@hthetiot hthetiot merged commit da89073 into v1 Jul 11, 2018
@hthetiot hthetiot deleted the remove-collections branch July 20, 2018 02:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants