Fix RxResult performance issue in Browser (#1023)

bigmontz · web-flow · commit dcb0ffd2f997 · 2022-11-25T16:07:19.000+01:00
`setImmediate` was slowing down the result consumption since it postpone the execution to the next cycle.
Since the cycle in Browser is longer, the issue was more perceptive there.

The remove of `setImmediate` doesn't cause any issue with the back-pressure mechanics.
diff --git a/packages/neo4j-driver/src/result-rx.js b/packages/neo4j-driver/src/result-rx.js
@@ -251,7 +251,8 @@ function createFullyControlledSubject (
       } else {
         subject.next(value)
         if (!streamControl.paused) {
-          setImmediate(async () => await pushNextValue(iterator.next()))
+          pushNextValue(iterator.next())
+            .catch(() => {})
         }
       }
     } catch (error) {

Original file line number	Diff line number	Diff line change
`@@ -251,7 +251,8 @@ function createFullyControlledSubject (`
`251`	`251`	`} else {`
`252`	`252`	`subject.next(value)`
`253`	`253`	`if (!streamControl.paused) {`
`254`		`- setImmediate(async () => await pushNextValue(iterator.next()))`
	`254`	`+ pushNextValue(iterator.next())`
	`255`	`+ .catch(() => {})`
`255`	`256`	`}`
`256`	`257`	`}`
`257`	`258`	`} catch (error) {`