Skip to content

Transforming Handler #185

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
dmjio opened this issue Jun 1, 2018 · 5 comments
Open

Transforming Handler #185

dmjio opened this issue Jun 1, 2018 · 5 comments
Labels

Comments

@dmjio
Copy link

dmjio commented Jun 1, 2018

Is there currently a way (and if not, a plan) for supporting any other Monad besides Handler when resolving queries / mutations? servant accomplishes through a monad morphism. I'd really like to be able to further transform Handler. If this is not supported, and there is no current architecture for doing so, I wouldn't mind giving this a shot. Do advise. cc @jml

@jml
Copy link
Collaborator

jml commented Jun 1, 2018 via email

@dmjio
Copy link
Author

dmjio commented Jun 1, 2018 via email

@jml
Copy link
Collaborator

jml commented Jun 1, 2018

I'm not rejecting your use case—it's a good point. I'm just curious as to the specific motivation.

By all means, do give this a shot.

@dmjio
Copy link
Author

dmjio commented Jun 1, 2018

For example, ReaderT r IO would be a monad I’d like to use. Would it be as simple as making an instance for HasResolver?

@jml
Copy link
Collaborator

jml commented Jun 1, 2018 via email

@teh teh added the question label Jun 6, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants