Should not dependencies be relaxed or updated?

[madjestic]

Hey guys,

I've edited the .cabal like this:
https://github.com/madjestic/iexcloud/blob/iexcloud/iexcloud.cabal
And it built ok.

Should not the dependencies be more relaxed to be more future ompatible? Or, perhapse, there needs to be a new release?

Cheers.
Vlad

[ksallberg]

Hello,

I think that you are probably right. I have not used this lib since IEX started charging for basic features - I cannot even run the tests anymore. I don't know how to get around that.

[ksallberg]

I contacted IEX support to ask if they can provide this project with some sort of API key we can use for testing and development. @madjestic would you like to create a PR?

[madjestic]

I think they still have a free version "Test your ideas with 50,000 core messages/mo on a limited platform for free." Do you know of a better alternative though?

I'll create a PR.

Cheers,
Vlad

[madjestic]

Dang, I think I screwed up the PR. I've changed a few more files which I'd rather not share and I don't know an easy way to just PR the cabal... Maybe I need to finish the clean up at least.

[madjestic]

I contacted IEX support to ask if they can provide this project with some sort of API key we can use for testing and development.

https://intercom.help/iexcloud/en/articles/2915433-testing-with-the-iex-cloud-sandbox
Is that not what you are looking for?

[ksallberg]

@madjestic no worries. yes right, we already have some functions that use the sandbox API - I had just forgotten. issue #1 is about that

[madjestic]

I noticed that every *.hs file seems to have import Data.Maybe, even if it's redundant. Is that intentional?

For now I commented out everything that I get a warning from ghc.

[ksallberg]

No it is not intential, it is probably a copy paste error. From the beginning we had just one .hs file with all functions in, but then I separated into several files because otherwise the record fields would conflict.