svizzle
svizzle copied to clipboard
nestauk
Svelte components for data visualisation and utilities for data transformation.
Lerna has released [`v4.0.0`](https://github.com/lerna/lerna/releases/tag/v4.0.0), so we might want to check new features first.
They don't play well with the formatter in the GitHub Release/Tag page
Aftr [updating rollup](https://github.com/nestauk/svizzle/pull/97) we need to check next releases of Sapper to fix [1] See: - [x] https://github.com/rollup/rollup/ pull/3659 - [x] https://github.com/sveltejs/sapper/ pull/1326 (waiting for Sapper 0.28 to be released)...
When building the doc site we're getting one message like [1] for: - `/components/BarchartVDiv-keyToColorFn` - `/components/BarchartVDiv-keyToLabelFn` - `/components/BarchartVDiv-valueAccessor` - `/components/BarchartVDiv-formatFn` - `/components/ChoroplethG-keyToColorFn` - `/components/ChoroplethG-focusedKey` - `/components/ChoroplethG-projection` - `/components/HistogramG-ticks` - `/components/HistogramDiv`...
For example, navigating at https://nestauk.github.io/svizzle/components/HistogramG-interactivity and clicking on `non uniform bins` we should navigate to something like `/components/HistogramG-interactivity#non-uniform-bins`. Conversely, landing directly at `/components/HistogramG-interactivity#non-uniform-bins` should select the `non uniform bins` option.
Create routes to substitute the automatically generated documentation, using the jsdoc parser to generated data for the new routes
to ease navigation we could have split there files by output type: - `read.js` - `read/dsv.js` - `read/exportedJs.js` - `read/object.js` - `read/yaml.js` - `write.js` - `write/dsv.js` - `write/exportedJs.js` - `write/object.js`...
We are currently using say `@arg {string} foo`, or `@arg {object} bar`, but `@arg {regexp} par` would not autocomplete to a RegExp when hovering `par`. For consistency we agreed to...
