More Accurate Dependencies
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 67
- Forks
- 58
- PR merge metrics
- No merged PRs in 30d
Description
It has occurred to me that we are reliant on a number of d3 related repositories such as d3-simple-slider and d3-tip, but this is not reflected in the dependency graph. We may want to find a way to explicitly tell github that we use these things. I don't think the cdn (#34) affects this at all, but I think the dependency graph is a good thing to keep in mind for the future.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing GitHub dependency graph support for the repository and the d3-related repositories named in the issue, including d3-simple-slider and d3-tip. Check whether the CDN discussion in issue #34 changes the dependency scope. Done means the relevant dependencies are explicitly represented in the graph, with the approach documented or demonstrated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- d3, javascript, jekyll
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100