Abhinav Tushar
Abhinav Tushar
Yes, so here is what it would look like  - The gray region shows the data version time (week 49 here but could be something non discrete). - Time...
Fix for allowing timestring is up in v0.9.9 (`https://unpkg.com/[email protected]/dist/d3-foresight.min.js`). We will definitely be needing an explanation. I feel `data as of`/`data used` feels more intuitive as compared to `data version`....
1. Hmm, that was not a problem earlier since we were using the gray region (data version date) as an indicator for the time zero. Now we need to have...
For 1, we can also add _another_ vertical line instead of overloading the mouse hover line.
Try `v0.9.10` (https://unpkg.com/[email protected]/dist/d3-foresight.min.js). I added the following: 1. Descriptive text for the shaded region (says `data as of`; we can change/hide this in simpler situations) 2. Another vertical line showing...
Did you mean a toggle in the UI (the user might do this) or a toggle in the config (the programmer, while plotting will do)? EDIT: We already don't show...
Will be doing this sometime this week.
Done in [0.10.1](https://www.npmjs.com/package/d3-foresight). Documentation [here](http://reichlab.io/d3-foresight/#timechart-dvt).
@vipul-sharma20 what are the next steps in this
Note to self: The best way is to import the `sass` from spectre and `extend` the classes. The problem right now is that spectre was in `less` at 846353cb40512404c5b8d27084a6fbe7b4a47d23. Should...