canon

@datawheel/[email protected]

This PR updates d3plus to v2, which does three potentially breaking things:

1. changes some default visualization styles
2. updates all d3plus and d3 packages to their next major releases
3. updates popper.js from v1 to v2

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:

1. update all canon packages used to @latest
2. search your code for from "d3- to review if mouse or event are being used (and change them)
3. search your code for from "popper.js to review if it is being used, and if so migrate to Popper 2
4. review the visualizations on your site, and make adjustments to app/d3plus.js if needed (changelist)

@datawheel/[email protected]

This PR updates d3plus to v2, which does three potentially breaking things:

1. changes some default visualization styles
2. updates all d3plus and d3 packages to their next major releases
3. updates popper.js from v1 to v2

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:

1. update all canon packages used to @latest
2. search your code for from "d3- to review if mouse or event are being used (and change them)
3. search your code for from "popper.js to review if it is being used, and if so migrate to Popper 2
4. review the visualizations on your site, and make adjustments to app/d3plus.js if needed (changelist)

@datawheel/[email protected]

This PR updates d3plus to v2, which does three potentially breaking things:

1. changes some default visualization styles
2. updates all d3plus and d3 packages to their next major releases
3. updates popper.js from v1 to v2

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:

1. update all canon packages used to @latest
2. search your code for from "d3- to review if mouse or event are being used (and change them)
3. search your code for from "popper.js to review if it is being used, and if so migrate to Popper 2
4. review the visualizations on your site, and make adjustments to app/d3plus.js if needed (changelist)

• Merge pull request #1159 from Datawheel/d3plus-update (62784530)
• fixes deprecated use of d3-selection events (fb8955bd)
• updates d3 and d3plus package dependencies to next majors (7f7d7c28)

This release updates d3plus to v2, which does three potentially breaking things:

1. changes some default visualization styles
2. updates all d3plus and d3 packages to their next major releases
3. updates popper.js from v1 to v2

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:

1. update all canon packages used to @latest
2. search your code for from "d3- to review if mouse or event are being used (and change them)
3. search your code for from "popper.js to review if it is being used, and if so migrate to Popper 2
4. review the visualizations on your site, and make adjustments to app/d3plus.js if needed (changelist)

• bumps blueprint version (e42fbfbc)

• Merge pull request #1157 from Datawheel/issue-1156-searchbyid (94f0947b)
• allows search by id (64a122de)
• Update README.md (6c685a6e)

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.

• Merge pull request #1149 from Datawheel/feature-local-images (fb8e377f)
• Merge branch 'master' of http://github.com/datawheel/canon into feature-local-images (8c84eadc)
• Merge branch 'master' of http://github.com/datawheel/canon into feature-local-images (f725b116)
• fixes size/type bug (01031e71)
• updates script naming (3e544a6e)
• adds docs for local image hosting (c14aea22)
• chmods script (403aff39)
• adds migraiton script to package.json (cc9b8d3d)
• adds migration script (dcf23ea0)
• adds schema snapshot of 0.17 (ac17de1f)
• Merge branch 'master' of http://github.com/datawheel/canon into feature-local-images (c208bf07)
• finishes upload script (387f43c9)
• adds cloudfixer endpoint (e3fdfd84)
• Merge branch 'master' of http://github.com/datawheel/canon into feature-local-images (331fdf3b)
• prepares upload button for local images (37dc1bee)
• adds local image hosting, visible version, hides broken preview column (c6fbf6c4)

• Merge pull request #1152 from Datawheel/hotfix-profile-locale (c73e1799)
• fixes profilesearch locale (fc369ac4)

• bumps olap version (8b3321bb)

• fixes big list of datasets on undefined table closes #1148 (ae752330)

• fixes Vizbuilder component styles (33fb1200)

• reenables measureConfig property (396d8b17)

• fixes print issue with Matrix column Table conflict (7656a0a9)

• hotfixes whitescreen in variableeidtor (b5d7b8cf)

• Merge pull request #1143 from Datawheel/cms-small-bugfixes (46d098a4)
• fixes incorrect Subnav fixed top placement (b7a4e821)
• adds string length cutoff to Selector radio/select switch (8d840db0)
• fixes bugs with single data vizzes and tooltip tbody in simple-viz (7a07e89b)

• Merge pull request #1142 from Datawheel/fix-image-pathing (cdb31414)
• fixes image uploads (f33fa54c)

• Merge pull request #1141 from Datawheel/feature-selector-inception (99cc13d2)
• adds selector ref loop to other selectors (b7566a58)

• Merge pull request #1140 from Datawheel/cms-viz-update (17049f6a)
• passes simple-viz URLs through varSwap (920bf2a0)
• fixes transparency bug with disabled pop-ups in Builder (closes #1119) (b366405a)
• generalizes simple-viz method logic, adding in formatter and title defaults (08997495)
• adds Matrix and RadialMatrix viz options (4a27dd1b)
• fixes workspace d3plus-react (ed8ca4bb)
• updates d3plus-react (56e2758f)
• fixes pnpm workspace (2fc4a849)

🔥 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]

• fixes bad merge in master (22374795)
• compiles @datawheel/[email protected] (62161440)
• Merge pull request #1129 from Datawheel/issue-1095-redirects (4fc27216)
• cleans up regex for redirect (cceaea15)
• Merge branch 'master' into issue-1095-redirects (c74862cf)
• moves var init (40ead547)
• removes unused lines (e17e1ade)
• adds docs, safeguards against bad swaps (47d0580b)
• adds comment (fcaeb398)
• Merge branch 'master' of http://github.com/datawheel/canon into issue-1095-redirects (c4cf14e4)
• handles optional routes and unswapped vars (eb659a04)
• implements redirect middleware (5e244e0b)
• adds logic to mortarroute for redirects (38b05745)