reset operator

[sergeysova]

Sometimes we need to reset a bunch of stores on a single event, ex.: page unmounted

$post.reset(pageUnmounted)
$comments.reset(pageUnmounted)
$draftComment.reset(pageUnmounted)

I propose a new method reset:

reset({
  clock: pageUnmounted,
  target: [$post, $comments, $draftComment],
})

With support of multiple reset:

reset({
  clock: [pageUnmounted, pageMounted, $userSession],
  target: [$post, $comments, $draftComment],
})

[AlexandrHoroshih]

Sounds cool!

Implementation is obvious as well as the benefits 👍

[doasync]

I think it should work with a single target as well, so I would name the field target similar to the sample/guard.

[sergeysova]

But why you need it?

reset({ clock: event, target: $store })
// is the same as
$store.reset(event)

Second variant is shorter and already exists in effector

[AlexandrHoroshih]

I would agree here: for consistency with original operators of effector it would be cool to name field target + allow to pass only one store instead of array

This way it will be more clear, i think 🤔

reset({
 clock: [pageUnmounted, reloadTriggered],
 target: $someState
})

if later there will be more stores to reset, you would just need to add more targets as array, just like with sample

[doasync]

But why you need it?

So that you can use the full version everywhere (for consistency), without mixing the two styles, and avoid rewriting the shorter version into the full version when needed.

[sergeysova]

#181

[sergeysova]

Locked, because already implemented