Skip to content
This repository has been archived by the owner on Nov 11, 2018. It is now read-only.

ES6 Collections. #11

Closed
mbostock opened this issue Nov 30, 2016 · 2 comments
Closed

ES6 Collections. #11

mbostock opened this issue Nov 30, 2016 · 2 comments

Comments

@mbostock
Copy link
Member

What would d3-collection look like if we dropped the d3.map and d3.set implementations? You might still want a d3.map with a key accessor for constructing a Map from an array of data (the key would default to index if not specified, and perhaps #10 you’d also allow an optional value accessor), and a d3.set with an optional accessor.
@mbostock
Copy link
Member Author

mbostock commented Dec 7, 2016

Related to this, d3.nest’s keys would no longer be coerced to strings.

Likewise, we might change ordinal scales to not coerce the domain to strings.

@mbostock mbostock mentioned this issue Dec 7, 2016
Closed
@gunn gunn mentioned this issue Jan 18, 2017
Closed
@mbostock
Copy link
Member Author

Moving to d3/d3-array#75.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@mbostock