-
-
Notifications
You must be signed in to change notification settings - Fork 597
Remove batch size from SaveAll and DestroyAll #1047
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Codecov Report
@@ Coverage Diff @@
## master #1047 +/- ##
==========================================
+ Coverage 92.19% 92.22% +0.02%
==========================================
Files 54 54
Lines 5152 5133 -19
Branches 1145 1139 -6
==========================================
- Hits 4750 4734 -16
+ Misses 402 399 -3
Continue to review full report at Codecov.
|
I understand that your idea is to completely remove the batch size option. Besides a batch of only 20 items by default looks small, we could at least keep the option for the developer to define a batch size, which can be useful and very convenient for saving a huge amount of objects. For example, I have recently used the JS SDK to load data to one of my apps and called |
I see, you have a valid point. Maybe we could do |
Yes. I'd prefer something like this. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice
ok, next time i'll read the convo first. if i could dismiss my approval, i would. |
@acinader No problem, I'll close this out and make the changes in a separate PR. |
Closes: #1045
Adds slight improvement to
saveAll([ParseFiles])
. Should we return the parse files if only saving parse files?Although batchSize is removed
saveAll
will still make multiple calls to the/batch
endpoint to check for save cycles.