The API call that gets it doesn't have any caching parameter. It should be trivial to add those with a maxage parameter. Maybe don't add caching if the user is logged-in so that editors who modify the graph data see their updates immediately, but for unlogged visitors, the graph data should be cached for at the very least a few minutes.
Description
Description
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Open | Request | None | T274738 Archive the graphoid service and deploy repos | ||
Resolved | Clement_Goubert | T242855 Undeploy graphoid | |||
Resolved | • Gilles | T240626 Performance review of client-side-only version of Graph extension | |||
Stalled | None | T256642 Cache clientside json for graph |
Event Timeline
Comment Actions
The api call is currently not in use, at the moment it is using the jsconfigvars to fetch the json for the graph. This might change again in the future.