You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
getSymbols.tiingo function signature and implementation expose details of the tiingo API that are not needed. specifically:
the data.type parameter affects the protocol between tiingo and quantmod. Since the quantmod implementation always converts the data to an xts, the caller is not affected by data is transferred over the wire and it just adds complexity. one path should be selected and this should be hard coded as an implementation detail. @tiingo has stated that the csv implementation is very slightly more efficient, so that would get my vote
The text was updated successfully, but these errors were encountered:
ethanbsmith
changed the title
simplify getSymbol.tiingo
simplify getSymbols.tiingo
Oct 15, 2021
Remove the data.type parameter because getSymbols.tiingo() always
converts to an xts object. This user is not affected by which protocol
is used and handling the JSON response adds complexity. Use the CSV
interface because Tiingo said it's slightly more efficient and it
simplifies our implementation.
Fixes#343.
getSymbols.tiingo
function signature and implementation expose details of the tiingo API that are not needed. specifically:the
data.type
parameter affects the protocol between tiingo and quantmod. Since the quantmod implementation always converts the data to anxts
, the caller is not affected by data is transferred over the wire and it just adds complexity. one path should be selected and this should be hard coded as an implementation detail. @tiingo has stated that thecsv
implementation is very slightly more efficient, so that would get my voteThe text was updated successfully, but these errors were encountered: