Reusable React environment and components for creating visualization engines.
GPL-3.0 License
Published by davelandry over 5 years ago
Published by davelandry over 5 years ago
Published by davelandry over 5 years ago
Published by davelandry over 5 years ago
Published by davelandry over 5 years ago
Published by davelandry over 5 years ago
Published by davelandry over 5 years ago
Published by davelandry over 5 years ago
Published by davelandry over 5 years ago
Published by davelandry over 5 years ago
Published by davelandry over 5 years ago
Published by davelandry over 5 years ago
Published by davelandry over 5 years ago
Published by davelandry over 5 years ago
Published by davelandry over 5 years ago
Published by davelandry over 5 years ago
Published by davelandry over 5 years ago
The v0.2 release of canon-vizbuilder
contains a breaking change: any site using the vizbuilder must now add a specific reducer to it's project.
Vizbuilder's state is managed from the site-wide redux state, so is a requirement to setup the Vizbuilder's reducer function.
In app/reducers/index.js
, import the reducer function and assign it to the vizbuilder
key:
import {vbStateReducer} from "@datawheel/canon-vizbuilder";
...
export default {
...
vizbuilder: vbStateReducer,
...
};
Published by davelandry over 5 years ago
canon-cms
v0.2 is an entire rewrite of the CMS (mad props to @jhmullen). We will be creating an update script to migrate old v0.1 databases at a later point. This update includes the following breaking changes:
Moving away from the traditional Profile -> Section -> Topic hierarchy, this PR takes an "Everything is a Topic" approach. This means that profiles are actually quite small now - containing only generators, materalizers, and a title. Everything else, sections, footnotes, topics, vizes - these are all special cases/templates of the generic "Topic," and are organized in an ordered list like a website (as opposed to strictly hierarchically).
Most every entity is now multi-lingual. This required the creation of corollary content
tables that contain translated content, controlled by the CANON_LANGUAGES
environment variable. API endpoints now accept a &locale=<locale>
parameter to fetch content in the given locale, falling back to CANON_LANGUAGE_DEFAULT
if fields are missing.
Update to canon-core 17.4
. The most "breaking" part of this upgrade is the jump from blueprint 1.x to blueprint 3.x (though moving to react 16 caused a few blips as well). I have run both migration scripts and reorganized all labs components and moved all pt-
classes to bp3-
.
Published by davelandry over 5 years ago
Published by davelandry over 5 years ago