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
I want to consider removing the chained batch API from abstract-level because in my opinion it's not worth the internal complexity. I'm talking about this API:
This API is more verbose but also more composable. I.e. you can .map and .filter the array of operations.
Another option is to keep the chained batch API but change it to internally use the array-based API. It would then just be sugar, with much simpler internals, but no potential performance benefits. This could also live in its own npm package.
cc @Level/core
What do you want to do with the chained batch API?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I want to consider removing the chained batch API from
abstract-level
because in my opinion it's not worth the internal complexity. I'm talking about this API:Which would be removed in favor of the array-based API:
This API is more verbose but also more composable. I.e. you can
.map
and.filter
the array of operations.Another option is to keep the chained batch API but change it to internally use the array-based API. It would then just be sugar, with much simpler internals, but no potential performance benefits. This could also live in its own npm package.
cc @Level/core
1 vote ·
Beta Was this translation helpful? Give feedback.
All reactions