6 replies

Handling Mutations with `effect-rx` and Avoiding Unwanted Re-executions

effect-rx

effect-rx

-- Using Rx.fn for mutations is a bit troublesome -- if I

get

get

ctx.result

ctx.result

one of the values of an rx, I end up subscribing to it. And if that subscribed value changes, then the Effect which happen to be a mutation gets ran again.

I can use

once

once

, but that means I can't use initially unmountd

Rx<Result<...>>

Rx<Result<...>>

. I guess a workaround can be i can call

self

self

to check if the

Rx.fn

Rx.fn

has succeded before and return early if it does. But then i'd need to reset it

Rx.fn

Rx.fn

if i want to use it again.

Wondering what you guys use instead for mutations?

Effect Community•13mo ago•

6 replies

jvliwanag

Handling Mutations with `effect-rx` and Avoiding Unwanted Re-executions

effect-rx

effect-rx

-- Using Rx.fn for mutations is a bit troublesome -- if I

get

get

ctx.result

ctx.result

one of the values of an rx, I end up subscribing to it. And if that subscribed value changes, then the Effect which happen to be a mutation gets ran again.

I can use

once

once

, but that means I can't use initially unmountd

Rx<Result<...>>

Rx<Result<...>>

. I guess a workaround can be i can call

self

self

to check if the

Rx.fn

Rx.fn

has succeded before and return early if it does. But then i'd need to reset it

Rx.fn

Rx.fn

if i want to use it again.

Wondering what you guys use instead for mutations?

Handling Mutations with `effect-rx` and Avoiding Unwanted Re-executions

Similar Threads

Handling Mutations with `effect-rx` and Avoiding Unwanted Re-executions

Similar Threads

Similar Threads

Similar Threads