[Feature request] selector support for useRecoilTransaction()

I have the following issue.

Let’s say I have atom A with value 1.

1. In mouse event handler the recoil callback with setter is called to set A value to 2.
2. setTimeout callback fires, which in turn contains the recoil callback call. the snapshot in it still contains the A value of 1. The result of first step is not yet applied.

My question. Can I force all of the updates of the recoil callback to be applied right after the callback exits. e.g explicitly force not to batch it into a single transaction with subsequent callback calls ?

So subsequent callback (step two described above) call can read back the written value of previous callback call.

[cneuro]

This is definitely a feature I am missing in Recoil right now. A large application will likely have the requirement to get and set various atoms and selectors in one reusable “transaction” (akin to a traditional reducer), and currently I’ve come across only really one way to achieve this, which is via vanilla React hooks. There are several problems using traditional hooks in this way:

1. There is a lot of boilerplate involved in initializing all the values and setters of the atoms and selectors
2. The hook always needs to return a function that does the setting, which requires wrapping it in a useCallback with all its dependencies (lots of boilerplate again)
3. The only way to get close to the functionality as suggested by useRecoilTransaction is a selector with a setter that does all the work. However, it needs an arbitrary getter which results in confusing and ugly patterns.

It’s entirely possible I am going about this wrong of course - anyone else have a solution akin to useRecoilTransaction but with selectors?

I’d also like to echo @yoavniran and others here from over a year ago; is there a roadmap to move Recoil transactions from UNSTABLE to a permanent feature including the use of selectors? Thanks to @drarmstr and the dev team for all your efforts!

EDIT: typos & grammar

[yoavniran]

Am I right to think that useRecoilTransaction would/should be the only way to write setters with multiple “set” calls? If so, its really missing the option to get from selectors (and not just atoms). Is there a release date we can expect this to become available? thanks!