An option to cache datasource reads

datasource reads are already cached, though I don't think it's documented...

If you use the --context flag to load datasources, they're read once at startup and always held in memory. If you use --datasource then reference with the datasource/ds function, the data is cached at first read.

Thanks for the reply.

Looking at the source code, I see that the string content of the datasource is cached, but not the parsed result.

I'm working with a large JSON file, so the time it takes to parse each time results in a ~100x slowdown compared to using context.

@BenjyWiener ah. is using context an option? Usually I recommend that anyway, given the simpler syntax.

Reopening since there may be a possible feature request here...

I'm currently using context, but I use a lot of nested/recursive templates, which requires a lot of {{ template "..." (dict "current_item" . "top_level" $.top_level) }}.

I'm currently using context

ok, so then the data and parsed objects are already cached.

but I use a lot of nested/recursive templates,

I'm not sure I follow why this affects caching - could you elaborate? A concrete example would help...

This issue is stale because it has been open for 60 days with no
activity. If it is no longer relevant or necessary, please close it.
Given no action, it will be closed in 14 days.

If it's still relevant, one of the following will remove the stale
marking:

• A maintainer can add this issue to a milestone to indicate that
  it's been accepted and will be worked on
• A maintainer can remove the stale label
• Anyone can post an update or other comment