Reusable React environment and components for creating visualization engines.
GPL-3.0 License
Bot releases are visible (Hide)
Published by jhmullen over 3 years ago
@datawheel/[email protected]
This PR updates d3plus to v2, which does three potentially breaking things:
The last two changes will theoretically only effect users who have piggybacked off of the nested d3 and popper dependencies, and even then, only if they are using one of the few modified methods described here: https://github.com/d3plus/d3plus/releases/tag/v2.0.0
Otherwise, this change should be viewed as a positive improvement to visualization styles, so users shouldn't hesitate to upgrade. The suggested steps are:
@latest
from "d3-
to review if mouse
or event
are being used (and change them)from "popper.js
to review if it is being used, and if so migrate to Popper 2
app/d3plus.js
if needed (changelist)Published by jhmullen over 3 years ago
@datawheel/[email protected]
This PR updates d3plus to v2, which does three potentially breaking things:
The last two changes will theoretically only effect users who have piggybacked off of the nested d3 and popper dependencies, and even then, only if they are using one of the few modified methods described here: https://github.com/d3plus/d3plus/releases/tag/v2.0.0
Otherwise, this change should be viewed as a positive improvement to visualization styles, so users shouldn't hesitate to upgrade. The suggested steps are:
@latest
from "d3-
to review if mouse
or event
are being used (and change them)from "popper.js
to review if it is being used, and if so migrate to Popper 2
app/d3plus.js
if needed (changelist)Published by jhmullen over 3 years ago
@datawheel/[email protected]
This PR updates d3plus to v2, which does three potentially breaking things:
The last two changes will theoretically only effect users who have piggybacked off of the nested d3 and popper dependencies, and even then, only if they are using one of the few modified methods described here: https://github.com/d3plus/d3plus/releases/tag/v2.0.0
Otherwise, this change should be viewed as a positive improvement to visualization styles, so users shouldn't hesitate to upgrade. The suggested steps are:
@latest
from "d3-
to review if mouse
or event
are being used (and change them)from "popper.js
to review if it is being used, and if so migrate to Popper 2
app/d3plus.js
if needed (changelist)Published by jhmullen over 3 years ago
This release updates d3plus to v2, which does three potentially breaking things:
The last two changes will theoretically only effect users who have piggybacked off of the nested d3 and popper dependencies, and even then, only if they are using one of the few modified methods described here: https://github.com/d3plus/d3plus/releases/tag/v2.0.0
Otherwise, this change should be viewed as a positive improvement to visualization styles, so users shouldn't hesitate to upgrade. The suggested steps are:
@latest
from "d3-
to review if mouse
or event
are being used (and change them)from "popper.js
to review if it is being used, and if so migrate to Popper 2
app/d3plus.js
if needed (changelist)Published by jhmullen over 3 years ago
Published by jhmullen over 3 years ago
Published by jhmullen almost 4 years ago
This release of the CMS adds support for local image hosting (as opposed to google cloud) as well as reconciliation functionality for if the hosting pattern is split between methods.
Requires running a the usual migration script. However, a faster, easier way to achieve this would be to directly add two new columns to the image
table:
Add two new columns, splash
and thumb
, with type bytea
. This is the only change necessary for a 0.17.0 migration.
Published by jhmullen almost 4 years ago
Published by jhmullen almost 4 years ago
Published by davelandry almost 4 years ago
Published by davelandry almost 4 years ago
Published by davelandry almost 4 years ago
Published by davelandry almost 4 years ago
Published by jhmullen almost 4 years ago
Published by jhmullen almost 4 years ago
Published by jhmullen almost 4 years ago
Published by jhmullen almost 4 years ago
Published by jhmullen almost 4 years ago
Published by jhmullen almost 4 years ago
🔥 change to page routing 🔥
All routes that make use of member id
will now 302 redirect to their slug counterpart.
Users must upgrade to the companion canon-core 20.1 so the redirect will properly work at the server level.
@datawheel/[email protected]
Published by jhmullen almost 4 years ago