Open jdw6359 opened 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?
What do you mean by "local storage"?
A few reccomendations first.
Maybe we should only take in .csv
s? 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.
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.
@mok4ry local storage = database (sorry, that was the term the reqs dos used)
@kocsenc csv's sound fine - will read link
@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.
will implement the download for calendar events first, we can change the formatting from text when we need to - wont be hard
Building endpoint POST @ api/stock_transactions/upload to expect a json array of stock transactions to persist
Given a previously downloaded stock transaction history file, restore the stock transactions to local storage