External Sources Local Development Workflows

[thescientist13]

Overview

As part of introducing external data sources in #813, wanted to track a couple of the discussion items that came out of it

Caching

For most users (I am guessing) content likely isn't changing so much that it would make sense for that content to get fetched over and over and over again on each page reload. It would be nice to build in a utility or offer some easy way for developers to cache their responses so that if data exists within a certain time period (1 day, 1 week, etc) the fetch call would not need to happen, and the data could just get read from disk instead.

Think of it like react-query for these external data sources.

Route Collisions

It would make sense for Greenwood to warn if data coming in from an external source is going to collide with other pages added to the graph, including local files. At least warning to the console would help raise awareness since if there are two of the same routes, Greenwood could break, or only show the most recent entry into the graph, thus negating any existing entries matching that route.