svizzle
svizzle copied to clipboard
nestauk
Svelte components for data visualisation and utilities for data transformation.
Possibly related ot #144
In Firefox and Chrome. https://svelte.dev/repl/00def41d8bee47e387087c044d5a2b61?version=3.24.0
We could move these: - `packages/components/ui/src/icons/` -> `packages/components/icons/src/` - `packages/components/ui/src/bin/makeFeatherIcons.js` -> `packages/components/icons/src/bin/makeFeatherIcons.js`
We could move these: - `packages/components/ui/src/a11y/*` -> `packages/components/a11y/src/*`
We could to move these to a new package, tentatively named `@svizzle/io`: - `packages/components/ui/src/drivers` -> `packages/components/io/src/io` - `packages/components/ui/src/io` -> `packages/components/io/src/drivers` - `packages/components/ui/src/sensors` -> `packages/components/io/src/sensors`
- investigate which functions of [1] are not covered by existing functions in `lamb` or `@svizzle/utils` - for those having a correspondent function in `@svizzle/utils` [2], make sure they have...
- investigate which functions of [1] are not covered by functions accepting iterables in `lamb` or `@svizzle/utils` - for those having a correspondent function in `@svizzle/utils` [2], make sure they...
- investigate which functions of [1] are not covered by functions accepting iterables in `lamb` or `@svizzle/utils` - for those having a correspondent function in `@svizzle/utils` [2], make sure they...
In a WIP PR se: outmost regions we're going to clip them from the map and filter out their data to avoid doing too many things in the same PR....