search

TeamMartinez / YOLO-api

REST API for the yolo project (GitHub Auth)
http://vm344a.se.rit.edu
1 stars 1 forks source link

Restore Stock Transaction History #8

Open jdw6359 opened 8 years ago

jdw6359 commented 8 years ago

Given a previously downloaded stock transaction history file, restore the stock transactions to local storage

jdw6359 commented 8 years ago

@kocsenc more relevant here -- would it be fair to think of the file as raw content coming in the POST body?

The downloaded file is a .txt, so assuming the extension is the same when an upload happens - how should I expect to receive the file? I.E. will it come over as a raw string, or some more complicated object?

mok4ry commented 8 years ago

What do you mean by "local storage"?

kocsenc commented 8 years ago

A few reccomendations first. Maybe we should only take in .csvs? Whatever the format it.

Anyways, it does come in as a POST request. But there are libraries to handle all that niceness. Don't worry about the client, see this.

jonobrien commented 8 years ago

Depends on if we could csv a json object for calendar events, we have a requirement for calendar events being uploaded from the users manually.

jdw6359 commented 8 years ago

@mok4ry local storage = database (sorry, that was the term the reqs dos used)

@kocsenc csv's sound fine - will read link

kocsenc commented 8 years ago

@jdw6359 actually; JSON might be the easiest now that I think about it. If we have power over the format, think of what would be easiest.

jdw6359 commented 8 years ago

will implement the download for calendar events first, we can change the formatting from text when we need to - wont be hard

jdw6359 commented 8 years ago

Building endpoint POST @ api/stock_transactions/upload to expect a json array of stock transactions to persist