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
Sorry if this is a wrong place for questions, but I think even if what I'm asking isn't possible now - it can be a feature request in future.
I'm wondering if there's a way to integrate scalajs-react and cats-effect a step further than replacing CallbackTo[A] with IO[A]. In particular I'm wondering if there's a way to subscribe a component to cats.effect.Ref changes (or fs2.Signal, which is more appropriate)?
To avoid an XY problem - I'd like to use Ref to communicate between neighbour components by passing it as an argument to both of them. Imagine it's similar to what Context does, but I like the API much more.
The text was updated successfully, but these errors were encountered:
Hi @chuwy. I haven't used cats.effect.Ref but I do have a vague, ancient memory of fs2.Signal so I think I know what you mean. Sounds like a cool idea worth exploring. Not sure If you want to take a shot at a PR or not, but if you do feel free to ask for guidance along the way
Sorry if this is a wrong place for questions, but I think even if what I'm asking isn't possible now - it can be a feature request in future.
I'm wondering if there's a way to integrate scalajs-react and cats-effect a step further than replacing
CallbackTo[A]
withIO[A]
. In particular I'm wondering if there's a way to subscribe a component tocats.effect.Ref
changes (orfs2.Signal
, which is more appropriate)?To avoid an XY problem - I'd like to use
Ref
to communicate between neighbour components by passing it as an argument to both of them. Imagine it's similar to whatContext
does, but I like the API much more.The text was updated successfully, but these errors were encountered: