Luca Bonavita
Luca Bonavita
Right now modules order depends on the fetching order, hence connected releases can be distant from each others in the chart. Implement one or more sorting strategy: - based on...
- [ ] support all types of version range (#1) - [ ] support releases not sorted by time (#3) - [ ] implement a loader strategy (#4) - [...
If the dependency chain is very log, simply forcing all modules to fit in the screen will make release versions unreadable or even hidden if they are too small. Also,...
Get the module name from the hash fragment - http://mindrones.github.io/timely-dependency-graph/#npm/d3 -> load d3 modules - http://mindrones.github.io/timely-dependency-graph/#npm/backbone -> load backbone modules
For example in [`d3-queue.json`](https://github.com/mindrones/timely-dependency-graph/blob/master/data/d3-queue.json) you can see that releases are not sorted by time: ``` js ... "time": { "modified": "2016-03-03T17:18:21.214Z", "created": "2016-01-23T05:00:32.836Z", "1.2.0": "2016-01-23T05:00:32.836Z", "1.2.1": "2016-01-25T05:38:16.791Z", "1.2.2": "2016-01-25T21:20:04.839Z", "2.0.0":...
If the dependency chain is very long, fetching all modules data can take a lot of time. We can: - simply add a loader and draw when done fetching them...
As of version `1.0.0` it only supports ranges in the form `~1.2.3` as it seems to be the only kind of range used in `d3` modules. For example, if instead...
**Is your feature request related to a problem? Please describe.** I'd like to test it by installing it via `brew cask`. **Describe the solution you'd like** `brew cask install ttth`...
*Problems* - changing a setting/shortcut requires to find the installed package it's supposed to belong to (can be tricky at times, it's a bit time consuming), scroll down and find...