You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My stack is mostly cats/IO based, doobie, http4s, and so on, and autowire would fit in more naturally (i.e. no unsafeToFuture calls or having to choose to return Int or Future[Int]) if I could make the server side generated code have a different effect type (i.e. the usual F[_], which for me would be cats.effect.IO).
I understand this may not be something you would want to spend any time on, but perhaps you/anyone could give your thoughts on the amount of surgery needed? I'd like to try it.
Note: PR #76 adds support for IO but by calling unsafeToFuture, I would like to avoid the Futures altogether.
Thank you!
The text was updated successfully, but these errors were encountered:
Hi,
Love autowire, using it extensively.
My stack is mostly cats/IO based, doobie, http4s, and so on, and autowire would fit in more naturally (i.e. no
unsafeToFuture
calls or having to choose to returnInt
orFuture[Int]
) if I could make the server side generated code have a different effect type (i.e. the usualF[_]
, which for me would becats.effect.IO
).I understand this may not be something you would want to spend any time on, but perhaps you/anyone could give your thoughts on the amount of surgery needed? I'd like to try it.
Note: PR #76 adds support for
IO
but by callingunsafeToFuture
, I would like to avoid theFuture
s altogether.Thank you!
The text was updated successfully, but these errors were encountered: