fix: correctly scopes data variable within bulk update - #2901 #2904
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.
Description
Fixes #2901
The issue was caused by data being stored outside of the promises. This lead to stale data being set and accessed when setting/passing data within the bulk update operation.
I also removed the code related to files. I found it counterintuitive to even think about files when bulk updating an upload enabled collection. The admin panel does not allow upload enabled collections to replace all files with one file when performing a bulk update. The code removal aligns the API with the admin panel UI/UX, as it would be strange to replace all files with one file.Type of change
Checklist: