Request caching is not configurable #9
Description
Currently, the request caching is not configurable. Ideally, it would be nice to allow for consumers to be able to specify the cache size/timeout. I'm not sure what a normal pattern for this is, but there are a few options:
- Some kind of configuration file (pretty ugly, I don't like this)
- Export functions to modify the configuration (also ugly)
- Instead of exporting the schema directly, export a function that lets you generate a schema, with configuration options
- This feels like the most reasonable thing to do, will require some restructuring of the tempus API adapter, but it doesn't seem too awful
The last one makes the most sense to me, but I'll want to do some investigation into how other projects have tackled problems like this first.