Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

simplify getSymbols.tiingo #343

Closed
ethanbsmith opened this issue Oct 15, 2021 · 1 comment · Fixed by #344
Closed

simplify getSymbols.tiingo #343

ethanbsmith opened this issue Oct 15, 2021 · 1 comment · Fixed by #344
Assignees

Comments

@ethanbsmith
Copy link
Contributor

ethanbsmith commented Oct 15, 2021

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

@ethanbsmith ethanbsmith changed the title simplify getSymbol.tiingo simplify getSymbols.tiingo Oct 15, 2021
@ethanbsmith
Copy link
Contributor Author

this will simplify working on #289

joshuaulrich pushed a commit that referenced this issue Oct 16, 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.
joshuaulrich added a commit that referenced this issue Apr 29, 2022
@joshuaulrich joshuaulrich added this to the Release 0.4.20 milestone Mar 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants