Replies: 3 comments
|
I can see how that could be useful, but I imagine exposing a mechanism for completing only a subset of transactions could get tricky. In the interim it should already be possible to fetch multiple |
0 replies
|
@stevensJourney Call Yes, it shouldn't allow completing an arbitrary subset of transactions, only the first X transactions should be allowed to be completed. |
0 replies
|
Ah, you are correct. I overlooked that behaviour. I'll see that this request is added to our internal tracker. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
The current
getCrudBatchdoes not care about transactions, this can break transactions in some edge casts.I expect a
getNextCrudTransactionsBatchmethod, which can return more than one transaction at a time.What I expect I can do:
All reactions