Feature request: Support GOOGLEFINANCE historical parameters (`start_date`, `end_date`, `interval`)

[benjaminpo]

CACHEFINANCE currently supplements GOOGLEFINANCE for single current values (price, name, yieldpct) and caches values when GOOGLEFINANCE returns #N/A. It does not support GOOGLEFINANCE's historical query parameters:

• start_date
• end_date / num_days
• interval ("DAILY" | "WEEKLY")

Users (like me) who rely on historical series from GOOGLEFINANCE cannot use CACHEFINANCE as a fallback . Correct me if I'm wrong.

[demmings]

benjaminpo,

You are correct that it currently does no caching of the historical prices. My original problem was my daily trigger to record portfolio values failed on a regular basis and caching of historical stock prices was not what I needed.

The function could be modified to mimic all GOOGLEFINANCE() functionality, but there is virtually nobody visiting this github repository so I have only been making changes that I required and then updating github repository periodically.

[danieleds]

I agree that would be very useful. My use case for historical prices is so that, at the end of each month, my portfolio spreadsheet can look at the beginning of the month to record the price differences.

In any case @demmings thanks a lot for the tool, it saved my day

[demmings]

I will take a look. This change would not be doing any 3'rd party website lookups, so it would only be caching results from GOOGLEFINANCE(). Currently the 3'rd parameter to CACHEFINANCE() is the default results from GOOGLEFINANCE(). The first and second parameters are used to create the cache key AND lookup data from 3'rd party websites when google is failing. Since CACHEFINANCE would never look this data up, it is more of a matter coming up with how the second parameter is formatted so it can be used as a cache key and to return the data as a double array.

[demmings]

Hey @benjaminpo , getting stuck with src change. I built the dist file, which looks correct with all recent changes, but is failing test.
I am not really following how the tests are run. I am looking at it now, but any help would be appreciated.

Chris.