Having a Tagless Final version of the API about blockfrost-haskell HOT 3 CLOSED

Hi, sounds good to me but to be honest, I'm not sure how to convert it to tagless final right away. If you have good example I can take a look at or draft a solution here it would help a lot.

Regarding breaking the API - I don't think there are that many users of this library so it should be fine.

from blockfrost-haskell.

I've remembered about https://jproyo.github.io/posts/2019-03-17-tagless-final-haskell.html and it makes sense, having a typeclass BlockfrostClient (or maybe just Blockfrost to avoid name clashes) with instance that can possibly call the fixed mtl client functions. What I'm not sure about is ReaderT containing Project, maybe we can just wrap our old BlockfrostClient type though. I'll play with it a bit!

from blockfrost-haskell.

Hi, I've opened #11 which adds MonadBlockfrost class allowing you to use a custom monad instead of the default BlockfrostClient.

Using this I was able to compose it with example TestapiM like this:

class Monad m => TestapiM m where
  mGetTest :: m Bool

sample :: (MonadBlockfrost m, TestapiM m) => m ()
sample = pure ()

type GlobalConfig = (Bool, ClientConfig)
type App = ReaderT GlobalConfig (ExceptT ClientError IO)

runApp :: ClientConfig -> App a -> IO (Either ClientError a)
runApp globalC = runExceptT . flip runReaderT (True, globalC)

instance TestapiM App where
  mGetTest = fst <$> ask

instance MonadBlockfrost App where
  liftBlockfrostClient act = getConf >>= \(env, _prj) -> 
    (liftIO $ runClientM act env)
  getConf = snd <$> ask

Would this work for you?

from blockfrost-haskell.