dabcoder/stocks

Haskell library for the IEX trading API: https://iextrading.com/developer/docs/

stocks's Issues

[develop] Implement time series

https://iextrading.com/developer/docs/#time-series

[develop] Peers

https://iextrading.com/developer/docs/#peers

Make record names unique

Right now, we have a big problem due to using DuplicateRecordFields in Stocks.hs

It is possible to get data structures from this module,
but it is then not possible to pick data out of these data structures because the
record accessor functions will be ambiguous in the user's code

I propose to put each data structure in its own module, so that we can then pick out
for instance 'symbol' from 'Company' like (IEXCompany.symbol companyData)

Release 0.2.0.1

Let's make a new release? I merged develop to trunk with updated change notes

[develop] Look at and implement Reference data

https://iextrading.com/developer/docs/#reference-data

• Symbols
• IEX Corporate Actions
• IEX Dividends
• IEX Next Day Ex Date
• IEX Listed Symbol Directory

[develop] IEX Markets (not the same as IEX Market Data)

https://iextrading.com/developer/docs/#market

[testing] Create better tests

Right now the HUnit tests only makes calls to the IEX API and then makes sure the reply is not 'Nothing'. It would be better to see that the results are what we expect them to be.

[develop] IEX Regulation SHO Threshold Securities List

Adapt this code to the new IEX cloud API

Working on it in branch 'iexcloud'

Handle connection/404 errors

getNonJSONData :: String -> IO L8.ByteString
getNonJSONData query = do
    obj <- simpleHttp query
    return obj

getNonJSONData will simply crash if simpleHttp does not succeed. instead return (Either err bytestring) #

[develop] Use Text instead of String?

I was recommended to use Data.Text instead of the String type, but I do not know enough about this topic to be able to say which one would be best for this project.

Some resources:

• https://stackoverflow.com/questions/19608745/data-text-vs-string
• http://www.alexeyshmalko.com/2015/haskell-string-types/

Release 0.2.0.0

It would be good to think about an upcoming release on Hackage as the [develop] branch has a lot of new additions compared to version 0.1.0.0: http://hackage.haskell.org/package/stocks.

[develop] Implement batch requests

https://iextrading.com/developer/docs/#batch-requests

Add Changelog

[develop] Implement book API call

https://iextrading.com/developer/docs/#book

[develop] IEX Short Interest List

https://iextrading.com/developer/docs/#iex-short-interest-list

[develop] IEX Stats

https://iextrading.com/developer/docs/#iex-stats

• Intraday (added)
• Recent
• Records
• Historical Summary
• Historical Daily

[type system] relation between query parameters and results

Currently, (in the batch queries, since they are the only ones supporting parameters) it is possible for the code to return resulting data structures that have nothing to do with the parameters given.

I would like the type system to know about the relation between input parameters and output data structures. Perhaps using type families?

[develop] Relevant

https://iextrading.com/developer/docs/#relevant

[develop] Fix so we are able to give params to the API

to be able to give different options to IEX, 5y, 2y, 1y
start with: https://iextrading.com/developer/docs/#chart

CI

TravisCI, CircleCI, GitLab...?

Should it run the tests in Tests to get started?

[develop] IEX market data

https://iextrading.com/developer/docs/#iex-market-data

• TOPS
• Last
• HIST
• DEEP
• Book
• Trades
• System Event
• Trading Status
• Operational Halt Status
• Short Sale Price Test Status
• Security Event
• Trade Break
• Auction
• Official Price