The cached data used the template name and a hash that is built based on the arguments used to generate it.
Further, data is always stored in rds format.
One interesting alternative is the use of parquet files to store data.
With that duckdb could be used to query data on these files and the cache would form a database.
To get this done, and easy to debug and follow, a name formation rule should be interesting for cached files.
A naming function should be created to name cached data.
This naming function would be declared in the template file, the same way is done with downloader and reader.
The cached data used the template name and a hash that is built based on the arguments used to generate it. Further, data is always stored in rds format.
One interesting alternative is the use of parquet files to store data. With that duckdb could be used to query data on these files and the cache would form a database.
To get this done, and easy to debug and follow, a name formation rule should be interesting for cached files.
A naming function should be created to name cached data.
This naming function would be declared in the template file, the same way is done with downloader and reader.