[Feature] getNextCrudTransactionBatch #593
Draft
+116
−2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
Some users have requested the ability to batch upload multiple transactions using the
uploadData
handler. However, the existinggetNextCrudBatch
andgetNextCrudTransaction
methods make this process somewhat cumbersome.getNextCrudBatch
does not group items by transaction, and completing the batch removes all of its CRUD items from the queue. This makes it difficult for developers to fetch and complete a batch corresponding to multiple related transactions.getNextCrudTransaction
returns only the CRUD entries for a single transaction. Developers are effectively forced to upload transactions one at a time, as repeated calls will continue to return the first pending transaction until it has been completed.This PR introduces a new method,
getNextCrudTransactionBatch
(name subject to change), which returns aCrudBatch
containing items from multiple CRUD transactions. This allows for more efficient and flexible batch uploads.Related to #415