🔨 bake chart view map / TAS-829

[sophiamersmann]

Bakes http://staging-site-bake-chart-views/grapher/_chartViews.json that maps chart view names to chart config IDs.

The Figma plugin uses this information for autocompletion and to fetch a chart view via UUID.

Ideally, we don't trigger a full rebuild when a chart view is created or deleted. I imagine authors creating a chart view going directly to Figma to try to import it, so there shouldn't be a too-long lag.

We wouldn't need to bake if we exposed the map on the Admin API instead, but Mojmir said auth is tricky. I wonder if we could add another auth method to our admin that would make that easier? But I don't think it's a good use of my time to think about admin auth at the beginning of the cycle, so I want to go with this for now. It would be easy to revert these changes if I reconsider during the cycle.

The map is baked to /grapher/_chartViews.json. I named it similarly to /grapher/_grapherRedirects.json, but I'm happy to rename it if the name I chose is awkward.

[owidbot]

Quick links (staging server):

Site Dev	Site Preview	Admin	Wizard	Docs

Login: ssh owid@staging-site-bake-chart-views

• Site-screenshots: https://github.com/owid/site-screenshots/compare/bake-chart-views
• SVG tester: https://github.com/owid/owid-grapher-svgs/compare/bake-chart-views

SVG tester:

Number of differences (default views): 0 ✅
Number of differences (all views): 0 ✅

Edited: 2025-01-24 10:16:17 UTC
Execution time: 1.32 seconds

[notion-workspace]

Bake a chart view map that links chart view names to config UUIDs

[marcelgerber]

Nice!

As for the timeliness of updates, it may just be fine to make a route like this publicly accessible without auth, i.e. put it in publicApiRouter? Although, while testing this, I noticed that publicApiRouter is not really public anymore - https://owid.cloud/api/health is behind CF Auth, too, and we would probably need to put up an exclude rule for CF Auth to make it properly work again 🤠

[sophiamersmann]

I didn't know we have an admin router that is meant to be publicly accessible (although it isn't really at the moment). If we could make that work, that would be best, but I know too little about this stuff. Let's chat about it tomorrow?

[marcelgerber]

Let's chat about it tomorrow?

sure!